a day ago
Project id: 63935405-e7c5-456f-a142-dd384dd1d324
Service id: a908f77c-ae8e-4d5a-9d1b-5fca82d5ae2e
I deleted and re-added a custom domain because the previous custom-domain target became unreachable. Railway assigned a new custom-domain target, but the custom domain is still unreachable from my network.
Observed problem:
TCP connections to the assigned custom-domain edge target time out on both port 443 and port 80. No TLS handshake starts.
The Railway-provided domain for the same service works and returns HTTP 200, so the app/container itself appears healthy.
Chrome shows ERR_CONNECTION_CLOSED for the custom domain after around 10 seconds.
This looks like the custom-domain edge target is unreachable/stale or routed differently than the Railway-provided domain, not an app/container issue.
Could Railway staff check the custom-domain routing / edge assignment for this project? I can share the actual custom domain privately if needed.
6 Replies
a day ago
What domain are you using?
a day ago
I'm able to access the site just fine. Have you tried using a VPN or a different device/network?
Attachments
Thanks for checking. I also tested from mobile data and another phone, and the custom domain still does not work.
The Railway-provided domain works from the same networks:
atax-label-recognition-production.up.railway.app
But the custom domain fails with ERR_CONNECTION_CLOSED / timeout after around 10 seconds.
So it does not look like only my local Wi-Fi/network. Could Railway check whether the custom domain is correctly attached/routed on the edge side for this project?
a day ago
This may be related to your ISP or region. Unfortunately, Railway isn't able to do anything about this. Have you tried with a VPN?
a day ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 1 day ago