a month ago
Custom domain tracker-staging.100health.ai on project 100-health-tracker-staging (service 100-health-tracker) is stuck on TXT verification. The CNAME (tracker-staging → t5x1s0nq.up.railway.app) shows verified in the dashboard. The TXT record _railway-verify.tracker-staging.100health.ai is published with the exact value shown in the dashboard (railway-verify=f5fb9f215f5cfaabbc94d082e55b9324bb9f9af82e81b285bebf5c35c2d6b276). Google’s public DNS lookup confirms it. Visiting the domain returns your “Not Found / The train has not arrived” page (Request ID: klz-sWo0Qj-rJzYWYqdHTg). Could you re-trigger verification or tell us what’s blocking it?
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Both of your records are correct: the CNAME has propagated and the verification TXT exactly matches the expected value, but the ownership check never re-ran after the TXT was published. We've started a fresh verification and certificate issuance for the domain, which can take a few minutes to complete.
Status changed to Awaiting User Response sam-a • about 1 month ago
a month ago
Confirmed working, both records are green and the domain is live with a valid certificate. Thank you for the quick fix!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago
