a month ago
Custom domain sign.foraker.ai is verified/green in networking settings but returns 502 with x-railway-fallback: true. The auto-generated Railway URL (documenso-app-production-849e.up.railway.app) works fine. Edge node showing: railway/us-east4-eqdc4a. Service is deployed in US West. Please check the routing table for this custom domain.
4 Replies
Status changed to Open Railway • 30 days ago
a month ago
Is your custom domain URL mapped to the same port your app is listening on?
darseen
Is your custom domain URL mapped to the same port your app is listening on?
a month ago
Yes, the custom domain is mapped to port 3000 and the app is confirmed listening on port 3000. The auto-generated Railway URL (documenso-app-production-849e.up.railway.app) works fine on port 3000. The issue is specific to the custom domain routing.
a month ago
he generated *.up.railway.app domain works, this appears to be a Railway edge routing/cache issue for sign.foraker.ai, likely requiring a routing table refresh or propagation fix on the platform side.
a month ago
Fixed the DNS on our end. The incorrect A record was replaced with a CNAME pointing to lxefiuce.up.railway.app (DNS only, no Cloudflare proxy), and we removed a domain conflict with Vercel.
Current state:
sign.foraker.ai shows green/verified in Railway Networking (Port 3000)
The auto-generated Railway URL loads correctly
sign.foraker.ai still returns "Application failed to respond" with no errors in deploy logs
Based on this, it does seem like a routing table issue on Railway's end. Do you know if there's a way to escalate this or force a routing table refresh for the custom domain?
Thanks so much for your help!
Status changed to Solved 0x5b62656e5d • 21 days ago