Description
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
- You've met the prerequisites.
- You're running the latest version of Parse Server.
- You've searched through existing issues. Chances are that your issue has been reported or resolved before.
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
Logs/Trace
2016-03-12T17:21:07.174007+00:00 heroku[web.1]: Starting process with command
npm start 2016-03-12T17:21:08.712950+00:00 app[web.1]: 2016-03-12T17:21:08.712960+00:00 app[web.1]: > [email protected] 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