3 months ago
I'm experiencing an issue with custom domain routing for my service.
Service Details:
- Project: Connect service (Bun/Hono app)
- Railway URL: connect-production-ba24.up.railway.app - works correctly
- Custom domain: connect.gainable.dev - returns 502
Configuration:
- Port: 3000 (correctly set in custom domain settings)
- CNAME target: 007tej75.up.railway.app (DNS verified and resolving correctly)
- Custom domain shows "Setup complete" with green checkmark
What I've tried:
- Redeploying the service
- Removing and re-adding the custom domain
- Toggling the port setting (3001 → 3000) to force refresh
- Verified DNS is pointing to the correct Railway target
Behavior:
- curl https://connect-production-ba24.up.railway.app/health → {"status":"ok"}
- curl https://connect.gainable.dev/health → 502 "Application failed to respond"
The app is running correctly on the Railway URL, but the custom domain proxy doesn't seem to be routing to the service.
Request ID examples: V8Rk1rl0QNaV-9k0jUJq2g, 7V0kP10BTsmsvHclw9P4nw
Could you please check the routing configuration for this custom domain?
Thanks!
5 Replies
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 3 months ago
3 months ago
Hey! I noticed your Railway URL is connect-production-ba24.up.railway.app but your CNAME is pointing to 007tej75.up.railway.app - those don’t match. Your CNAME should point to the same subdomain as your Railway service URL. Try updating your DNS to point to connect-production-ba24.up.railway.app instead. If that’s intentional (like pointing to a different service), then there might be a routing issue on Railway’s end and you’ll need staff to check the proxy config for those request IDs you provided.
3 months ago
I just follow the instructions when you create the custom domain; works for everything else - tried that too (connect-production-ba24.up.railway.app) didn't work either - see screenshot. The incorrect error you see below is from a previous try to set the custom domain. You can also see in the other screenshot that it says setup complete and that's pointing to 007tej75.up.railway.app - done the exact same process for a couple of other deploys; and they work - but for some reason this one doens't.
3 months ago
I think it's a routing issue on Railway’s end and need staff to check the proxy config.
3 months ago
Nothing wrong on our end, this would be a misconfiguration, so I'll let the community help you with it!
3 months ago
Could you solve this? 