24 days ago
Hello Railway Support,
I'm having trouble connecting my custom domain, jagsonhaven.com, to my JagsonHaven application.
My application works correctly through its default Railway URL, but the custom domain returns ERR_SSL_PROTOCOL_ERROR over HTTPS and 404 Not Found over HTTP.
I've checked the following:
- The custom domain is listed under Public Networking.
- The current CNAME target is
f1mapqkr.up.railway.app. - The
_railway-verifyTXT record is publicly visible and matches the value Railway provided. - Cloudflare SSL/TLS encryption mode is set to Full.
- Cloudflare Universal SSL is active.
- I've temporarily disabled Cloudflare proxying on the root CNAME.
- Railway still displays “Cloudflare proxy detected” without a green verification checkmark.
I've also removed and re-added the custom domain once, but the issue persists.
Could you please check the domain verification and TLS certificate provisioning status for jagsonhaven.com and advise what needs to be corrected?
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
Apologies for the trouble. We had an incident that stopped TLS certificates from being issued for new or changed domains, and it has since been resolved. You can see the full timeline here: TLS certificates not generating
Your domain now shows as verified on our side, its certificate has been issued, and requests to it reach your service over our edge. Please try loading it over HTTPS again.
Status changed to Awaiting User Response brody • 24 days ago
16 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 16 days ago