next-auth: Mongo Atlas - MongoServerSelectionError: getaddrinfo ENOTFOUND

The issue seems to be related to typeorm version 0.2.29 according to this https://github.com/typeorm/typeorm/issues/7009 .

Adding this to your package.json should fix the issue temporarily until they fix it "resolutions": { "typeorm": "0.2.28" }

Edit: I forgot to mention, this workaround only works if you are using yarn. Otherwise use @unflawed solution instead

fixed by this command npm i typeorm@0.2.28

I just switched from mLab to Mongo Atlas, and started having the same problem. I found this thread, and switched from "typeorm": "^0.2.29" to "typeorm": "0.2.28" (note the LACK of a caret ^ in the version, to LOCK it to 0.2.28). That seems to have resolved the issue, and I am now able to connect to Mongo Atlas.

If I switch back to 0.2.29 or use any kind of semantic version auto-upgrade option (^ or ~ or .x) in the version, it uses the latest, and also has a problem. Locking the typeorm node module version to 0.2.28 seems to resolve the issue.

not sure if I am the only one, but I haven’t been able to get it working with any method in this thread so far.

Having same issue and adding "resolutions": { "typeorm": "0.2.28" } to my package.json didnt fix my problem. Any other ideas how to fix it?

Fixed. If you get this, you need to install and import the reflect-metadata package.

1. Install the npm package: npm install typeorm --save
2. You need to install reflect-metadata shim: npm install reflect-metadata --save
3. Import reflect-metadata somewhere in the global place of your app (for example in app.ts):

// _app.ts or _app.js
import "reflect-metadata";
...

Suggest making this clearer in the docs if possible.

this is available in the latest canary release!

Although it hasn’t been released yet, the PR to fix this in TypeORM has been merged.

I was able to fix it using the following config in [...nextauth].js:

 database: {
        type: "mongodb",
        useNewUrlParser: true,
        url: process.env.DATABASE_URL,
        ssl: true,
        useUnifiedTopology: true,
        authSource: "admin",
    },

To resolve for now without any “hackery”, simply bypass the string parser’s reliance on typeorm in the adapter and construct the object yourself. This way you don’t have to install a previous typeorm version, modify your package.json, or include reflect-metadata.

If your string looks like this: mongodb+srv://<username>:<password>@<cluster>.yu5ue.mongodb.net/<dbname>?retryWrites=true&w=majority

In your options for NextAuth, make your database value an object instead of a string. The structure should look as follows:

...
database: {
  type: "mongodb",
  uri: "mongodb+srv://<username>:<password>@<cluster>.yu5ue.mongodb.net/<dbname>",
  w: "majority",
  useNewUrlParser: true,
  useUnifiedTopology: true,
  retryWrites: true,
},

Important: Note that it says uri and not url. Obviously it is recommended to store values in .env.local.

Optional values such as synchronize and logger can also be added to the object.

Source of the issue seems to be coming from typeorm config. Big thanks to Richard Furberg for pointing me in the right direction.

@Zertz @matiastucci Thanks for the update!

Great to know there is a fix in progress with TypeORM!

Will get that rolled in and we can update the dependencies and docs when typeorm@0.3.0 is out.

This worked for me:

yarn add typeorm@next

and adding this in the package.json:

"resolutions": {
  "typeorm": "0.3.0-alpha.24"
},

@andrewgwallace try changing “optionalDependencies” to “peerOptionalDependencies” in your package.json like so: "peerOptionalDependencies": { "mongodb": "^3.6.2" }

Fix should be available in the latest typeorm @0.2.30

@andrewgwallace try changing “optionalDependencies” to “peerOptionalDependencies” in your package.json like so: "peerOptionalDependencies": { "mongodb": "^3.6.2" }

Yes that seems to have resolved it! Thank you @SelvinM ! Had to install mongodb as a dependency of course.

Yea – my solution stopped working for me as well. 😭 I reverted to downgrading to typeorm 0.2.28 and the resolutions in my package.json. However now I’m getting UnhandledPromiseRejectionWarning: Error: no optional dependency [mongodb] defined in peerOptionalDependencies in any package.json I’ve also tried the steps recommended in issue https://github.com/nextauthjs/next-auth/issues/552 of NextAuth. I’ve got a hunch the issue stems from https://github.com/nextauthjs/next-auth/issues/552#issuecomment-671662283 but that’s out of the scope of my knowledge on how to resolve beyond what he suggested.

For now, the stability of NextAuth and MongoDB Atlas is not sufficient enough for production use IMO. I’ll keep an eye on this and other tickets for progress.

Just going to note current key settings here where I last had it. If someone spots an issue let me know. Node version: 12.19.0 package.json:

  "dependencies": {
     ...
    "next-auth": "^3.1.0",
    "reflect-metadata": "^0.1.13",
  },
  "optionalDependencies": {
    "mongodb": "^3.6.3"
  },
  "resolutions": {
    "typeorm": "0.2.28"
  },

_app.js import "reflect-metadata"; […nextauth].js

  database: {
    type: "mongodb",
    uri: process.env.DATABASE_URL, // mongodb+srv://<user>:<pass>@<cluster>.yu5ue.mongodb.net/<db>
    w: "majority",
    useNewUrlParser: true,
    useUnifiedTopology: true,
    retryWrites: true,
  },

I just switched from mLab to Mongo Atlas, and started having the same problem. I found this thread, and switched from "typeorm": "^0.2.29" to "typeorm": "0.2.28" (note the LACK of a caret ^ in the version, to LOCK it to 0.2.28). That seems to have resolved the issue, and I am now able to connect to Mongo Atlas.

If I switch back to 0.2.29 or use any kind of semantic version auto-upgrade option (^ or ~ or .x) in the version, it uses the latest, and also has a problem. Locking the typeorm node module version to 0.2.28 seems to resolve the issue.

Solved for me! Thanks @jrista 😃

@iaincollins Could you pin this issue so it’s easier for other mongodb users to find? Thanks! 🎉

Adding the resolution to my package.json resolved the issue for me.

@unflawed your solution worked for me, thanks so much! ❤️

Having same issue and adding "resolutions": { "typeorm": "0.2.28" } to my package.json didnt fix my problem. Any other ideas how to fix it?

Fixed. If you get this, you need to install and import the reflect-metadata package.

1. Install the npm package: npm install typeorm --save
2. You need to install reflect-metadata shim: npm install reflect-metadata --save
3. Import reflect-metadata somewhere in the global place of your app (for example in app.ts):

// _app.ts or _app.js
import "reflect-metadata";
...

Suggest making this clearer in the docs if possible.

Worked for me. Thanks! 👍