a year ago
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:
0 Replies
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?
For completness:LoginHandlerError: Login handler failed. CAUSE: Discovery requests failing for https://dev-.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
All online resources point me to this being some sort of endpoint protection layer. Does railay have anything like that?
Context: https://github.com/auth0/nextjs-auth0/issues/1336#issuecomment-1660497703