Application failed to respond for a few seconds after deploy
I have this recurring issue where every time I do a deploy, its successful, but when I check the domain, I get a
Application failed to respond message from Railway.
I keep refreshing a couple of times, and then it finally loads the newly deployed app. It's as if the deployment is published before it is ready, even though the logs indicate that the server is listening
Any idea what is going on? I tried playing with the health check settings, but it didn't help.16 Replies
Project ID:
660f85e6-f8fa-467e-8c57-d93f8eb3304e660f85e6-f8fa-467e-8c57-d93f8eb3304e
By any chance, are you using volumes with your project?
yes, I am
Solution
That would be why.
There will be a slight delay from successful deployment to active site
I should also note that I always also get an email that the service crashed after a successful deployment
I dont know if its related
This is from the docs on volumes
I see,
It is a safeguard for data integrity
makes sense. Is the email that i receive part of that caveat?
It’s possible. It could just be a false alarm
As long as the service is successfully deployed and running I would say it’s safe to ignore those if it’s only at a redeploy and you are testing to make sure it is running
But I will bring it to the attention of the team
oh ok.
So for now, there is no workaround to the volumens caveat?
I guess it will be addresed further down the line?
There is no workaround at this time, unless you were to use s3 or r2 for storage if files