a month ago
Hello, I’m having an issue with my Railway service.
The deployment shows SUCCESS, but whenever I restart the service, it runs for a few seconds and then crashes. Before this happened, the service was working normally. I restarted it from the Railway console after following a tutorial, and since then it keeps crashing after every restart.
Could you please check the service and let me know what is causing the crash? I also want to make sure that my existing data and configuration files have not been deleted or lost.
Thank you.
9 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month 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:
VjbSTl34TeO0sKDhss7a6g
Go to Railway
a month ago
Would you mind sharing your logs?
You can do so by clicking on the service, clicking on the Deployment and clicking on the "Deploy Logs" tab, or clicking "View Logs" directly
dev
Would you mind sharing your logs? You can do so by clicking on the service, clicking on the Deployment and clicking on the "Deploy Logs" tab, or clicking "View Logs" directly
a month ago
yes sure
dev
Would you mind sharing your logs? You can do so by clicking on the service, clicking on the Deployment and clicking on the "Deploy Logs" tab, or clicking "View Logs" directly
a month ago
INFO - Remove Inbound User Avesta.test due to expiration or traffic limit
dev
Would you mind sharing your logs? You can do so by clicking on the service, clicking on the Deployment and clicking on the "Deploy Logs" tab, or clicking "View Logs" directly
a month ago
Attachments
a month ago
how to solve this?
a month ago
please solve my problem
Status changed to Solved nimakarimi1592n-droid • about 1 month ago
a month ago
I was eating :/
Two issues:
- Multiple things are starting on the same port, causing conflict
- You are missing a configuration file, you can solve this depending on how you're deploying:
- If you're using a custom Dockerfile, just add the config file in your repository and move it to the right place
- Or if you aren't using a Dockerfile and deploying straight from GitHub, place the config in your repo and add a custom start command that'll move the file to the right place and start your app
- If you're deploying directly from a docker image, you either need to make a more complex custom start command that'll create the config file on launch or you should move to one of the above 2 methods
Status changed to Open Railway • about 1 month ago
