First time deploying with Railway - 502 Bad Gateway Error for Frontend
quitemason
HOBBYOP

13 days ago

Hello fine folk of the Railway community,

I'm trying to deploy 3 services from a monorepo (backend, frontend, event handler). It seems like the building is working properly. But when I generate a public URL for the frontend (I'm not expecting it to do anything amazing yet, but perhaps just load the main landing page), I'm immediately hit with 502 Bad Gateway error.

When it deploys, it looks like it's going onto port 5173. Not sure if it running it with dev is part of the problem or if it's always going to do that.

Then, it seems like it's not a port mismatch, if this is what I'm seeing in the service's configuration.

So yeah, I click the link and it immediately shows the 502. Am I missing something fundamental here? Apologies in advance, this is probably a super common kind of question. I'm excited to get this and the other services going! Let me know if I can provide any additional information. Thank you!

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 13 days ago


quitemason
HOBBYOP

13 days ago

Resolved it by myself. Needed to set my config to use a host of 0.0.0.0, and a port of 8080, updating the Railway UI accordingly. Works fine now.


Status changed to Solved quitemason 13 days ago


Loading...