Skip to content
Custom-domain SSL: verified ownership but rate-limited or stuck issuing
raji-max
OP

a month ago

Hi, I am seeing two custom-domain SSL issues and would appreciate general guidance. I am intentionally omitting website addresses, account details, project/service IDs, and verification tokens for privacy. Please do not disclose those details in public replies.

Case 1: Ownership is verified and Railway now confirms the CNAME is propagated. Certificate status is CERTIFICATE_STATUS_TYPE_ISSUE_FAILED, with “Let’s Encrypt rate limit reached. Please wait before retrying.” and retryable: false. Authoritative DNS and public resolvers return the expected CNAME, and the ownership TXT is present.

Case 2: Ownership is verified, but the certificate remains CERTIFICATE_STATUS_TYPE_ISSUING with no reported error. A browser reaches the Railway-hosted site but receives the fallback *.up.railway.app certificate, causing a hostname mismatch. Railway’s DNS status has reported an older target, so stale DNS or propagation may still be involved in this second case.

The Railway-generated URLs work over HTTPS. I have seen similar reports posted today.

Is there a known certificate-issuance issue? For a rate-limited domain, how can we identify the exact limit and Retry-After time, and will issuance resume automatically or require a manual retry? For a domain stuck issuing, what checks distinguish stale DNS from a stalled certificate workflow?

I am avoiding repeated deletion/re-creation and retries. Please provide general troubleshooting steps, or a private route for any account-specific investigation. Thank you.

Solved

4 Replies

Railway
BOT

a month ago

We checked the two affected custom domains on your account without naming them here, and there is no current status-page incident covering certificate issuance.

For the rate-limited domain, ownership is verified and the traffic CNAME is propagated, so the failure is the Let's Encrypt rate limit rather than DNS. The status we can read reports only that the limit was reached; it does not include which specific limit or a Retry-After time. Because the certificate is in a failed state rather than still issuing, we cannot confirm that it will retry on its own, so avoid repeated retries or deleting and re-adding the domain, since each new attempt counts against the same limits.

For the domain stuck issuing, a fresh public lookup returns the correct CNAME target, while our own DNS check last recorded the older target, so the dashboard's DNS reading is stale compared with public DNS. The certificate is still waiting on authorization, and that status alone does not tell us whether issuance is progressing or has stalled. The practical way to separate the two is to compare your authoritative DNS answer with what the dashboard reports: once the dashboard shows the CNAME as propagated and the certificate still sits at issuing, stale DNS is no longer the explanation.


Status changed to Awaiting User Response Railway • 26 days ago


raji-max
OP

a month ago

Thanks. Could you escalate both cases to your networking/certificate team? For the failed certificate, please confirm how issuance should be restarted once the rate limit clears. For the issuing certificate, please refresh the stale DNS check and investigate authorization if it remains stuck. Please continue keeping the domains and account details private.


Status changed to Awaiting Railway Response Railway • 26 days ago


raji-max
OP

25 days ago

Can you please help me?


Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

25 days ago

Apologies for the trouble, this related to an account issue today with our TLS certificate provider. We are back now, please click try again where the error arose in the UI. If this button doesn't regenerate it, please try removing the domain and adding again.


Status changed to Awaiting User Response Railway • 25 days ago


Status changed to Solved dizzydes90 • 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...