a month ago
Resolved (domain and project details removed for privacy). Root cause: a custom domain needs both a CNAME to the Railway target AND a TXT record at _railway-verify.subdomain, using status.verificationToken from the API. Thanks to darseen for pointing this out.
Pinned Solution
a month ago
You need to add a TXT record for _railway-verify.<DOMAIN>. If you are using the API to add your custom domain, you can find it in verificationToken under status.
5 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
a month ago
You need to add a TXT record for _railway-verify.<DOMAIN>. If you are using the API to add your custom domain, you can find it in verificationToken under status.
a month ago
Confirmed working now, thank you! Added the TXT record, waited for propagation, then called customDomainIssueCertificate again and status.verified flipped to true within a minute. Domain is live and returning 200.
a month ago
Hi darseen, small favor: could you edit your reply above to remove the domain name (replace with something generic like _railway-verify.subdomain)? Now that it's resolved I'd rather not leave the actual domain in a public thread. Thanks again for the help, it saved us a lot of time!
ingoncalves0-bit
Hi darseen, small favor: could you edit your reply above to remove the domain name (replace with something generic like _railway-verify.subdomain)? Now that it's resolved I'd rather not leave the actual domain in a public thread. Thanks again for the help, it saved us a lot of time!
a month ago
Sure, no problem.
Status changed to Solved 0x5b62656e5d • about 2 months ago