a month ago
Custom domain demo.kmest.top is stuck on "Validating domain ownership".
Authoritative DNS is already correct:
- CNAME demo -> kwnasj0q.up.railway.app
- TXT _railway-verify.demo -> railway-verify=e1a89284376f4e1b08950f6f1fd2265abb79772d85dc1674830906d7b98ff1c9
The domain resolves publicly and https://demo.kmest.top reaches railway-edge with HTTP 200, but TLS still serves the default certificate for *.up.railway.app instead of demo.kmest.top.
Please recheck domain ownership validation / SSL issuance on your side.
Please note that the affected public service is profound-solace / Kmest-Ecommerce / production.
Pinned Solution
a month ago
I’d try removing all associated records from your DNS provider and Railway, waiting ~10-15 mins, then readd them back.
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
but I don't have an option to change the status? it has remain Validating domain ownership
Status changed to Open Railway • about 1 month ago
a month ago
I’d try removing all associated records from your DNS provider and Railway, waiting ~10-15 mins, then readd them back.
a month ago
the DNS setup is correct and Railway's edge is already routing traffic for demo.kmest.top (HTTP 200 confirms it). the stuck Validating domain ownershipb+ wrong TLS cert is a known provisioner race condition on Railway's side, not a DNS problem.standard fix: remove the custom domain from your Railway service settings, wait ~30 seconds, then re-add it.this kicks a fresh cert provisioning cycle. in most cases the cert for demo.kmest.top comes through within 2-5 minutes after re-adding.if it gets stuck again after that, the cert provisioner needs a manual trigger on Railway's end - that's something only Railway staff can do from the backend.
a month ago
I already removed and re-added the domain, updated the CNAME to the new Railway target, and kept the TXT verification record in place.
The domain still remains stuck at "Validating domain ownership" in Railway.
At this point it looks like the DNS is correct but the verification / certificate provisioning is stuck on Railway's side.
Could a Railway staff member please manually check or trigger the domain verification / SSL provisioning for demo.kmest.top?
Status changed to Solved 0x5b62656e5d • 25 days ago