Fail to connect Mongolab with MongodbShell - javascript

I'm trying to connect the Mongo shell with Mongolab. I am using my mongolab username and password but it is giving an error: "Failed to connect to 54.81.180.188:56789."
My userName and password is correct.
I'm using Windows 8.1
When I ping ds0-----.mongolab.com that's working fine.
C:\mongodb\bin>mongo ds0----.mongolab.com:56789/dbname -u "MyUserName" -p "MyPassword"
MongoDB shell version: 3.0.3
connecting to: ds027751.mongolab.com:56789/dbname
2015-06-05T10:55:30.019+0530 W NETWORK Failed to connect to 54.81.180.188:56789, reason: errno:10061 No connection could be made because the target machine actively refused it.
2015-06-05T10:55:30.024+0530 E QUERY Error: couldn't connect to server ds027751.mongolab.com:56789 (54.81.180.188), connection attempt failed
at connect (src/mongo/shell/mongo.js:181:14)
at (connect):1:6 at src/mongo/shell/mongo.js:181
exception: connect failed

I had the same problem, my server abruptly lost the ability to connect to MongoLab. I contacted support, who sent this reply:
Hello,
Your Experimental Sandbox plan is running MongoDB 3.0.x, which
includes changes to Mongo's authentication mechanism. This new
mechanism is supported by certain newer driver versions, as described
at
http://docs.mongodb.org/manual/release-notes/3.0-scram/#upgrade-drivers.
To connect to this database, you will need to use one of the drivers
listed at the above link.
Please let us know if you have questions about this.
Sincerely, Samson
I assume I was upgraded automatically, as I hadn't touched the server code or MongoLab in months. As an immediate fix, I just created a new db in MongoLab, which was created in mongod v2.6.9 (I don't remember seeing an option to choose the version).

Related

ntlm auth failed with error STATUS_USER_SESSION_DELETED

I am using a Windows server to manage our files(read, write). To connect to that server I am using SMB2 npm module https://www.npmjs.com/package/smb2. Internally, this module uses the ntlm method to authenticate. While authenticating, I am getting the error STATUS_USER_SESSION_DELETED. Authentication process is given below:
it sends NEGOTIATE command
SESSION_SETUP command
SESSION_SETUP command with SessionId (this is where the error is thrown)
TREE_CONNECT command
There is already open issues regarding same with Repo, so, waiting for that as well but any lead would be helpful

Sails.js connect to Cloud mongoDb Atlas

I created a Sails.js app, it connects to local MongoDB correctly but if I want to connect it to cloud mongodb, Sails throws an error. what should I do to fix it?
default: {
adapter: 'sails-mongo',
// url: 'mongodb://localhost:27017/referral' // this work fine
url: 'mongodb+srv://MYUSERNAME:MYPASS#cluster0.ikncs.mongodb.net/referral?retryWrites=true&w=majority'
},
error:
error: A hook (orm) failed to load!
error: Could not tear down the ORM hook. Error details: Error: Consistency violation: Attempting to tear down a datastore (default) which is not currently registered with this adapter. This is usually due to a race condition in userland code (e.g. attempting to tear down the same ORM instance more than once), or it could be due to a bug in this adapter.
error: Error: Invalid configuration for datastore default: Provided URL ('mongodb+srv://MYUSERNAME:MYPASS#cluster0.ikncs.mongodb.net/referral?retryWrites=true&w=majority') has an invalid protocol.
If included, the protocol must be "mongodb://".
I will appreciate if someone help quickly
I had a similar issue.
The connection string I got from Atlas was for Node version 3.0 or later did not work with the sails adapter.
But the connection string from Atlas for Node version 2.2.12 worked.
From Atlas, click connect -> Connect to your application (using MongoDB's Native Drivers) -> Select Node.js Version 2.2.12 or later. Use the connection string it provides.
I have got the same issue, it’s due to mongodb version used in sails-mongo, for our production database we have worked on improving the existing package.
You can search for sails-mongo-cloud in npm which supports cloud mongo atlas and cluster with server less setup as well.

IBM MFP Adapter Deployment Failed

Using IBM MFP 8 with Google cloud platform,
I have an adapter with many java/lib dependencies, adapter built successfully but when i deploy in MFP Console,
getting Connection error. Contact the server administrator (HTTP code: 413)
Adapter File Size is 42MB
Hope your other adapter deploys successfully, Below are the reasons
Check the connection time out on your server.xml for under data source tag.
Connection alive time in your DB as you have mentioned Google cloud.
If using F5, check the error status and max size allowed params.

Failed to connect to SQLEXPRESS - Node.js

I am trying to connect to my MS SQL database via node.js (Express), but the connection cannot be established. I have probably wrong configuration, but I have tried everything and nothing worked. I also enabled TCP/IP in configuration Manager.
Here is my JS code: https://snipboard.io/ufk49d.jpg
Here is one of my errors: https://snipboard.io/wyTbLi.jpg
When I add localhost or IP adress before SQLEXPRESS in server configuration, it thow this error: https://snipboard.io/RE6Xov.jpg
And also, I added new user and allow SQL auth and windows auth connection.
Thanks for your tips!
Can you put your machine name in server parameter?
server: 'YOUR_MACHINE_NAME\\SQLEXPRESS',

Kurento Media Server HelloWorld Javascript example webSocket error

Merry Christmas!
I am trying to configure KMS on my Ubuntu 14.04 (64 bit). I could install the KMS server successfully following the guide at https://www.kurento.org/docs/6.0.0/installation_guide.html.
Also, downloaded the Javascript HelloWorld tutorial from https://www.kurento.org/docs/6.0.0/tutorials/js/tutorial-1-helloworld.html. I could run the example successfully on localhost on Google Chrome Version 47.0.2526.106 (64-bit) on the same Ubuntu System.
But, I could not see the local video nor the loop backed video. Only a spinner icon is shown on both the Video placeholders. Consulting the Console log reveals a problem after creating the SDP offer. The error is as described below.
kurento-client.js:21072 WebSocket connection to 'wss://127.0.0.1:8433/kurento' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
I am no expert on web sockets and stuff. Any help on this would really help me to proceed forward.
Note: I am running the example on HTTP, not on HTTPS. I guess that would not be the cause of the problem, though.
Regards,
LazyCoder7
I managed to solve it. I was wrong on my guess though, HTTPS was indeed required in order to make the WebSocket connection ( i was not aware of that part ). Created a certificate file (.pem) (from crt and key file already in the helloworld folder) and configured the KMS server to use the certificate. After this I was able to see myself and the same me in loopback :)
You are following an old version of the documentation. Since Chrome 47, in is mandatory to server pages through HTTPS if you want to use the getUserMedia APi. So we updated all our tutorials, and they now have a self-signed certificate. In case of the JS tutorials, you also need to configure KMS to expose a secure WS signalling connection, as the browser directly connects to the media server to control it.
Please follow the latest version of the documentation here
Be sure that the KMS is running on the port 8433 (not 8888), if you are using docker
docker run -d --name kms -p 8433:8433 kurento/kurento-media-server:trusty-latest

Categories