2 years ago
Recently I realized the production railway server goes down randomly throughout the day and show 503 error. What's going on? Can someone take a look?
My project ID is 99e122f7-a96e-42ba-95aa-325cd3e66c82
...
<h1 class="error-404">Nothing here... yet</h1>
<h1 class="error-503">Application failed to respond</h1>
<a href="https://railway.app"> Go to Railway </a>71 Replies
2 years ago
do you have any logs for when you get the error page?
what kind of app?
2 years ago
right but if your application was erroring and not responding, ideally there would be logs
```
Nothing here… yet
Application failed to respond
<a href="https://railway.app"> Go to Railway </a>
```2 years ago
that page is shown when your application doesn't respond
2 years ago
are these https requests? what am I looking at here?
The server soetimes works and sometimes doesn't without any changes from my side
2 years ago
do you have a custom domain?
2 years ago
I understand how it sounds but that does not rule out an issue with your app
2 years ago
it also does not rule out an issue with railway, but from experience it's more often an issue with the application
My other friends also have uptime problems with railway and have migrated to render
2 years ago
unfortunately working locally does not rule out an issue with the application either
2 years ago
do you have the edge proxy enabled?
2 years ago
it would be in the service settings
2 years ago
yes, but first, you said your domain provider was namecheap?
2 years ago
are you sure you are using the correct generated cname it gave you when you set it up?
2 years ago
I'm sorry but that answer does not instill confidence, I would like to ask for confirmation
2 years ago
you are using the generated cname, not the auto generated domain, correct?
2 years ago
go ahead and enable the edge proxy
2 years ago
wait and see if you continue to have issues
When should I check back in? Just tried postman and still have the same issue
2 years ago
what's the state of your deployment
2 years ago
I'm sorry but that's not a valid state
2 years ago
yes, please tell me it's state
2 years ago
it's deployment state
2 years ago
your app has exited
2 years ago
this would not be a platform issue
2 years ago
completed
2 years ago
first, let me correct myself, the edge proxy is not going to help here, I had asked you to make that change without enough information from you.
second, since this is an issue with your application I would recommend implementing error handing everywhere and verbose logging to help you narrow down the issue.
remember, railway only ever runs your code as-is, so if it's exiting that's something your app is doing, not the platform
2 years ago
the app exited with a non error code for (at this time) an unknown reason
2 years ago
I wish you the best of luck in your debugging endeavour
Is it possible it exceeded resource constraints? Is there some way to check for that?
2 years ago
you think your app could have exceeded 32gb of ram?
2 years ago
what do your memory metrics look like?
2 years ago
have you received any emails from railway that state you ran out of memory?
2 years ago
then it doesn't seem like that's the issue
What does completed mean? This deployment is "completed" instead of "active" but up and running, have healthy logs

2 years ago
Completed is when you exit using a 0 exit code. However, going to raise this to the team for investigation.
2 years ago
!t
2 years ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response angelo-railway • over 1 year ago
2 years ago
It does look to me like the app is restarting if I'm reading logs correctly, but doesn't seem like it's due to OOM or CPU based on the metrics graphs.
Can you confirm if this log line prints when the app starts: "DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): huggingface.co:443". That could also explain why the status is being updated to "Completed". As Brody suggested, I would also encourage you to add some more verbose logging and error handling to help track down the issue, even starting with a clear debug line for when the app starts so it's easier to see when/if it restarts.
Status changed to Solved Railway • over 1 year ago
2 years ago
This thread has been marked as solved automatically due to a lack of recent activity. Please open a new thread if you require further assistance. Thank you!







