#Any changes recently on Railway that could cause this Auth0 error?

8 messages · Page 1 of 1 (latest)

haughty glen
#

I randomly started getting errors from auth0 that from my research, only happen when the server can't access auth0. auth0 still works locally and when not hosted on Railway. I'm trying to rule out any recent change on railway that could cause this issue. Anything related to limiting web traffic recently get pushed?

Here is the error I now run into and a forum post about possible things that could cause it, including changes to ports, or changes to the default node.js railway container:

https://community.auth0.com/t/login-handler-failed-cause-discovery-requests-failing-for-https-stattracker-uk-auth0-com/128627/8

Auth0 Community
Login handler failed. CAUSE: Discovery requests failing for https:/...

Hi @dawid.matuszczyk Thanks for the response! The 2 things you wanted me to check: from the host machine I was able to do both of them and there were no issues. However when running the same commands from the container it doesn’t work. It seems that my container doesn’t have internet access and as such can’t call out to your discovery endpoint...

sturdy spadeBOT
#

Project ID: 98f66160-ce86-4b15-a73b-cab912256208

haughty glen
#

98f66160-ce86-4b15-a73b-cab912256208

#

The outage started sometime between 11:30am PT and 4pm PT. was there any changes to containers or how network is allowed in and out of railway node.js containers during that time?

#

This has resulted in a complete outage for us,

#

For completness:
LoginHandlerError: Login handler failed. CAUSE: Discovery requests failing for https://dev-<READACTED>.us.auth0.com, outgoing request timed out after 5000ms

this is the error I'm receiving. I've tracked it down to mean that my railway app cannot reach auth0. Locally, the app works fine, and i have quadruple checked my env variable and all looks correct in my railway config.

Any help on this would be much appreciated

haughty glen
#

after redeploying, it now works