Request timed out error while using Google provider
See original GitHub issueDescription 🐜
After following the docs for Prisma Adapter and Google Provider, I added auth to my repo, but when trying to log in through google auth, it’s timing out for some reason.
I even tried with a longer timeout, but still no luck 😦
providers: [
GoogleProvider({
clientId: process.env.GOOGLE_CLIENT_ID,
clientSecret: process.env.GOOGLE_CLIENT_SECRET,
httpOptions: {
timeout: 10000,
}
})
],
Is this a bug in your own project?
Yes
How to reproduce ☕️
I replicated the issue in a new separate repo, just add the env variable and run it in local - https://github.com/Nikit-Singh/next-auth-google-issue
Screenshots / Logs 📽
No response
Environment 🖥
System:
OS: Windows 10 10.0.22000
CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
Memory: 4.38 GB / 15.95 GB
Binaries:
Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22000.120.0), Chromium (96.0.1054.62)
Internet Explorer: 11.0.22000.120
npmPackages:
next: 12.0.10 => 12.0.10
next-auth: ^4.2.1 => 4.2.1
react: 17.0.2 => 17.0.2
Contributing 🙌🏽
Yes, I am willing to help solve this bug in a PR
Issue Analytics
- State:
- Created 2 years ago
- Comments:30 (3 by maintainers)
Can you guys try passing httpOptions with timeout like shown below (40000 is in ms)and check the error, now it won’t timeout because of openid-client, but you’ll see some error due to network issue with google/github auth server from there you can further check the issue.
No bug in sight, your Node.js process may not be able to reach google servers for a variety of local network / network setup related reasons.