a month ago
I have a custom domain www.fiveaccountsbudgeting.com that is correctly CNAMEd to 1zv7gb9g.up.railway.app, but there is a DNS routing issue preventing TLS termination.
Current State:
CNAME record: www.fiveaccountsbudgeting.com → 1zv7gb9g.up.railway.app ✓
1zv7gb9g.up.railway.app resolves to: 69.46.46.77 (has valid TLS cert for www) ✓
www.fiveaccountsbudgeting.com resolves to: 18.204.152.241 (does NOT terminate TLS) ✗
Problem: Public DNS for www.fiveaccountsbudgeting.com is resolving directly to 18.204.152.241 instead of following the CNAME to 1zv7gb9g.up.railway.app (69.46.46.77). This causes TLS handshake failures when accessing the custom domain.
What I need: Fix the edge/DNS routing so that www.fiveaccountsbudgeting.com resolves to the TLS-terminating IP (69.46.46.77 or another edge IP with a valid cert), not to 18.204.152.241.
Project Details:
Project: ravishing-charisma (ec022ff7-faaf-4961-952f-e5af4ce7fbee)
Environment: production (3f32e9b9-3239-43b5-80f9-1ae43acd68ca)
Service: five-accounts-budgeting (c6fd2905-4ea8-40db-88b8-96ad31eafa34)
Domain: www.fiveaccountsbudgeting.com
Current CNAME target: 1zv7gb9g.up.railway.app
Pinned Solution
a month ago
I"m able to acecss your site just fine. Try using a different device or network, and set your DNS to use 1.1.1.1 if possible.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Update: This appears to be a Railway edge/DNS routing issue that needs platform-level investigation. The DNS is not following the CNAME to the TLS-terminating edge.
Current specifics:
CNAME correctly points to 1zv7gb9g.up.railway.app (69.46.46.77 — has valid TLS cert)
But www.fiveaccountsbudgeting.com resolves to 18.204.152.241 (no TLS cert)
This is preventing HTTPS access to the domain. If anyone from Railway's team sees this or has insight into custom domain edge routing, please help!
a month ago
I"m able to acecss your site just fine. Try using a different device or network, and set your DNS to use 1.1.1.1 if possible.
Status changed to Solved 0x5b62656e5d • about 1 month ago