Railway failing to deploy on non-functional change and network requests failing to reach server
parth220
PROOP

3 months ago

I use Railway for infrastructure for my backend, Supabase with Postgres for my database, and Vercel for my frontend.

I just made a non-functional comment change on my main branch and pushed it, causing a redeploy for my Railway.

Suddenly, all API requests from my frontend to my backend are timing out.

However, suddenly no request from our web FE to our Railway BE are being received, and therefore are timing out on the FE.

Database is healthy

On local dev set up, using the exact same env vars production, everything works perfectly as intended.

I testing a public endpoint on my backend via browser, which is on api.hud.so. Works perfectly fine.

I hit it via a curl request, works perfectly fine.

When I hit it from my Vercel-hosted frontend Next.js web app, I never see the requests propagate through to my backend server logs, then they just time out.

Finally, I reverted the commit and now the project wont deploy.

Would love any insights here.

Solved

4 Replies


jack
PRO

3 months ago

Looks like it may be an issue related to a recent incident mentioned in another post (https://station.railway.com/questions/failed-to-start-deployment-a4269225), supposedly the team is investigating it and some users are reporting it working in some regions.


drmarshall
PRO

3 months ago

Also experiencing this network outage in production. It's approaching 1 hour without acknowledgement now.


jake
EMPLOYEE

3 months ago

The OP project looks deployed?


Status changed to Awaiting User Response Railway 3 months ago


Railway
BOT

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 2 months ago


Loading...