- My Django service and PostgreSQL database service are both within the 'production' environment
14 days ago
- My Django service and PostgreSQL database service are both within the 'production' environment. - The PostgreSQL database service is active and shows "Deployment successful". - The DATABASE_URL environment variable in my Django service is correctly set to: postgresql://postgres:oKdvFTjcGtCqaGhgyvgIgULrYLqtbwgR@postgres.railway.internal:5432/railway
- My Django settings.py is configured to use this DATABASE_URL. - My Procfile's release command runs python manage.py migrate --noinput && python manage.py collectstatic --noinput
. - I have already tried the following troubleshooting steps: - Deleting and recreating the PostgreSQL database service. - Ensuring the "Pre-deploy Command" field in the Django service settings is empty. - Triggering multiple deployments via both the UI and railway up
CLI command. Despite these steps, the error persists, preventing my application from connecting to the database and deploying successfully. It appears to be an internal networking or DNS resolution issue within the Railway platform for my project. Could you please investigate this issue from your end?
1 Replies
14 days ago
Hey there! We've found the following might help you get unblocked faster:
🧵 Internal Networking Issue: Prometheus Cannot Connect to Django App Despite Correct Configuration
🧵 Railway Support Request - Internal Database Connection Failure
If you find the answer from one of these, please let us know by solving the thread!