LetsEncrypt (our cert issuer) is having an active incident at the moment - https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3

Thank you for the quick update, is there any ETA for when this will be fixed? Or is this on their end.

It's on their end unfortunately, nothing we can do here. We're tracking this in https://status.railway.com/incident/1QD5978Z.

Unfortunate, I need this up tonight lol, got a meeting to show off some software via a website im hosting

Good news - the Let's Encrypt incident has resolved and your certificate is actively issuing right now. You should be up and running shortly, likely within a few minutes. If it doesn't complete on its own, click "Try Again" on the domain in your service settings.

@brody

It doesn't work for me. I tried adding again custom domain with One Click "Connect to Cloudflare" and my frontend will gets 525 error

https://frontend-production-cb26.up.railway.app/

Those warning signs don't explain what is the problem

project/580fd05e-2259-47b1-aeed-536409d60110/service/bfb64fb6-402e-448b-9eb6-b70736b9f318

I had to pause Cloudflare proxy and recreate records ;/

Feature request: I'd good if warning would say what is the problem

Glad you got it sorted! Cloudflare's proxy can interfere with certificate validation, so pausing it during setup is the right move. For the feature request about more descriptive warnings, feel free to post it on our feedback board so other users can upvote it.