Skip to content
rostyre.digital stuck on “Issuing TLS certificate”
telem777-beep
OP

10 days ago

The custom apex domain rostyre.digital is attached to the rostyre-digital service (production, port 8080). Its Public Networking status is “Issuing TLS certificate.” The Railway service URL https://rostyre-digital-production.up.railway.app/ works over HTTPS; /health and all five printed QR landing pages returned HTTP 200 there.

Cloudflare has an apex CNAME to l4c6krd2.up.railway.app in DNS-only mode. Google and Cloudflare public resolvers return the same address for the apex and the Railway target. The Railway ownership TXT is publicly visible and matches the value provided at setup. No CAA or DS records were returned.

For TLS SNI rostyre.digital, the endpoint presents a Let’s Encrypt certificate whose SANs are *.up.railway.app and up.railway.app, so browsers reject it with NET::ERR_CERT_COMMON_NAME_INVALID. The error still reproduces now.

Could you check the latest ACME validation attempt for the existing custom-domain binding, share the exact error if any, and retry issuance on that binding if appropriate? Please keep the domain attached and URLs intact: QR codes are already printed. Thank you.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 10 days ago


sam-a
EMPLOYEE

10 days ago

Your domain's ownership verification has passed, its DNS record is propagated, and the certificate validation path reaches our edge successfully, yet the certificate is still sitting in the issuing state with no recorded error. We've started a fresh certificate issuance on the existing domain binding, so the domain stays attached and your URLs are unchanged; it may take a few minutes for the new certificate to be served in place of the default one.


Status changed to Awaiting User Response sam-a • 10 days ago


telem777-beep
OP

10 days ago

Thanks !!! Bro!


Status changed to Awaiting Railway Response Railway • 10 days ago


Status changed to Awaiting User Response Railway • 10 days ago


Status changed to Solved Railway • 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...