a0f3572b-295e-4a43-b776-ce352a4d0980

please use a non privileged port.

as for the health check failing, there's a bug with the v2 runtime where your app needs to listen on ipv6 to pass a health check, if I'm not mistaken you should be able to set a HOSTNAME variable to :: or change your start script to add a -H :: flag to next start, but I'm not sure if you are using next start so try the variable first

Thanks for the info

@Brody I used port 443 so the x-forwarded-port would be passed correctly, but now it thinks this is port 3000

So the above solution works, but the I18n plugin I use, checks the x-forwarded-port to apply certain redirects

https://github.com/amannn/next-intl/issues/987

railway does not set a x-forwarded-port header

instead of setting your PORT to 443, this is the correct solution

Hmm okay, hardcoding it for the port can be fine. But the same issue applies also for X-Forwarded-For I would think and then the originating client IP is lost.

pseudo code
if X-Forwarded-Proto == https { X-Forwarded-Port = 443 }

Check, thanks

A fix has been rolled out for this

What does the fix entail exactly?

I assume it would allow you to bind to a non-privileged port given the context of this thread

You can now use port 443

fwiw I still think binding to a non-privileged port is the more correct option