Failed to issue TLS certificate | Railway | Page 1

frigid saffron Apr 29, 2026, 9:16 AM

#

I got several of these when trying to set up a new domain:
"
Failed to issue TLS certificate
An internal error ocurred. Please retry or contact support.
"

After clicking try again a few times I got rate limited by lets encrypt.

Any issues with regards to certificate issuing at the moment?

I have moved the domain back to heroku for now.

half obsidianBOT Apr 29, 2026, 9:16 AM

#

Linked Railway resource: 78ca930f / 14c27cba / 5601103b

gilded pebble Apr 29, 2026, 9:25 AM

#

No issue with TLS provisioning that I know of, are you sure your DNS records were still in tact?

frigid saffron Apr 29, 2026, 10:03 AM

#

Yes they were.

API response for that domain reported it as verified:
{
"id": "d3595c4f-8029-4d97-bd75-b3d2cbc52b4f",
"domain": "estrodoxin.no",
"dnsTarget": "3olxabfg.up.railway.app",
"verificationToken": "railway-verify=7f10b128f500554653a23428d02592bd95ee97b617d2874239227c1ed5ff1b65",
"verified": true
}

#

Seems like a lot of people reporting the same problem

gilded pebble Apr 29, 2026, 10:43 AM

#

Alright, your intuition was correct, this was a platform error. Team is working on a fix now

#

they'll call an incident as well, sorry for the inconvenience

half obsidianBOT Apr 29, 2026, 10:44 AM

#

New reply sent from Central Station thread:

Having same issue!

You're seeing this because this thread has been automatically linked to the Central Station thread.

gilded pebble Apr 29, 2026, 10:50 AM

#

incident called: https://status.railway.com/incident/C4L89HAF

Railway Status

Current status and incident history for Railway services.

frigid saffron Apr 29, 2026, 10:51 AM

#

Thanks for the help. Will wait for the incident to resolve before trying again. We will probably have to wait until next week since we got rate limited by letsencrypt right?

gilded pebble Apr 29, 2026, 10:57 AM

#

Yea most likely 😬

gilded pebble Apr 29, 2026, 12:03 PM

#

should be resolved now

#Failed to issue TLS certificate