Custom domain cert stuck in VALIDATING_OWNERSHIP - _railway-verify TXT already correct
barry-cp
PROOP

a month ago

Project: focused-enthusiasm, Service: core-lms

Custom domain: academy.coachingpen.com (id: 658f28a9-ee0a-4053-94f3-c5836f479908)

The certificate for academy.coachingpen.com has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for nearly 2 hours and is not advancing.

To skip the standard answer: the _railway-verify.academy.coachingpen.com TXT record is already present and its value exactly matches the verificationToken the Railway API reports for this domain. Verified on both authoritative nameservers (ns1 and ns2.dns-parking.com) and on Google and Cloudflare resolvers. So this is past the missing-TXT cause.

Precedent: a sibling domain in the same project, academy4.coachingpen.com, had a VALIDATING_OWNERSHIP stall that was resolved via the missing-TXT fix (a thread on this forum from about a day ago). This is a similar stall, but with the TXT already correctly in place, so it needs a different look.

This is not isolated to our project. In the last 5 to 15 hours multiple Railway users have reported the identical symptom: a custom-domain certificate stuck in VALIDATING_OWNERSHIP with the _railway-verify TXT already correctly in place, including a thread from about 15 hours ago (still open) where a second user has also commented confirming the same. This pattern points to a current platform-side issue on the ownership-validation step. Railway's status page shows Fully Operational, but per its own note it only surfaces widespread incidents and directs smaller or isolated issues to this forum.

DNS is otherwise fully correct: CNAME academy.coachingpen.com points to a3acfwrf.up.railway.app, which the Railway domains API itself reports as DNS_RECORD_STATUS_PROPAGATED (currentValue == requiredValue). No CAA records on coachingpen.com, no conflicting A or AAAA records. The domain is reachable at the Railway edge (http://academy.coachingpen.com returns 301).

History: the domain was previously in CERTIFICATE_STATUS_TYPE_ISSUE_FAILED (it pointed at a different host for a long period). We removed and re-added the custom domain to reset it; it moved to VALIDATING_OWNERSHIP and has not advanced since. A service redeploy did not move it.

Request: please advance or re-trigger certificate issuance for academy.coachingpen.com. DNS and ownership records are all correctly in place.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


barry-cp
PROOP

a month ago

Update: I've now upgraded to Pro to escalate this. 20+ hours in "Awaiting Railway Response" with no platform-team reply. DNS and _railway-verify TXT remain verified correct, and a sibling domain in the same project (academy4.coachingpen.com) is serving fine. B2B launch is on Tuesday 2026-05-26 and the canonical domain (academy.coachingpen.com) needs a valid cert by then. Could someone from the platform team take a look? Happy to provide any extra info needed.


chandrika
EMPLOYEE

a month ago

The certificate for academy.coachingpen.com has completed issuance and is now valid. DNS, verification, and certificate status all show as fully resolved on our end, so you should be all set for your Tuesday launch. No further action is needed.


Status changed to Awaiting User Response Railway about 1 month ago


chandrika
EMPLOYEE

a month ago

Please let us know if you are seeing anything otherwise and good luck for you launch 🙌


Railway
BOT

23 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...