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
We've been using this module for a couple years now with no issues. All of a sudden over the past 24-48 hours without any code changes we've seen a huge amount of errors like these repeatedly.
InternalOAuthError: failed to fetch user profile
at /Users/danvk/github/better-mobility/node_modules/passport-google-oauth2/lib/oauth2.js:92:28
I went to that file and console.log'd the err object. It spit this out:
{ statusCode: 403,
data: '{\n "error": {\n "errors": [\n {\n "domain": "usageLimits",\n "reason": "accessNotConfigured",\n "message": "Access Not Configured. The API (Google+ API) is not enabled for your project. Please use the Google Developers Console to update your configuration.",\n "extendedHelp": "https://console.developers.google.com"\n }\n ],\n "code": 403,\n "message": "Access Not Configured. The API (Google+ API) is not enabled for your project. Please use the Google Developers Console to update your configuration."\n }\n}\n' }
That's a much more helpful error message! Maybe try something similar?
passport-google-oauth should do a better job of surfacing this error.
InternalOAuthError: Failed to fetch user profile (status: 500 data: {
"error": {
"code": 500,
"message": null
}
}
)
at /var/www/node_modules/passport-google-oauth20/lib/strategy.js:99:19
at passBackControl (/var/www/node_modules/oauth/lib/oauth2.js:132:9)
at IncomingMessage.<anonymous> (/var/www/node_modules/oauth/lib/oauth2.js:157:7)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickDomainCallback (internal/process/next_tick.js:218:9)
We've been using this module for a couple years now with no issues. All of a sudden over the past 24-48 hours without any code changes we've seen a huge amount of errors like these repeatedly.
Also
Anyone have any ideas? Thanks.
The text was updated successfully, but these errors were encountered: