a month ago
Hi Railway Support,
Could you help me check whether there was a Railway-side routing or networking issue for my service on May 20?
An API request failed with Railway’s default 404 page:
“The resource you are requesting could not be found”
“The train has not arrived at the station.”
Request ID:
XRu8mCCfSZq-eL67ljLL4A
The request was made from:
empathetic-cat / Primary / production (n8n)
to:
refreshing-creation / majerier-rental / production API
Endpoint:
The same endpoint and request format works on other days, so I’d like to confirm whether the request failed before reaching my FastAPI app.
Thanks.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago
a month ago
That specific Railway 404 page usually means the request did not hit your FastAPI route. It’s Railway edge/router output, not a normal app-level 404.
One thing I’d still change in n8n: call the HTTPS URL directly, not HTTP.
Right now the HTTP URL redirects at the Railway edge:
http://majerier-rental-production.up.railway.app/... -> 301 -> https://majerier-rental-production.up.railway.app/...So in n8n I’d use:
https://majerier-rental-production.up.railway.app/rentals?...and make sure the HTTP Request node is following redirects.
For the May 20 event specifically, only Railway can trace XRu8mCCfSZq-eL67ljLL4A. On your side, I’d compare these for failed vs working requests:
- final URL after redirects
- status code
- response headers:
server,x-railway-edge,x-railway-request-id - whether there are app logs at that exact timestamp
If the response is Railway’s train/station 404 and your app logs are empty, then yeah, it failed before FastAPI. The usual causes are generated domain not attached at that moment, service/deployment not routable yet, wrong environment/domain, or a short Railway edge routing issue. The request ID is the strongest thing for staff to confirm which one it was.