The status for the most recent insident say resolved, but my deployments are still failing
shyam-habarakada
HOBBYOP

a month ago

Here is a snapshot. Trying to run diagnostics also appears to time out. Same symptoms as before while you were troubleshooting the issues.

image.png

Attachments

Solved$10 Bounty

Pinned Solution

vamshi9666
FREE

a month ago

check your settings and under the 'networking', you will see 'HealthChecks' . disable them or correct with right path

image.png

Attachments

5 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 1 month ago


vamshi9666
FREE

a month ago

check your settings and under the 'networking', you will see 'HealthChecks' . disable them or correct with right path

image.png

Attachments


vamshi9666

check your settings and under the 'networking', you will see 'HealthChecks' . disable them or correct with right path ![image.png](https://station-server.railway.com/attachments/att_01m16873z3ferbh8nvcdttd0qs)

shyam-habarakada
HOBBYOP

a month ago

I have mine set to / — and this hasn't changed.

Are you suggesting a workaround to the issue that is going on?

Thanks


shyam-habarakada

I have mine set to `/` — and this hasn't changed. Are you suggesting a workaround to the issue that is going on? Thanks

vamshi9666
FREE

a month ago

that means, railway is waiting for service to start and serving '/' route for a 200 response. can you share build logs and service logs too in .log format


shyam-habarakada
HOBBYOP

a month ago

I know, what I meant is, what changed in railway? My app has always been returning a 307 on the healthcheck URL it had, and now it looks like (and per railway docs) it is strictly expecting a 200. Did they start enforcing it or something? I don't recall getting a notice about a change though, so I am mainly curious here.


shyam-habarakada

I know, what I meant is, what changed in railway? My app has always been returning a 307 on the healthcheck URL it had, and now it looks like (and per railway docs) it is strictly expecting a 200. Did they start enforcing it or something? I don't recall getting a notice about a change though, so I am mainly curious here.

shyam-habarakada
HOBBYOP

a month ago

I see this other thread, also reporting that helthchecks are failing and that is a new issue. So it does look like soe enforcement actually did change on the railway side. So that makes sense https://station.railway.com/questions/healthchecks-failing-with-service-unava-8f8674eb


Status changed to Solved brody • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...