2 months ago
Two custom domains on my project (forevercookbook) have been stuck in "Validating ownership" with no certificate for several hours:
update.myforevercookbook.com (staging env, web service) → CNAME points to r2t2gzlq.up.railway.app
admin.myforevercookbook.com (production env, web service) → CNAME points to mm6db39b.up.railway.app
For both, Railway shows currentValue == requiredValue (DNS is correct). www.myforevercookbook.com on the same service issues fine. I've tried deleting/recreating and removing a stale root-domain entry — the cert just never issues. Can you force a re-issue / check why ownership validation is stuck? Thanks!
1 Replies
2 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
You need to add a TXT record for both _railway-verify.admin.myforevercookbook.com, and _railway-verify.update.myforevercookbook.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.