22 days ago
I added tufaena.com (root/apex domain) as a custom domain on my faena service. The CNAME record (tufaena.com → the Railway-provided value) and the required TXT verification record are both correctly configured and confirmed propagated externally (verified via DNS-over-HTTPS from multiple resolvers). Despite this, the domain has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP / verified: false for over 24 hours — well beyond the ~1 hour documented in your docs.
Requests to https://tufaena.com/ return:
HTTP/1.1 404 Not Found
{"status":"error","code":404,"message":"Application not found"}
I deleted and re-created the custom domain once (got a new CNAME target, updated DNS accordingly, re-confirmed propagation) — no change in outcome.
No CAA records exist on the domain (checked, so that's not blocking Let's Encrypt). www.tufaena.com on the same service works perfectly and is verified.
Could you check what's blocking verification on the tufaena.com (apex) custom domain for this service?
1 Replies
22 days ago
The verification TXT record is published on the root of the domain rather than on the _railway-verify subdomain. Railway expects the ownership token at _railway-verify as the host/name in your DNS provider (Cloudflare will append your zone automatically), not as a TXT record on the bare domain itself. Moving that record to the correct host will unblock verification and certificate issuance, which resume automatically once the corrected record propagates.
Status changed to Awaiting User Response Railway • 22 days ago
15 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 • 15 days ago