Custom domain stuck on VALIDATING_OWNERSHIP, certificate never issues
jaap-seoninja
PROOP

21 days ago

Hi, a custom domain on one of our services is permanently stuck validating ownership and never issues a TLS certificate.

  • Project: renovlies-net (e6dcb564-7b31-4b30-b21f-d4304e2bea3b)
  • Environment: production (4dcb4c00-b14a-4c15-b55b-940adc653fde)
  • Service: strapi-backend (e949bd84-4333-4ac3-8085-f97d31ba9216)
  • Custom domain: cms.renovlies.net (domain id adb817e3-1854-4454-9b11-38f41f3d3102), target port 1337
  • Status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP — never progresses to issued.

What we've verified:

  • DNS is a plain CNAME cms.renovlies.net → yhjv1bki.up.railway.app (DNS-only, not proxied), which exactly matches the requiredValue Railway reports, and Railway shows the record as PROPAGATED (currentValue == requiredValue).
  • No CAA records exist on renovlies.net (so Let's Encrypt is not blocked).
  • The domain has been stuck since ~early June. We've deleted and re-created the custom domain several times; each recreate assigns a new target and DNS was repointed to match, but it always stays on VALIDATING_OWNERSHIP.
  • Other custom domains on our account validate and serve valid certs without issue (e.g. cms.baptistenkatwijk.nl and api.baptistenkatwijk.nl in project baptistenkatwijk), so this looks specific to this domain/service rather than a DNS or account-wide problem.

Request: Could you investigate the certificate provisioning pipeline for this domain and force/repair issuance? Happy to provide anything else needed.

Solved$20 Bounty

1 Replies

Railway
BOT

21 days ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway 21 days ago


You need to add a TXT record to _railway-verify.cms.renovlies.net. You can find the content for it from the verificationToken property under status.


Status changed to Solved jaap-seoninja 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...