2 months ago
Service: Tasker
Service ID: 3e97ce52-d411-457f-840b-18ce367298f3
Project: sweet-reflection
Environment: production
Issue: Service domains return "can't find the server" despite successful deployments.
Tried domains: tasker-production-cbd4.up.railway.app, tasker.up.railway.app
App is running (gunicorn listening on 0.0.0.0:8000) but domain routing is broken at Railway infrastructure level.3 Replies
2 months ago
Your service has two Railway-provided domains assigned: tasker-production-cbd4.up.railway.app and tasker-production-86cf.up.railway.app. The domain tasker.up.railway.app is not assigned to any of your services, which is why it does not resolve. Also, ensure your application is listening on the PORT environment variable provided by Railway rather than a hardcoded port, or set the PORT service variable to 8000 to match your gunicorn configuration.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
how to fix this ?
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open noahd • about 2 months ago
yashv026
how to fix this ?
2 months ago
As the bot said, ensure you application is listening on the PORT env var, or set the PORT service variable to 8000.
You can also follow this troubleshooting docs: https://docs.railway.com/networking/troubleshooting/application-failed-to-respond
Status changed to Solved medim • about 1 month ago