Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MongoServerSelectionError: getaddrinfo ENOTFOUND #1037

Closed
1 of 6 tasks
YuriGor opened this issue Jan 3, 2021 · 2 comments
Closed
1 of 6 tasks

MongoServerSelectionError: getaddrinfo ENOTFOUND #1037

YuriGor opened this issue Jan 3, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@YuriGor
Copy link
Contributor

YuriGor commented Jan 3, 2021

Describe the bug
Bug in typeorm dep

Steps to reproduce

npx create-next-app --example with-next-auth with-next-auth-app
  • Configure to use MongoDB Atlas.
  • Configure Google OAuth
  • run npm run dev
  • try to login

Expected behavior
Should work

Screenshots or error logs

https://next-auth.js.org/errors#adapter_connection_error
[next-auth][error][oauth_callback_handler_error] TypeError: Cannot destructure property 'manager' of 'connection' as it is null.
    at Object.<anonymous> (/home/gor/Development/planzed/node_modules/next-auth/dist/adapters/typeorm/index.js:102:9)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/home/gor/Development/planzed/node_modules/next-auth/dist/adapters/typeorm/index.js:28:103)
    at _next (/home/gor/Development/planzed/node_modules/next-auth/dist/adapters/typeorm/index.js:30:194) 
https://next-auth.js.org/errors#oauth_callback_handler_error

Additional context
Issue should be fixed in typorm@v0.2.30
typeorm/typeorm#7009 (comment)

Here is my pr: #1036
but v0.2.30 is not published yet.

Feedback

  • N/A
  • Found the documentation helpful
  • Found documentation but was incomplete
  • Could not find relevant documentation
  • Found the example project helpful
  • Did not find the example project helpful
@YuriGor YuriGor added the bug Something isn't working label Jan 3, 2021
@balazsorban44
Copy link
Member

isn't this a duplicate of #833?

@YuriGor
Copy link
Contributor Author

YuriGor commented Jan 3, 2021

Yes, looks like dup, sorry, will try workarounds there
Looks like incoming typorm v0.2.30 is also going to fix this in a straightforward way.

@YuriGor YuriGor closed this as completed Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants