d700d7ec-2321-4589-9b7f-8277bb9bfdf8

Logs

Attempt #1 failed with service unavailable. Continuing to retry for 1m39s

Attempt #2 failed with service unavailable. Continuing to retry for 1m28s

Attempt #3 failed with service unavailable. Continuing to retry for 1m16s

Attempt #4 failed with service unavailable. Continuing to retry for 1m12s

Attempt #5 failed with service unavailable. Continuing to retry for 1m4s

Attempt #6 failed with service unavailable. Continuing to retry for 48s

Attempt #7 failed with service unavailable. Continuing to retry for 18s



1/1 replicas never became healthy!

Healthcheck failed!

I've tested the /health path locally and it works great!

Update: I've found the solution - it's to migrate to render.

our pricing and support is better than theirs 😉

You have mandatory "hEAltHcHecKs" that stop deployment dead in its tracks

it's not mandatory, it was something you set so you can always remove it

I never set it. Where would I remove it?

we don't set it automatically, it can be removed in the service settings

you need to be more specific. I looked in there multiple times and I couldn't find a way to turn it off

you can use the search bar!

search bar? What search bar? Are we talking about the same app?

The only search bar I see is in logs

the search bar at the top of the service settings

again, no way to turn this dogshit "feature" off

you set it in your railway.toml file

remove the setting from that file

which one?

healthcheckPath = "/health"
healthcheckTimeout = 100

path

are the only 2 settings that have the word health in them

no, it's still doing it!

you need to push the changes to GitHub

i did

what does the health check path say now?

same bullshit

I'm pretty sure I have never had this much difficulty deploying a node server to the cloud <:doge:951339002278055946>

hmmm I don't know what we could do better here, these are your settings

I promise you I would NEVER implement such a dogshit feature

the language is not needed

It wouldn't have been needed 30 minutes ago, or if it worked on the first try, but now I'm very frustrated

that is your railway.toml file and the platform is simply respecting your settings

I want my node server to WORK, and the platform isn't respecting that

it seems your configurations are preventing that, I'll check things out closer when in back at my laptop

Yea, yea, it's all MY fault. Railway is the MOST PERFECT, MOST USABLE, MOST INTUITIVE HOSTING APP OUT THERE

that's our goal!

looks like you have removed the health check!

and it took way too long because there's no "healthcheck on / healthcheck off" flag for some reason

Very bizarre design choices

You set the healthcheck path, if you dont want a healthcheck you don't set a path

I never set the healthcheck path

it was in your railway.toml file

healthcheck = on

was never in there

per your previous message -

healthcheckPath = "/health"

why would that turn the healthcheck on???

thats turning it on

why wouldn't it? you set it

lobotomized <:kekw:788259314607325204>

just trying to help point out how settings work

dear god the fucking env vars don't work <:kekw:788259314607325204>

BANKRUPTCY
BANKRUPTCY
BANKRUPTCY
BANKRUPTCY
BANKRUPTCY

you haven't set any?

RENDERRRRRRRRRR

env vars arent going to work on render either if you don't set any

!s