Skip to content

MongoError  #1438

Closed
Closed

Description

@GongChen1107

Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

Environment Setup

parse-server version 2.2.6

Steps to reproduce

When I modify databaseUri to a cluster "mongo://....." ,I come up the error of "MongoError: Authentication failed" ,but the same connection string can work in the old version of parse server (2.1.3).
I change the connection string to a singe node mlab ,I can pass the indentify and get the instalations data. I doubt that there are some issue in the mongo libs.

Logs/Trace

error: Uncaught internal server error. { [MongoError: Authentication failed.]
name: 'MongoError',
message: 'Authentication failed.',
ok: 0,
code: 18,
errmsg: 'Authentication failed.' } MongoError: Authentication failed.
at Function.MongoError.create (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/error.js:31:11)
at commandCallback (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/topologies/server.js:1154:66)
at Callbacks.emit (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/topologies/server.js:119:3)
at null.messageHandler (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/topologies/server.js:295:23)
at Socket. (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/connection/connection.js:285:22)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:529:20)

Activity

  1. GongChen1107 commented on Apr 12, 2016

    @GongChen1107
    Author

    I found the reason .
    b82deec0-a409-4d0a-b4ee-360e9864b79a The url format makes the connenction string authentication failed

  2. tony-pizza commented on Apr 14, 2016

    @tony-pizza

    I ran into this as well and the solution above fixed it. For me it was due to a / character and uppercase letters in my password. Manually encoding the slash worked without modifying any code. See here: #986 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions