2 months ago
fireinspecthub.com and www.fireinspecthub.com returning 502 Bad Gateway for 13+ hours. app.fireinspecthub.com works fine on the same service.
Service ID: b2a39cdb-360d-47de-a728-f2daea983f4e
Project ID: 366c9df5-2086-40fc-bbd0-4c659c01593f
All three domains on same Railway service. All show Cloudflare proxy detected. Gunicorn starts clean — no errors in deployment logs. DNS is Cloudflare authoritative.
Working: app.fireinspecthub.com → f6gqii9t.up.railway.app
Broken: fireinspecthub.com → 0hp2tua8.up.railway.app
Broken: www.fireinspecthub.com → llsglpe1.up.railway.app
Issue started around the time of CDN changelog #0283 on March 27. Suspect new CDN routing is not handling root domain and www correctly.
16 Replies
2 months ago
Can you screenshot the custom domain configuration on Railway, and the requested DNS values?
fireinspecthub.com
0hp2tua8.up.railway.app
railway-verify=bacfcc3adba4500105e1ba035b2d817b94c2e2ee008d65a7e730349b8f63c86b
1lsglpe1.up.railway.app
railway-verify=7d9ed75e9b44c54c605adadb5f2fe753a7f89668f03b0cf90e34cfbd826f7c67
2 months ago
Can you try changing the target port of [www.]fireinspecthub.com to 3000?
2 months ago
leave app.fireinspecthub.com as is
2 months ago
do you know what port the landing page (root and www) listens on?
The app runs on Gunicorn and listens on $PORT which Railway sets automatically. The start command is:
python manage.py migrate && python manage.py collectstatic --noinput && gunicorn dispatcher_core.wsgi --bind 0.0.0.0:$PORT
The deployment logs show it started on port 8080. app.fireinspecthub.com works correctly on port 8000 in Railway settings
2 months ago
Cloudflare is masking Railway's error page
Hard to diagnose like that, perhaps temporarily disable Cloudflare proxied to see the actual error?
2 months ago
I still believe it may be a port mismatch
Disabled Cloudflare proxy on both domains. Now seeing Railway's own error page: 'Application failed to respond'
Request ID: aWs8ZsNDShOXDU6Jc9o55Q
This confirms it's a Railway routing issue not Cloudflare. The request is reaching Railway but Railway is not routing it to the application correctly.
2 months ago
This confirms that it's a port issue
2 months ago
3000 may not be correct, but 8000 isn't either
2 months ago
(this is not a Railway issue, just a configuration error)
ok, Port 8080 fixed it. Both fireinspecthub.com and www.fireinspecthub.com are now working. Thank you!