That's the mistake!
I searched the Internet. The solution is almost all about the issue of authentication mechanisms:
>Use Admin switched to DB admin>Db.system.version.find () {"_id":"featurecompatibilityversion","version":"3.4" } { "_id":"Authschema","CurrentVersion":5}
Then delete the user after the "CurrentVersion": Change to 3 and finally add the user.
But I tried it many times and I didn't use!!!!!!!!!!!!!!!!!!!!.
If you use the above solution, it may be a mechanism problem. If not, you should not use the Admin library to log in.
See below, how do I fix it.
Very simple, you use admin after the user of create only for the admin library,
Your own library, like test, you need to use test and then build another
Db.createuser ({User:"xxx", pwd:"123456", roles:[{" role":"readWrite","db": " Test "}]})
The user name and password can be the same as the admin library.
Okay, here we go.
Using Robomongo to connect MongoDB Authorization failed solution