Railway Dashboard Down
lacrossehub
PROOP

2 months ago

Hi team, the railway dashboard has been inaccessible for me for the last 72 hours. Logging into the dashboard gives the following error and screen: "The train was derailed". Nothing really useful in the network logs, clearing the cookies and site data doesn't fix either.

Solved

9 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


We're aware of a dashboard access issue affecting a number of users, our Product on-call Paulo just shipped what we may think is a fix for this but you may see this page before you redirect into the platform.


Status changed to Awaiting User Response Railway about 2 months ago


lacrossehub
PROOP

2 months ago

Thanks for getting back to me, I've cleared the site cookies and data, and attempted to login once again, however still getting the same issue.

Let me know if I can grab any data from the browser console


Status changed to Awaiting Railway Response Railway about 2 months ago


QQ: Do you have 2FA


Status changed to Awaiting User Response Railway about 2 months ago


lacrossehub
PROOP

2 months ago

Yep login with Github, GH has 2FA on it


Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

Gotcha, thank you for sharing that information. We will continue to look into this and update you when we have a fix out.


Status changed to Awaiting User Response Railway about 2 months ago


lacrossehub
PROOP

2 months ago

Adding the console logs here:

react-dom-CWIgXKDx.js:6 Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

main-DbLBmzdp.js:2 POST https://unifyintent.com/analytics/api/v1/page net::ERR_BLOCKED_BY_CLIENT

One interesting thing is that for this one I can see the network request to /page fail for dashboard here

fetch("https://unifyintent.com/analytics/api/v1/page", {

"headers": {

"authorization": "Basic d2tfTFE3QTNFbmtfRGkyZDYxQzc3d01HTHlnOHMxNDZoQzdYWnFRZVU0Nm06",

"content-type": "application/json; charset=UTF-8",

"sec-ch-ua": "\"Chromium\";v=\"146\", \"Not-A.Brand\";v=\"24\", \"Google Chrome\";v=\"146\"",

"sec-ch-ua-mobile": "?0",

"sec-ch-ua-platform": "\"macOS\""

},

"referrer": "https://railway.com/",

"body": "{\"type\":\"page\",\"anonymousUserId\":\"7326dc50-9e9c-4552-85d1-384ac1321d83\",\"sessionId\":\"970a541a-184e-434b-97ed-0d5f74a4d48b\",\"context\":{\"locale\":\"en-US\",\"userAgent\":\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36\",\"userAgentData\":{\"brands\":[{\"brand\":\"Chromium\",\"version\":\"146\"},{\"brand\":\"Not-A.Brand\",\"version\":\"24\"},{\"brand\":\"Google Chrome\",\"version\":\"146\"}],\"mobile\":false,\"platform\":\"macOS\"},\"utm\":{}},\"timestamp\":\"2026-04-02T04:48:03.561Z\",\"properties\":{\"path\":\"/dashboard\",\"query\":{},\"referrer\":\"https://github.com/\",\"title\":\"\",\"url\":\"https://railway.com/dashboard\"}}",

"method": "POST",

"mode": "cors",

"credentials": "include"

});

osano.js:1 GET https://luminaire.railway.com/static/posthog-recorder.js?v=1.298.0 net::ERR_BLOCKED_BY_CLIENT

the rest are stripe fetch errors also blocked by client


Status changed to Awaiting Railway Response Railway about 2 months ago


lacrossehub
PROOP

2 months ago

ERR_BLOCKED_BY_CLIENT probably just has to do with ublock origin extension, hasn't been an issue before with Railway


2 months ago

Hey, we just merged a fix for this. The issue arises when a user doesn't have 2FA enabled on their account, but they are part of a workspace that requires its users to have 2FA enabled. Now, instead of the derailed page, we show a modal that prompts you to enable 2FA.


Status changed to Awaiting User Response Railway about 2 months ago


lacrossehub
PROOP

2 months ago

Ahhh that makes sense. Thanks for looking into, confirmed fixed on my end


Status changed to Awaiting Railway Response Railway about 2 months ago


Status changed to Solved lacrossehub about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...