Flask app returns 502 despite successful gunicorn startup
juliaklineai
HOBBYOP

4 months ago

My Flask/gunicorn app deploys successfully and starts cleanly (I can see "Listening at 0.0.0.0:8080" in deploy logs and "DATABASE: init_db() succeeded"), but every HTTP request returns a 502. I've tried: binding to $PORT explicitly in railway.toml, hardcoding port 8080, using a Procfile, and the app passes its own /health check locally. The app has been deployed at episodeengine.com. Project ID: 329e2f02-6deb-48c4-bf09-63987aede0fc.

Solved$10 Bounty

Pinned Solution

Something I'd try is to explicitly make your application listen on port 3000 and set the port your domain si mapped to on 3000 as well.

Then access the link from an incognito browser to minimize caching issues.

3 Replies

Status changed to Awaiting Railway Response Railway 4 months ago


Something I'd try is to explicitly make your application listen on port 3000 and set the port your domain si mapped to on 3000 as well.

Then access the link from an incognito browser to minimize caching issues.


xmrafonso
FREE

4 months ago

Additionally, are there any errors/logs that could be relevant?


Status changed to Awaiting User Response sam-a 4 months ago


0x5b62656e5d

Something I'd try is to explicitly make your application listen on port 3000 and set the port your domain si mapped to on 3000 as well. Then access the link from an incognito browser to minimize caching issues.

juliaklineai
HOBBYOP

4 months ago

That totally worked! Thank you SO MUCH. I sure wish I'd asked here before dinking around alllllllll daaaaaaaaay with this thing.


Status changed to Solved juliaklineai 4 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...