24 days ago
Hi Railway team, a custom domain on my Hobby workspace has been stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for 13+ hours with no error message and no Try Again button.aHi Railway team, a custom domain on my Hobby workspace has been stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for 13+ hours with no error message and no "Try Again" button. Everything on my side looks correct.
Project: superman-community (04f4a1cd-fa6d-4fb4-8694-d93ce9fe6e86) / environment: production (ace1f420-acf3-40c8-98a0-0931d1e9ddcb) / service: app (dd4647c7-1127-4925-a08f-217c2ed6a3a1). The service deploys fine and its Railway domain app-production-67d3.up.railway.app works over HTTPS.
Custom domain: community.supermanlondon.com (domain id 6346e40d-3c9c-40d1-830c-80b6deabab67), target port 3000.
Timeline: Sep 11 ~14:10 UTC I added the domain via API before the CNAME existed (my mistake); the CNAME was added ~10 min later at Wix DNS. It stayed VALIDATING for ~50 min, so I deleted and re-added the domain at ~15:15 UTC. New required CNAME: najw0tb6.up.railway.app, updated in Wix DNS immediately. Since ~16:15 UTC the API shows DNS PROPAGATED with currentValue == requiredValue (najw0tb6.up.railway.app), but the certificate has stayed VALIDATING ever since (now 13+ hours).
Checks: dig via 8.8.8.8 / 1.1.1.1 / Wix authoritative NS all return CNAME community.supermanlondon.com -> najw0tb6.up.railway.app (TTL 3600). No CAA records on supermanlondon.com or the subdomain. curl -I http://community.supermanlondon.com/ reaches the Railway edge (301 to https, x-railway-67 header), so HTTP-01 should be reachable. Another custom domain in the same workspace (order.supermanlondon.com, project superman-restaurant) was issued fine previously.
Could you please check the ACME order for this domain and re-trigger certificate issuance? Thank you!
2 Replies
24 days ago
Your CNAME is propagated correctly, but the TXT ownership-verification record is missing. That is why the certificate is stuck at VALIDATING_OWNERSHIP with verified showing false. Add a TXT record in Wix DNS with the host _railway-verify.community (Wix appends the zone) and the value railway-verify=145a7916cbd30d0d21425762041c305366fd8a6c4f1437f61a67c288b6552948. Verification and certificate issuance will resume automatically once the record propagates.
Status changed to Awaiting User Response Railway • 24 days ago
24 days ago
Solved, thank you! Adding the TXT ownership-verification record (_railway-verify.community) in Wix DNS did it: within about 3 minutes the domain showed verified and the certificate went to VALID, and https://community.supermanlondon.com now loads. For anyone else hitting this: the API domain-status only reports the CNAME, so a missing TXT record is easy to miss. If you are stuck at VALIDATING_OWNERSHIP with a correct CNAME, check for the _railway-verify TXT record.
Status changed to Awaiting Railway Response Railway • 24 days ago
Status changed to Solved Railway • 24 days ago