Skip to content
Custom domain certificate stuck on “Validating ownership” for 8+ days (DNS + TXT verified)
Anonymous
OP

22 days ago

Project lexia, service lexia, environment production.

Domain: www.lexiaimobiliaria.pt, added Oct 20.

CNAME www → nbnb3v8j.up.railway.app: Railway shows DNS_RECORD_STATUS_PROPAGATED

TXT _railway-verify.www matches the current token. Railway shows verified: true

No CAA records, no DNSSEC

curl -k https://www.lexiaimobiliaria.pt returns 200, so traffic reaches the edge

Certificate status has been CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP since Oct 20. railway domain certificate retry is refused because issuance hasn’t failed.

Could you re-trigger certificate issuance for this domain? Thank you!

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 22 days ago


dizzydes90
EMPLOYEE

22 days ago

Hi Ricardo,

Thanks for the precise write-up; you've done everything right on your side. Your CNAME and the verification record both check out on our side too, and a certificate that has sat in "validating ownership" since 20 October with correct DNS is stuck on our side, not yours. We'll fix it for you: we're reissuing the certificate for www.lexiaimobiliaria.pt within the next 12 hours. Please leave the domain, its CNAME and the verification record exactly as they are; there's no need to remove and re-add it or to retry from the CLI.


Status changed to Awaiting User Response Railway • 22 days ago


dizzydes90
EMPLOYEE

21 days ago

A new certificate has now been issued for your custom domain, and it shows as valid on our side. The domain was left exactly as it was, with the same CNAME target and verification record, so there is nothing to change in your DNS. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.


Status changed to Solved dizzydes90 • 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...