17 days ago
Hi team,
I’ve had a custom domain stuck in VALIDATING_OWNERSHIP since ~8 PM CT yesterday (May 18 / now May 19, 10 AM CT — about 14 hours). I’ve tried delete/recreate cycles to retrigger validation; no change.
Project: business in a box (af55d2b6-021a-49b2-9a1a-5d7829f45a4c)
Service: bellah-audio (2f69ac9d-1336-4d22-8ca1-51bdfabc3a63)
Environment: production (f5b6a278-151d-40d1-a2f7-255c5d1d4a13)
Domains: bellahaudio.com, www.bellahaudio.com
Context: this domain was previously claimed by another Railway customer (Townsquare Interactive) hosting the prior version of the site. That claim was released yesterday. After release I added these as new custom domains on my service.
Diagnostic: www.bellahaudio.com’s CNAME is correctly visible to your system — currentValue: 1s1g8hmi.up.railway.app exactly equals requiredValue: 1s1g8hmi.up.railway.app — but the certificate never provisions. Suggests a stuck verification job from the previous claim release.
Could you manually trigger cert issuance or clear any pending state from the prior claim?
Thanks,
Kallisti Upton
2 Replies
17 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 17 days ago
17 days ago
add a TXT record at _railway-verify.bellahaudio.com. the value is in the verificationToken field under status — visible in the Networking → Custom Domains panel of the dashboard, or via the API.
17 days ago
You need to add a TXT record at _railway-verify.www.bellahaudio.com. Railway uses TXT records to verify domain ownership.
If you are using the API to add your custom domain, you can find it in verificationToken under status