Custom domain SSL cert stuck on "validating ownership" for 6+ hours
srgplus
HOBBYOP

2 months ago

Project ID: 8158bd50-134c-4fb8-8ed0-7d14230025a8

Service ID: 1c25c8ba-8b17-440b-89f0-6059a347099f

Environment ID: 4ab6581a-f297-4aae-8b65-f2ad2f49c4fb

Custom domain: app.creatorstudios.io

Current domain ID: dcd5ea1d-d5b4-48bc-98f1-b9c000fa7e46

CNAME target: gqy0lbvn.up.railway.app

DNS status: CNAME correctly configured and propagated (verified via multiple resolvers: 1.1.1.1, 8.8.8.8, 9.9.9.9)

Certificate status: Stuck on CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP

Duration: 6+ hours

Attempts: Created/deleted the custom domain 4 times via GraphQL API — each time gets a new CNAME target, DNS is updated, but cert never progresses past "validating ownership"

No CAA records blocking Let's Encrypt on the domain

Service domain works fine: srgplus-production.up.railway.app serves traffic with valid SSL

Could you check if there's a Let's Encrypt rate limit hit or a platform-side issue preventing cert issuance for this domain?

5 Replies

Make sure you added the TXT records for _railway-verify.app.


I ran nslookup and it returned NXDOMAIN.


srgplus
HOBBYOP

2 months ago

@pepper ok we've added. It's still showing this screen. How long should we wait after we've added TXT?

Screenshot_2026-04-02_at_9.54.09_PM.png

Attachments


srgplus
HOBBYOP

2 months ago

Yay it worked


Usually takes a few minutes to work but can take up to 24-48 hours for DNS to fully propagate.

But good to know it worked quick.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...