a month ago
Subject: Custom domain SSL certificate not provisioning — www.kotelnikov-tutor.ru
Hello Railway Support Team,
I am writing regarding a persistent SSL certificate issue with my custom domain on Railway.
Project: triumphant-blessing
Service: web
Custom domain: www.kotelnikov-tutor.ru
Railway internal URL: web-production-aa92f.up.railway.app
Situation:
The application works perfectly via the Railway internal URL. DNS propagation is fully complete — all global DNS servers resolve www.kotelnikov-tutor.ru to the correct CNAME (verified via dnschecker.org). Both the CNAME and TXT verification records are confirmed with green checkmarks in the Railway dashboard.
However, the domain times out in the browser (ERR_TIMED_OUT) and does not load. The Railway dashboard shows the domain as verified, but the SSL certificate does not appear to be provisioning.
History:
This issue began after the service was temporarily suspended due to a billing gap. Upon resumption, Railway assigned a new internal CNAME address. We have since updated the DNS records multiple times as Railway regenerated the domain verification records. The current DNS configuration is correct and propagated, but the SSL certificate has never successfully issued for this domain.
What we have tried:
— Updated CNAME record to the current Railway address
— Verified TXT record is present and confirmed
— Deleted and re-added the custom domain in Railway settings
— Cleared DNS cache on client machines
— Waited 24–48 hours after each DNS change
— Confirmed the site loads correctly on the Railway internal URL
Suspected cause:
We believe the SSL certificate issuance (via Let's Encrypt) is failing, possibly due to rate limiting caused by the repeated domain deletion and re-addition cycles, or due to a provisioning issue on Railway's side.
Request:
Could you please manually trigger SSL certificate provisioning for www.kotelnikov-tutor.ru, or investigate why the certificate is not being issued despite successful DNS verification?
Thank you very much for your help.
Best regards,
Ilya Kotelnikov
4 Replies
a month ago
Your custom domain's SSL certificate is valid, DNS is fully propagated, and the edge is serving traffic with a 200 response, so the domain is working correctly from our side right now.
a month ago
This thread has been marked as private.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your custom domain's SSL certificate is valid, DNS is fully propagated, and the edge is serving traffic with a 200 response, so the domain is working correctly from our side right now.
a month ago
The Railway bot confirmed the SSL certificate is valid and DNS is propagated with a 200 response from your edge. However, the domain still times out (ERR_TIMED_OUT) in the browser from multiple devices and networks, including mobile data. The Railway internal URL works perfectly. Could you check if there's something blocking traffic at the edge level for this specific domain?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We've looked into this from our side and haven't found anything on the Railway platform that explains what you're seeing, so working it out means digging into your specific setup.
That's exactly what the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
The domain is working fine, and accessible on my end. Try to access it using a VPN, or a different device/network. This might be just a caching issue.