2 months ago
Hi team,
My custom domain has been stuck in VALIDATING_OWNERSHIP for over 6 days.
DNS is correctly pointing to the Railway-provided CNAME target and has been
verified via dig from multiple locations — Let's Encrypt validation just
never completes.
- Project: candor-platform
- Environment: production
- Service: candor-platform
- Custom domain: app.candorconstruct.com
- Custom domain ID: d5ea213e-89dc-4d81-ba56-0b41c82481ec
- Status: VALIDATING_OWNERSHIP (unchanged since ~July 29)
- DNS provider: Squarespace
- CNAME target on file: (whatever Railway shows in the domain panel)
I've already tried:
-
Recreating the custom domain (which changed the CNAME target — I updated
Squarespace DNS accordingly)
-
Verifying DNS resolves correctly from multiple resolvers
Can you please retrigger the cert issuance or investigate why the ACME
challenge isn't completing?
Thanks,
Wes Loewen
4 Replies
2 months ago
Your CNAME is correctly propagated, but the TXT ownership-verification record is missing, which is why the certificate is stuck. Both a CNAME and a TXT record are required for custom domains. In your Squarespace DNS, create a TXT record with the host _railway-verify.app and the value shown in the domain panel under your service's settings (it starts with railway-verify=). Once it propagates, certificate issuance will proceed automatically. Reply here after adding it so we can verify propagation.
Status changed to Awaiting User Response Railway • 2 months ago
Railway
Your CNAME is correctly propagated, but the TXT ownership-verification record is missing, which is why the certificate is stuck. Both a CNAME and a TXT record are required for custom domains. In your Squarespace DNS, create a TXT record with the host `_railway-verify.app` and the value shown in the domain panel under your service's settings (it starts with `railway-verify=`). Once it propagates, certificate issuance will proceed automatically. Reply here after adding it so we can verify propagation.
2 months ago
Added the TXT record _railway-verify.app with the value from the Configure
DNS Records panel. Propagation verified — `dig TXT
_railway-verify.app.candorconstruct.com +short` returns the expected
railway-verify= value.
Please retry ownership validation and cert issuance.
Thanks!
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Your DNS is fully correct - both the CNAME and the TXT verification record are propagated and match. The certificate workflow had stalled, so we've re-triggered verification and certificate issuance for app.candorconstruct.com. This should complete within a few minutes.
Status changed to Awaiting User Response Railway • 2 months ago
mykal
Your DNS is fully correct - both the CNAME and the TXT verification record are propagated and match. The certificate workflow had stalled, so we've re-triggered verification and certificate issuance for `app.candorconstruct.com`. This should complete within a few minutes.
2 months ago
Confirmed working — https://app.candorconstruct.com is live with a valid
Let's Encrypt cert. Thank you mykal, huge help!
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved Railway • 2 months ago