2 months ago
Application failed to respond
This error appears to be caused by the application.
If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.
If you are a visitor, please contact the application owner or try again later.
Request ID:
o31OGBKEQbSLBTWF2JZdWA
3 Replies
2 months ago
Your application's logs show it starts a wrapper listening on port 8080 that proxies to an internal target on port 18789, but if that internal target isn't actually running, requests will fail with a 502. Check your deploy logs for any errors from the underlying process on port 18789, and ensure your domain's target port matches the port your app is serving on (8080 based on logs).
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
what to do?
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Open chandrika • 2 months ago
2 months ago
Make sure that your application is listening on IPv4 instead of v6 (use 0.0.0.0 instead of ::), and that the port your application is listening to is the same port your URL is mapped to.
Additionally, check if your deployment logs have any errors. If you do, send them here.