Skip to content
TLS certificate rate limit on verified custom domains
dark04phoenix
OP

a month ago

Hello,

I need help with TLS certificate issuance for the tlt-transport service.

Custom domains:

Both domains are connected to Railway and the DNS records have already propagated correctly.

Current DNS configuration:

  • Root domain: ALIAS to the Railway target
  • www: CNAME to the Railway target
  • Railway verification TXT records are present

I verified the records using the authoritative Vimexx nameserver, Cloudflare DNS (1.1.1.1), and Google DNS (8.8.8.8).

The application itself is deployed and working correctly at:

https://tlt-transport-production.up.railway.app/

However, Railway now shows the following error for both custom domains:

“Failed to issue TLS certificate — Let’s Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried.”

The DNS configuration is stable now and I have not been repeatedly changing the records.

Could you please check:

  1. Which Let’s Encrypt rate limit has been reached?
  2. When certificate issuance can safely be attempted again.
  3. Whether Railway will retry automatically when the limit resets.
  4. If not, what exact manual action I should take after the reset.
  5. Whether certificate issuance can be retried or assisted from Railway’s side.

I would prefer not to remove and re-add the domains unnecessarily, as I do not want to trigger further certificate attempts before the rate limit has cleared.

The production website is ready; valid TLS on the custom domains is the only remaining blocker.

Thank you.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 26 days ago


Status changed to Solved dark04phoenix • 26 days ago


dark04phoenix
OP

a month ago

Hello Railway Support,

This issue is not resolved. My thread was marked as "Solved" unintentionally, and I cannot find an option to reopen it.

Both tlttransport.nl and www.tlttransport.nl still show the Let's Encrypt rate-limit error, despite DNS being verified and propagated.

Could you please reopen this thread and set it to "Awaiting Railway Response"?

I still need assistance identifying when certificate issuance can safely be retried and whether Railway can trigger the retry without removing the existing domains.

Thank you!


Status changed to Awaiting Railway Response Railway • 26 days ago


Status changed to Solved dark04phoenix • 26 days ago


dark04phoenix
OP

a month ago

This support experience has been extremely frustrating and disappointing.

My production website has been unable to obtain valid TLS certificates for two verified custom domains due to a Let's Encrypt rate limit. Despite correct DNS configuration, I have received no actionable guidance, no confirmed retry date, and no assistance resolving the issue.

Even worse, my support thread keeps being marked as "Solved" without any response or resolution, despite me explicitly stating that the issue remains unresolved. I have not manually closed the thread.

My emails were automatically closed because an existing support thread supposedly handles the issue, yet that same thread is incorrectly marked as resolved. This creates an unacceptable support loop where customers cannot obtain meaningful assistance.

A production-blocking TLS issue should not be treated as resolved simply because an automated system changes its status.

I expect Railway to investigate this behavior, restore my support request to an active state, and provide clear technical guidance on safely issuing the certificates.

Please improve your support workflow. Customers should not have to fight the support system just to get an unresolved issue acknowledged.


Status changed to Awaiting Railway Response Railway • 26 days ago


Status changed to Solved dark04phoenix • 26 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...