You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a long-running server process, online for approximately 67 days. In that time, the server processed 7,319 logins using this module.
However, about 24 hours ago, the server appears to have stopped processing Google logins. After visiting the Google provider URL and signing in with their credentials, upon returning to my site via the callback URL, users were getting timeout errors (HTTP 504 Gateway Timeout since my server is running behind Nginx). My other Passport authentication modules continued working during the Google downtime.
Restarting my server process has temporarily resolved the issue. There are no unusual errors in my server log. I'm unsure what would have caused this problem, or even where in the stack the culprit lies, but I thought I'd post it here just in case.
The text was updated successfully, but these errors were encountered:
I have experienced something similar. I assumed it had something to do with Google deprecating Google+ logins. Not sure. But I received an email from Google that Google+ logins will be disabled in march, and can experience downtime also before that date.
Why passport seems to be stuck until a restart, I don't know.
Thanks for maintaining this module.
I had a long-running server process, online for approximately 67 days. In that time, the server processed 7,319 logins using this module.
However, about 24 hours ago, the server appears to have stopped processing Google logins. After visiting the Google provider URL and signing in with their credentials, upon returning to my site via the callback URL, users were getting timeout errors (HTTP 504 Gateway Timeout since my server is running behind Nginx). My other Passport authentication modules continued working during the Google downtime.
Restarting my server process has temporarily resolved the issue. There are no unusual errors in my server log. I'm unsure what would have caused this problem, or even where in the stack the culprit lies, but I thought I'd post it here just in case.
The text was updated successfully, but these errors were encountered: