Not logging in to railway for a while breaks the site?
jonathan-neugber
HOBBYOP

23 days 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.

I have been quite busy with work and did not check in on railway.

I got notified by potential customers that the website to request commissions showed this warning.

Just logging in to railway fixed this. The last deployment was 8 months ago and there are no error logs.

Is this expected behavior? I mean I have been paying monthly and it turns out the website was not serving anything but a 502.

$10 Bounty

5 Replies

Status changed to Awaiting Railway Response Railway 23 days ago


Status changed to Open Railway 23 days ago


There are ongoing incident right now, the railway team had to pause deployments for trial, free, and hobby plan


jonathan-neugber
HOBBYOP

23 days ago

That seemingly was the case for a longer period of time and has been and reported to me before the incident.


23 days ago

It was probably some blip, it's not expected behavior.

Just to double check, I suggest you redeploy your service since last deploy was ~8 months ago.


jonathan-neugber
HOBBYOP

23 days ago

So I think the reason was that at some point some regions stopped responding but one still worked. I still think it's not expected behavior to have to redeploy every couple months to ensure a static website keeps working


jonathan-neugber

So I think the reason was that at some point some regions stopped responding but one still worked. I still think it's not expected behavior to have to redeploy every couple months to ensure a static website keeps working

22 days ago

You're not supposed to redeploy your app every X months. It's just that with the current info you provided, my guess is that you were affected by a past reported incident that went unnoticed by you. It's very rare for incidents to affect networking/workloads, so you should be fine with your long-running static app.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...