2 years ago
I have a nestjs app. I switched to the v2 runtime in Settings and now the healthcheck fails. The weird part is that the app starts normally and it looks like it works. I switched back to the legacy runtime but now the build takes much more time.
ⓘ Deployment information is only viewable by project members and Railway employees.
7 Replies
2 years ago
There's a bug with the v2 runtime where your app needs to listen on the IPv6 host :: to pass a health check.
2 years ago
Will this be fixed? Should I wait for a fix or should I update the application?
2 years ago
Yes sorry I should have mentioned that this absolutely will be fixed, my bad.
However I don't have an exact ETA, but depending on what your app is, having it listen on the host :: could be an extremely simple change that I would go ahead and make since it's still going to work when the fix comes out.
What kind of app do you have?
2 years ago
Running a rails app with puma, I just tried to update my 'BIND' environment variable to be '[::]' to bind to that address but for some reason the puma config is not picking it up 
2 years ago
Got it to bind to the [::] interface but still failing healthcheck
2 years ago
Update, health checks can now pass if your app only listens on 0.0.0.0 but if you have already changed it to :: there's no point in changing anything back as listening on :: has no known drawbacks.
jkogara, if you are still having issues with your app, please open a new post.
Status changed to Solved Railway • over 1 year ago