Hello Railway Support,

I’m deploying a FastAPI backend on Railway and connecting it to my custom domain:

api.revapp.qd.je

The backend deployment is working correctly. The domain is also resolving to Railway, and the Railway TXT verification record is correctly configured.

I can successfully access:

https://api.revapp.qd.je

and the response is:

{"detail":"Not Found"}

This confirms that the request is reaching my FastAPI application.

However, Railway is showing:

Failed to issue TLS certificate

Let's Encrypt rate limit reached. Please wait before retrying.

This error cannot be automatically retried.

I initially configured the CNAME incorrectly, which caused several certificate issuance attempts. I have since corrected the DNS configuration and verified that the CNAME and TXT records resolve correctly.

Current DNS:

api.revapp.qd.je → CNAME → Railway domain

_railway-verify.api.revapp.qd.je → Railway verification TXT

DNS is hosted on deSEC.

Could you please check the TLS certificate issuance for api.revapp.qd.je and let me know when/how the certificate can be retried after the Let's Encrypt rate limit?

I have not changed the DNS configuration after correcting it, as I don't want to trigger additional certificate requests.

Thank you.