a month ago
The login page at railway.com/login is non-functional. The main JavaScript bundle (/assets/main-BVcHbIfI.js) is being served truncated by the CDN, causing the entire app to fail with SyntaxError: Unexpected end of input.
Details:
- File:
https://railway.com/assets/main-BVcHbIfI.js -
- Expected size (from ETag
9259f): 599,455 bytes
- Expected size (from ETag
-
- Actual size received: 562,703 bytes
-
- Missing: ~36,752 bytes (≈6% of the file)
-
- CDN edge serving the truncated file:
railway/us-east4-eqdc4a(x-cache: HIT)
- CDN edge serving the truncated file:
-
- The GitHub login button and all interactive elements are non-responsive because the React app never initializes
-
- Hard reload and cache clearing do not resolve the issue — the truncation happens server-side on the CDN
6 Replies
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
Is this truncation or compression?
I am not able to check as that File 404's for me.
Status changed to Awaiting User Response Railway • 26 days ago
25 days ago
Hi Brody! To simplify: the main issue is that when I go to railway.com/login and click "Continue with GitHub", nothing happens at all — the button is completely unresponsive.
The login page loads visually, but no interactions work. I can't log in at all. Clearing the browser cache and hard reloading didn't help.
The technical details I mentioned may have been related to my specific CDN edge node — if the file is 404ing for you, it's possible the issue varies by region. I'm located in Brazil and connecting to the us-east4-eqdc4a edge.
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
The JS file you referenced has since been replaced by a newer deploy of the dashboard, which is likely why Brody saw a 404. That new deploy would have invalidated the CDN cache for the old asset. Could you try loading railway.com/login again in an incognito/private window and let us know if the GitHub button is still unresponsive?
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Hi mykal! Still not working, even after the new deploy.
The new bundle (main-CY1FwGGU.js) is still being served truncated by the same CDN edge node:
- Expected: 599,455 bytes (from ETag)
-
- Received: 562,637 bytes (~36KB missing)
-
- Edge: railway/us-east4-eqdc4a (x-cache: HIT)
The JS fails with SyntaxError: Unexpected end of input, so the app never initializes and the GitHub login button remains completely unresponsive. This specific edge node (us-east4-eqdc4a) seems to be caching a corrupted/truncated version of the file. Could you force a cache purge on that specific node?
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
We've purged the CDN cache on that edge node. Could you try loading railway.com/login again with a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) and let us know if it's working now?
Status changed to Awaiting User Response Railway • 25 days ago
24 days ago
Hello! Could you also visit https://railway.com/.railway/cdn-trace from the same network that you were experiencing this issue from with and copy+paste the output into this thread? Thank you!
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago