a month ago
Custom domain: www.diggerpocket.com
Service: DiggerPocket-app
Project ID: 78de3b7d-cafd-4724-86b5-0feb12dcf019
Domain ID: b19e2e30-6fa3-44d4-b3df-aec17230b927
The custom domain has been stuck at "Validating domain ownership" /
Certificate status CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for
over 90 minutes. The service itself is online and serving traffic
fine on the Railway-provided domain.
DNS records added (via Onamae.com, nameservers 01-04.dnsv.jp):
- CNAME www -> kj68wp3e.up.railway.app
- TXT _railway-verify.www -> railway-verify=801e9562b81ccbd7d74582350af217caa1035782a421cab133e1f4d2ff32bd3a
Verified via dig from multiple resolvers (local + 8.8.8.8):
- CNAME resolves correctly to kj68wp3e.up.railway.app
- TXT record is present and matches exactly
- No CAA records on either diggerpocket.com or www.diggerpocket.com (no restriction)
- No DS record — DNSSEC is not enabled, so that's not a factor
- Not behind Cloudflare or any other proxy
Since every DNS/config check passes on our end, this looks like a
platform-side issue with certificate issuance. Could someone take a
look at what's blocking validation for this domain?
Pinned Solution
a month ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
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
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Status changed to Solved 0x5b62656e5d • 7 days ago