4 months ago
Hi Railway team,
Custom domain www.tendit.io has been stuck returning HTTP 502 with
x-railway-fallback: true for 12+ days.
All verifications pass cleanly:
- Project ID: 7de24dd0-745a-4db3-9799-216f24f09618
- Service ID: eae50c1e-3c51-4f52-a44c-19b407d499a7
- Environment ID: ee89b0e3-d0e7-4c9d-b262-ec64583294b4
- Custom Domain ID: 702fe920-ae71-4e5e-83ad-e7e6fe77fb66
- CNAME
www.tendit.io → yjxuwvpr.up.railway.app— PROPAGATED ✓ - TXT
_railway-verify.www.tendit.io— added and propagated ✓ - Target Port: 5000 (matches app)
- Deployment status: SUCCESS
- App responds 200 on tendit-ai-production.up.railway.app
Recent request IDs showing the fallback:
- 1UP8ORhHSlmwzS5VnpoFkQ (us-west2)
- EMWhxIujTvaRQbuZ0_TJvA (us-west2)
I've tried: delete-and-readd, restart deployment, customDomainUpdate
via API, adding TXT verification — none have cleared the fallback state.
Please kick the domain verifier and force the certificate binding /
edge routing refresh for this domain.
Thanks!
Pinned Solution
4 months ago
I'd try changing the port to an arbitrary number (eg, 4100) and redeploy. Make sure to use the PORT variable.
1 Replies
4 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 4 months ago
4 months ago
I'd try changing the port to an arbitrary number (eg, 4100) and redeploy. Make sure to use the PORT variable.
Status changed to Solved 0x5b62656e5d • 4 months ago