parse-server: Issue - users not able to log in after updating to v3

I’ve just updated my Parse server by updating nodejs, node, npm and then using ‘git pull’ and ‘npm install’ to update. Dashboard is running fine but at the top of the dashboard it says “v1.0.18” which I believe is not the newest.

Non of our 6K users can log in right now so I need this fixed asap. I tried logging on on a test IOS device and got the error back from the server (after a correct username and password were entered):

unauthorized (Code: 0, Version: 1.13.0) 2018-12-08 21:59:00.841563+0000 QuickFlics[3086:757234] ERRORR = Error Domain=Parse Code=0 "unauthorized" UserInfo={error=unauthorized, NSLocalizedDescription=unauthorized, temporary=0}

My package.json file: { "name": "parse-server-example", "version": "1.4.0", "description": "An example Parse API server using the parse-server module", "main": "index.js", "repository": { "type": "git", "url": "https://github.com/ParsePlatform/parse-server-example" }, "license": "MIT", "dependencies": { "express": "^4.16.4", "kerberos": "~0.0.x", "mailgun-js": "*", "npm": "^6.4.1", "nvm": "0.0.4", "parse": "~1.8.0", "parse-dashboard": "*", "parse-server": "*", "parse-server-mailgun": "*", "parse-server-simple-mailgun-adapter": "*", "stripe": "*" }, "scripts": { "start": "node index.js" }, "engines": { "node": ">=4.3" } }

Also I can’t see an error logged in the ‘logs’ section saying what went wrong (like I’d expect to be able to see if the user had entered a wrong password.

I logged verbose and only things related I can see is the following:

‘{“message”:"Unable to ensure uniqueness for usernames: ",“stack”:“MongoError: exception: Index with name: username_1 already exists with different options\n at /root/parse-server-example/node_modules/mongodb-core/lib/connection/pool.js:581:63\n at authenticateStragglers (/root/parse-server-example/node_modules/mongodb-core/lib/connection/pool.js:504:16)\n at Connection.messageHandler (/root/parse-server-example/node_modules/mongodb-core/lib/connection/pool.js:540:5)\n at emitMessageHandler (/root/parse-server-example/node_modules/mongodb-core/lib/connection/connection.js:310:10)\n at Socket.<anonymous> (/root/parse-server-example/node_modules/mongodb-core/lib/connection/connection.js:489:15)\n at Socket.emit (events.js:182:13)\n at Socket.EventEmitter.emit (domain.js:441:20)\n at addChunk (_stream_readable.js:287:12)\n at readableAddChunk (_stream_readable.js:268:11)\n at Socket.Readable.push (_stream_readable.js:223:10)”,“createdCollectionAutomatically”:false,“numIndexesBefore”:19,“errmsg”:“exception: Index with name: username_1 already exists with different options”,“code”:85,“ok”:0,“name”:“MongoError”,“level”:“warn”,“timestamp”:“2018-12-08T22:35:04.606Z”} {“message”:"Unable to ensure uniqueness for user email addresses: ",“stack”:“MongoError: exception: Index with name: email_1 already exists with different options\n at /root/parse-server-example/node_modules/mongodb-core/lib/connection/pool.js:581:63\n at authenticateStragglers (/root/parse-server-example/node_modules/mongodb-core/lib/connection/pool.js:504:16)\n at Connection.messageHandler (/root/parse-server-example/node_modules/mongodb-core/lib/connection/pool.js:540:5)\n at emitMessageHandler (/root/parse-server-example/node_modules/mongodb-core/lib/connection/connection.js:310:10)\n at Socket.<anonymous> (/root/parse-server-example/node_modules/mongodb-core/lib/connection/connection.js:489:15)\n at Socket.emit (events.js:182:13)\n at Socket.EventEmitter.emit (domain.js:441:20)\n at addChunk (_stream_readable.js:287:12)\n at readableAddChunk (_stream_readable.js:268:11)\n at Socket.Readable.push (_stream_readable.js:223:10)”,“createdCollectionAutomatically”:false,“numIndexesBefore”:19,“errmsg”:“exception: Index with name: email_1 already exists with different options”,“code”:85,“ok”:0,“name”:“MongoError”,“level”:“warn”,“timestamp”:“2018-12-08T22:35:04.640Z”}’

Any help much appreciated.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

@Rahul369Verma but wouldn’t that cause you to lose all of the data you might have in the collection?