Galaxy mongo auth failed

deployment
1

I’m having some issues with my mongo db set up for my galaxy deploy.

This is my full settings.json:

{
“postTwitter”: false,
“linkScore”: 1000,
“listLength”: 10,
“archiveLength”: 100,
“twitterConsumerKey”: “xxx”,
“twitterConsumerSecret”: “xxx”,
“twitterAccessToken”: “xxx”,
“twitterAccessSecret”:“xxx”,
“timeOne”: 4.6,
“timeHold”: 1,
“galaxy.meteor.com”: {
“env”: {
“ROOT_URL”: “http://latest.xyz”,
“MONGO_URL”: “mongodb://xxxuser:xxxpassword@ds025918-a0.mlab.com:25918,ds025918-a1.mlab.com:25918/database”,
“MONGO_OPLOG_URL”: “mongodb://xxxoplog-user:xxxpassword@ds025918-a0.mlab.com:25918,ds025918-a1.mlab.com:25918/admindatabase”
}
}
}

(With some fields changed of course)

The logins work if I use mongo right away like:
mongodb://:@ds025918-a0.mlab.com:25918,ds025918-a1.mlab.com:25918/admin

But my galaxy logs say:
2016-03-09 15:40:16+01:00Exception in callback of async function: MongoError: auth failed
vzjv
2016-03-09 15:40:16+01:00 at Object.toError (/app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/utils.js:110:11)
vzjv
2016-03-09 15:40:16+01:00 at /app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1128:31
vzjv
2016-03-09 15:40:16+01:00 at /app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1843:9
vzjv
2016-03-09 15:40:16+01:00 at Server.Base._callHandler (/app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
vzjv
2016-03-09 15:40:16+01:00 at /app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
vzjv
2016-03-09 15:40:16+01:00 at MongoReply.parseBody (/app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
vzjv
2016-03-09 15:40:16+01:00 at null.<anonymous> (/app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
vzjv
2016-03-09 15:40:16+01:00 at emit (events.js:95:17)
vzjv
2016-03-09 15:40:16+01:00 at null.<anonymous> (/app/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
vzjv
2016-03-09 15:40:16+01:00 at emit (events.js:98:17)
2 Likes
2

did you ever solve this? having the same issue.

3

I’ve found this to somehow be caused by the custom domain setup,I’m not sure whats wrong yet, but the problem isn’t with mongo.

I’m using galaxy with compose.io and godaddy as my domain registrar.

4

HI wondering if you resolved this?
I am trying to upgrade on Galaxy (using compose.io) and getting this issue. I upgrade to Compose.io MongoDB 3.2/WiredTiger

5

BYW< not sure if you saw this article https://www.compose.com/articles/connecting-to-the-oplog-on-the-new-mongodb/