2 months ago
Hello,
My React application (Create React App/Craco) is successfully deployed and running inside the container on port 5173. The custom lightweight Node.js HTTP server is explicitly binding to 0.0.0.0:5173 and internal logs show that the application is online and healthy.
However, accessing my custom domain smart-asistent.com consistently results in an "Application failed to respond" error from the Railway gateway.
Here are the latest Request IDs for reference:
- vIJNE0yHT1isB-kZ0-QtfA
- BpcEMMj5RmWQsUI855So4g
The application logs confirm that the container is healthy and listening, but the platform router seems completely unable to forward the traffic to port 5173. Could you please check the gateway routing table for this project and perform a hard reset on the service domains?
Thank you.
6 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
Make sure your custom domain is mapped to the port 5173 in your service settings > networking.
darseen
Make sure your custom domain is mapped to the port 5173 in your service settings > networking.
2 months ago
Hi darseen, thank you for the fast reply! Yes, I have already explicitly mapped smart-asistent.com to target port 5173 in the service settings -> networking. The custom Node.js HTTP server inside the container is also verified to be listening on 0.0.0.0:5173.
Despite this, the gateway still returns "Application failed to respond" with the Request IDs mentioned above. It feels like a platform-side routing glitch or a stuck cache on the gateway router. Any thoughts on how to force a hard reset on the router for this service domain?
2 months ago
In that case, I would try to change the port to an arbitrary value (3000 for example), and map it to the domain. It's also recommended that you set up a PORT env variable in your service settings > variables.
darseen
In that case, I would try to change the port to an arbitrary value (3000 for example), and map it to the domain. It's also recommended that you set up a `PORT` env variable in your service settings > variables.
2 months ago
Thanks for the suggestion! We actually tried switching ports earlier, but due to multiple staged changes, Railway hit us with a "You have reached the limit for service domains per service" error on this Free plan. Since the controller seems stuck on the platform side, we are hesitant to push more port variables manually right now. We are hoping a Railway staff member can step in and perform a hard reset on the gateway routing table for this project.
2 months ago
Update: I managed to bypass the custom domain issue by generating a default Railway domain. The application is now live and running at smart-asistenttest1-frontend-production.up.railway.app, which proves the Node.js server config and build are 100% correct.
However, the styles (CSS) are broken because the custom domain smart-asistent.com is still trapped in the gateway routing bug and returns "Application failed to respond". Can a staff member please flush the routing table for smart-asistent.com so the custom domain can connect properly?
2 months ago
Still facing the same issue today. The default Railway domain is up, but assets/CSS are completely blocked because the custom domain routing remains stuck. Any Railway staff available to look into this and clear the gateway table? Thank you!