24 days ago
Hi,
Reaching out for similar topic of TLS Certificate that is constantly failing after domain purchase of www.creaturoai.com. Could you please check and fix this bug. Certificate is not issued so far.
Thanks and I look forward hearing from you soon.
4 Replies
24 days ago
Apologies for the trouble. We had an incident yesterday 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 apex domain is verified, but its last certificate attempt failed because Let's Encrypt is currently rate-limiting that name after repeated failed attempts. Waiting until that rate-limit window clears is the only remedy, since a new attempt before then will fail the same way.
The www hostname is not added to any of your services, so no certificate can be issued for it until it is added as a custom domain on the service.
Status changed to Awaiting User Response Railway • 24 days ago
24 days ago
Thanks, the Let's encrypt limit rate cleared and after another try it failed again. Please advise.
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
The certificate for your www hostname has now been issued and is valid.
The root domain's latest attempt failed again with Let's Encrypt's rate limit, so the window had not fully cleared when it was retried. Each new attempt before it clears fails the same way. Your DNS for the root domain is verified and the challenge path is reaching us correctly, so leave it alone for a while before using "Try Again" on that domain in the service's Settings → Networking.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
A new certificate has now been issued for your apex domain, and the www hostname shows a valid certificate as well. Both were left exactly as they were, with the same DNS targets and verification records, so there is nothing to update in your DNS, and HTTPS is serving on each hostname. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.
Your DNS was correct throughout; the failure was not caused by anything on your domain.
Status changed to Awaiting User Response dizzydes90 • 24 days ago
Status changed to Solved dizzydes90 • 24 days ago