a month ago
We've just pointed a custom domain. It does resolve and the DNS records are showing as correct. But we keep getting a 'failed to issue TLS certificate' message and so the space is not secure when opened in any browser.
6 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
Are you using Cloudflare? If the proxy is turned on, it blocks Railway from issuing the TLS cert. Try setting it to 'DNS Only' and see if it goes through.
a month ago
The domain is www.altaxgroup.com, DNS is on GoDaddy (no Cloudflare/proxy involved). CNAME and TXT records are confirmed correctly added and resolving — I can load the site over HTTPS from some networks, but not others (e.g., cellular fails with ERR_CERT_COMMON_NAME_INVALID), which looks like inconsistent certificate propagation rather than a DNS problem.
I actually found another thread with the exact same "Failed to issue TLS certificate — Let's Encrypt rate limit reached", where a Railway moderator explained it's a moving 7-day rate-limit window and there's no manual override. Is that what's happening here too, or is there something else going on given it's already resolving correctly some of the time?
"Failed to issue TLS certificate
Let's Encrypt rate limit reached. Please wait before retrying.
This error cannot be automatically retried. Please check your DNS configuration or contact support."
a month ago
If CNAME and TXT records are confirmed as correctly added, It might take a few hours, maybe upto 24 hours for railway to issue certificate domain verification.
altaxservice
The domain is www.altaxgroup.com, DNS is on GoDaddy (no Cloudflare/proxy involved). CNAME and TXT records are confirmed correctly added and resolving — I can load the site over HTTPS from some networks, but not others (e.g., cellular fails with ERR_CERT_COMMON_NAME_INVALID), which looks like inconsistent certificate propagation rather than a DNS problem. I actually found another thread with the exact same "Failed to issue TLS certificate — Let's Encrypt rate limit reached", where a Railway moderator explained it's a moving 7-day rate-limit window and there's no manual override. Is that what's happening here too, or is there something else going on given it's already resolving correctly some of the time? "Failed to issue TLS certificate Let's Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried. Please check your DNS configuration or contact support."
a month ago
Unfortunately, if Let's Encrypt rate limit reached, there is nothing Railway can do about it. You just have to wait the 7 days rate limit window to reset.