2 months ago
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:
DXdBfi4ISVKvFVah7fhULg
4 Replies
2 months ago
The "Application failed to respond" error means our edge proxy cannot reach your application, typically because it is not listening on the correct host and port. Your "taskmanager" service shows a successful deployment but no runtime logs, which suggests it may not be starting or binding correctly. Ensure your application binds to host 0.0.0.0 and uses the PORT environment variable that we inject automatically, and also verify that the target port on your domain matches the port your app listens on. See our troubleshooting guide for language-specific examples.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
still same issue.
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:
jlZfR-_hR3iv27DeYqdHTg
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open Railway • about 2 months ago
Status changed to Solved ian-jefa • about 2 months ago
