2 months ago
I had a deployment crash earlier because I canceled it before it was done -- it was in the late stages of deployment and I should have waited in hindsight.
Now, ever since this occurred (roughly 4 hours ago) my website has been experiencing heightened 502 errors and constant in/out connection issues and sluggish loading.
There are no actual error logs that I'm seeing, and absolutely nothing changed on my end between now and before these 502 errors started (other than the crashed deployment event), and I have already tried pushing multiple fresh deployments (all successful) with no change in the 502 error rate.
How can I resolve this?
Attachments
3 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Bumping for any assistance with this
2 months ago
still an issue. BUMP
2 months ago
Sorry for the delayed response - I was investigating while you pinged again. Your service is healthy now - all requests are returning successfully since the last container restart. The 502s throughout the day were caused by your container repeatedly crashing and restarting, with each restart producing a burst of connection failures at the proxy level. This pattern suggests your application may be hitting resource limits (memory or CPU) under load, possibly from the volume of concurrent WebSocket connections. You can check your service metrics in the Observability tab to see if memory usage was climbing before each crash.
Status changed to Awaiting User Response Railway • 2 months ago
2 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 • about 2 months ago