#Listening on 127.0.0.1 instead of 0.0.0.0. Running with gunicorn
49 messages · Page 1 of 1 (latest)
Project ID: 79f1c83a-6d2b-438b-83e7-222a04cc317a
@echo pike
- railway currently runs on the Google cloud platform, and the only region available at the moment is us-west1, not aws
- gunicorn listens on host 0.0.0.0 and Environment variable PORT by default
- you forgot to prefix the Procfile's start command with
web:
a Procfile with this should be fine
web: python manage.py migrate && python manage.py collectstatic --noinput && gunicorn mysite.wsgi
obviously adapting that for whatever name you use for your django app
we greatly appreciate your efforts to help but unfortunately this answers gets some things wrong, and in the interest of providing the most accurate help we can, I've had to remove this answer, but we hope you can continue helping people in the future!
its showing up in the build logs???
exactly
can you share your repo so i cant understand whats going on
after couple of minutes it's automatically failinh
please
email pls
check pls
i see whats wrong
- delete your Procfile
- for uniformity, use a lowercase 'r' in your railway.json file
- replace your railway.json with this
{
"$schema": "https://railway.app/railway.schema.json",
"build": {
"builder": "NIXPACKS"
},
"deploy": {
"startCommand": "python manage.py migrate && python manage.py collectstatic --noinput && gunicorn coverletter.wsgi",
"restartPolicyType": "ON_FAILURE",
"restartPolicyMaxRetries": 10
}
}
I just copied from this instruction
please do these things
testing now
just curious about something, can you send me a screenshot of the table at the top of your build logs please?
screenshot of the details tab please
seems like its using an old railway.json file, i think you may have bugged the service, can you please delete the service and remake it
trying now. But 100% it's using new one that you provided
no it's not
this is not the same railway.json that I gave you, look closer
this one is correct, but it is not the one railway is using, according to your screenshot of the details tab
have you set a custom build command in the service settings??
now rebuilding in the app
there we go, that looks good
OMG it's going further 😄 I'm trying to solve this around a week
damn I wonder how many deploys you have made that have failed in a week
railway gonna have to start billing for builder resources after this lmao
And it's crashed 
'''
please reference the railway django settings.py file on how to configure static files
https://github.com/railwayapp-templates/django/blob/main/mysite/settings.py