a month ago
Hi Railway team,
My custom domain www.combinedbc.com has been stuck at "validating ownership"
/ waiting for SSL certificate issuance since July 19, and no certificate has
been issued. The domain still serves the default *.up.railway.app certificate.
Project details:
- Project: CombinedBC
- Project ID: 3f52c1a0-7215-4287-ab64-bfbfcb936d0b
- Environment: production (59343098-d6e6-450d-891a-c3ef5ee2be64)
- Service: CombinedBC (339e70e2-8ed9-4ea3-92c6-b3d6c7b1969a)
- Custom domain: www.combinedbc.com (current domain ID: 64bf67cd-8347-4501-9f8b-94271c31947f)
- Target port: 8080
What I've verified on my side:
-
The CNAME record for www.combinedbc.com points to the exact target shown
in the dashboard (vqfh1xv0.up.railway.app) and is confirmed propagated on
the authoritative nameservers (ns45/ns46.domaincontrol.com), Google DNS,
and Cloudflare DNS.
-
Your own API reports the DNS record as DNS_RECORD_STATUS_PROPAGATED, but
certificateStatus stays at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
and the certificates array is empty.
-
There are no CAA records on the domain, so Let's Encrypt issuance is not
blocked.
-
The _railway-verify TXT record is present.
-
I have already tried: redeploying the service, and removing/re-adding the
custom domain (the current domain ID above is from the fresh re-add). The
status remains stuck.
Could you please check what is blocking ownership validation / certificate
issuance for this domain on your side, and force a re-validation?
Thank you!
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
You need a TXT record at _railway-verify.www.combinedbc.com. You can get the content for it from the verificationToken property under status.