Subject: Service domain stopped routing traffic EDIT: solved - port mismatch
afriendofblue
HOBBYOP
14 days ago
Details:
- Service: robust-commitment (backend API)
- Service domain:
robust-commitment-production-4c69.up.railway.app - Issue: Service domain was routing traffic and working correctly until approximately 19:50 UTC today (2026-05-08). Login was successful via this domain. Now the domain returns
net::ERR_FAILEDwith no response. - What changed: Only the service domain port configuration was modified (removed
:8000port specification from the service domain config). The backend service itself has not been redeployed. - Current state: The backend service is running and healthy. The internal domain
robust-commitment.railway.internalworks. Only the public service domain is broken. - Environment: Production (ID: 532a1146-b02c-4a20-9261-3ddf91be77f6)
- Project: proud-connection
1 Replies
Railway
BOT
14 days ago
Your robust-commitment service shows a successful deployment and the Railway-provided domain is still attached, so the issue is the target port configuration on that domain. When you removed the :8000 port specification, the domain lost its routing target. You can fix this by clicking the edit icon next to the domain in your service's Settings under Public Networking and setting the target port back to 8000 (or whichever port your backend is listening on). More details on target ports are in our Working with Domains docs.
Status changed to Awaiting User Response Railway • 14 days ago
Status changed to Solved afriendofblue • 14 days ago