8 months ago
Why all my requests are dropping? testing in dev they are working fine but when i upload to railway, it does not work
35 Replies
8 months ago
Error 499 is Nginx
8 months ago
Your project is public only if you set it to public
8 months ago
The reason is because Nginx doesn't do dynamic DNS
8 months ago
Restart your Nginx service to register the restarted services that connect to it
8 months ago
If you want dynamic DNS use Caddy
8 months ago
it's not limited to nginx, in this case our proxy returned 499, because the client making the request abruptly closed the connection mid way through.
8 months ago
and in case you are curious, no we do not use nginx to proxy traffic for user applications
8 months ago
oh my google AI overview has lied to me
8 months ago

8 months ago
why would a status code be specific to nginx lol
8 months ago
why not
8 months ago

8 months ago
it firmly believes that this is Nginx specific
8 months ago
AI lies
8 months ago
Often
8 months ago
OP is not using nginx, we have returned 499
8 months ago

8 months ago
Why is railway using an ngix specific return code smh my head ||/s||
8 months ago
nginx might have used it first, but we aren't the only ones
8 months ago
glad to hear you got it working!
8 months ago
some apps require some little tuning before being able to be deployed to Railway, this docs page also helps alot: https://docs.railway.com/reference/errors/application-failed-to-respond
8 months ago
@Blakes can I mark this thread as solved?
8 months ago
!s
Status changed to Solved medim • 8 months ago
