Redeploying a Healthy Service caused it to go completely offline

a-dl

PROOP

5 months ago

I made a small push to an otherwise healthy service and all of a sudden I saw a spike of 502s. I found this odd but rolled back to a completely health deployment. Now, my service is completely unreachable (404) via both my custom domain and Railway's supplied public url.

Solved

4 Replies

a-dl

PROOP

5 months ago

Update: the service randomly became responsive again. Would love to understand what happened here.

a-dl

PROOP

5 months ago

Update: It's begun 502ing again

a-dl

PROOP

5 months ago

Looks like the 502s were on me for not handling timeouts but still confused about the 404 part, definitely less urgent.

angelo-railway

EMPLOYEE

5 months ago

All good to note, is everything working as expected on your end?

Status changed to Awaiting User Response Railway • 5 months ago

Railway

BOT

4 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 4 months ago

Welcome!