-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Error: double colon in host identifier] #1002
Comments
It seems that you have 2 servers specified in your MONGOLAB_URI, is that one purpose? |
@flovilmart Yes it's a replica set on mLab. I took the connection string directly form them. I also tried using only one of the database url's, but I still have the same problem. If you check out the issue i referred there is a bug in the mongo driver actually but it is strange that no one else is having the same problem. |
can you test on that branch about to be merged? #986 |
I'm not sure how I can use that branch on parse-server since the driver is added as an npm dependency. If you can point me in a direction of how to, I'd be glad. |
if this is a mongo driver problem, please post the issue to the mongo people :) |
@flovilmart I tried to use that branch you offered by changing the dependency in parse-server-example package.json to All I get is Can you help me build with that branch please? |
The branch at #986 seems to help. It appears that mongo driver can't parse a password with a column ',' in it. This branch seems to fix it or another option is to avoid '@,:' in your database username or password. Also mongo driver doesn't accept replica set connection strings obtained from mLab. The connection string needs to have only one database url in it. This issue and related issue #855 can be closed now. |
hello, i am still facing this issue, any suggestions? my DB connection string is mongodb://username:password@7163360509808/iad2-c5-1.mongo.objectrocket.com:port/preprod at new Promise (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:191:7) |
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
parse-server-example 2.1.4 running on Heroku
database running on mLab shared cluster
Steps to reproduce
MONGOLAB_URI : mongodb://:@ds059645-a0.mongolab.com:59645,ds059645-a1.mongolab.com:59645/?replicaSet=rs-ds059645
#855
@gfosco
Logs/Trace
2016-03-12T17:21:07.174007+00:00 heroku[web.1]: Starting process with command
npm start2016-03-12T17:21:08.712950+00:00 app[web.1]: 2016-03-12T17:21:08.712960+00:00 app[web.1]: > parse-server-example@1.2.0 start /app 2016-03-12T17:21:08.712961+00:00 app[web.1]: > node index.js 2016-03-12T17:21:08.712961+00:00 app[web.1]: 2016-03-12T17:21:10.105043+00:00 app[web.1]: parse-server-example running on port 27750. 2016-03-12T17:21:10.573179+00:00 heroku[web.1]: State changed from starting to up 2016-03-12T17:21:26.759620+00:00 app[web.1]: [Error: double colon in host identifier] 2016-03-12T17:21:56.747283+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/parse/classes/Waves" host=coralline.herokuapp.com request_id=d94cfa43-8644-4d30-a684-71fdef946cc8 fwd="178.240.162.250" dyno=web.1 connect=1ms service=30205ms status=503 bytes=0
The text was updated successfully, but these errors were encountered: