2 months ago
Hi, my app stopped being reachable yesterday at rockket-production.up.railway.app even though nothing changed on my end.
Details:
Service: Server (NestJS backend)
Domain: rockket-production.up.railway.app
Latest deployment: 084e08dc-ce92-46de-874d-e0ef7708de31 (successful)
Service status: Online, running 1 replica
App status: Healthy, all routes mapped correctly
The issue: Requests to the domain return 404 straight from Railway's edge layer. The service itself is working fine — I can see successful requests in the logs from before it broke. No code changes, no config changes. It just stopped routing.
It seems I am still using Nixpacks, but not sure that would suddenly result in my domian not routing to the service anymore?
What I've tried:
Redeployed the service
Removed and re-added the domain
Verified the app is listening on the correct port (switiched between detected 8080 and 300)
This appears to be a routing issue at Railway's infrastructure level. Can someone help investigate?
17 Replies
2 months ago
Can you make sure that the domain you show there is actually assigned to that service? A screenshot would be helpful
2 months ago
the 404 means Railway doesn't see any service assigned to that domain
Attachments
2 months ago
interesting, and just to be sure there is no pending Deploy at the top of your screen, right?
Yes
Attachments
2 months ago
I mean like this
Attachments
2 months ago
When did you assign that domain?
The recent deployment from 2days ago is likely what broke it, however I am not sure what triggered it, I didnt ask it to redeploy, I havent pushed anything in 8mo.
actually nvm, I tried redeploying after the issue was already present
2 months ago
could you try redeploying once more?
2 months ago
my original thinking was its some odd state your service might be in simply due to how old it is but I checked my own deployment from 11 months ago which I keep up for situations like these to compare, and domains are being provisioned just fine so I'm honestly stumped lol
2 months ago
i also checked if Railway's aware that the domain is assigned to your service by trying to assign it to my service, and it seems Railway does at least know the domain is assigned to your service. So that 404 status is very confusing
2 months ago
Nice! Glad that helped
2 months ago
Of course 🙂 Happy to help
Status changed to Solved dev • 2 months ago