failing to reach application, backend django service
zach-d
HOBBYOP

2 years ago

docs said the 503 i'm getting is a port issue usually, but I'm a newbie not sure what I setup wrong attaching logs and repo

8 Replies


brody
EMPLOYEE

2 years ago

What's your current start command and where is it set?


zach-d
HOBBYOP

2 years ago

command: gunicorn backend.wsgi, set inside of my docker.yaml, should this be in a procfile instead? wasn't sure if that was necessary or not


brody
EMPLOYEE

2 years ago

docker.yaml is in no way applicable for the Railway platform, where else have you set a start command?


zach-d
HOBBYOP

2 years ago

only in the .yml currently, I had a procfile using the same command but was just trying to figure out docker so went with just that, so should I get rid of that and just set it in the procfile?


brody
EMPLOYEE

2 years ago

A Procfile is a heroku thing, while Railway does support them, it's best to use a railway.json file instead, here's an example -

https://github.com/railwayapp-templates/flask/blob/main/railway.json


zach-d
HOBBYOP

2 years ago

ok, switched over to the railway.json, seems to build/start, but still getting the 503? attached logs


brody
EMPLOYEE

2 years ago

Both your logs look good, perhaps you had checked the link before the new deployment went live so you where still shown the old error page, would you still be experiencing this issue?


Loading...