3 months ago
Hello,
I'm having an issue with a custom domain on Railway.
Project:
viabilis-crm
Custom domain:
crm.viabilis.be
The application is running correctly and the deployment is Active.
The DNS has already propagated correctly:
CNAME crm.viabilis.be -> rmlsitg3.up.railway.app
Verified with:
- Cloudflare (1.1.1.1)
- Google DNS (8.8.8.8)
However Railway still shows:
"Waiting for DNS update"
and the HTTPS certificate is never issued.
I already:
- upgraded to the Hobby plan,
- recreated the custom domain,
- updated the CNAME,
- kept the TXT verification record.
Could you please check why the custom domain verification is stuck?
Thank you.
Pinned Solution
3 months ago
You have an invalid TXT record set for _railway-verify.crm.viabilis.be. Your TXT is currently: railway-verify=99d9a10c96835c332deb8beb7a..., which appears to be a copied truncated string. You need to copy the entire string, and it should not contain any dots. A valid TXT record should be like this: railway-verify=<64 char string>
2 Replies
3 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 3 months ago
3 months ago
You have an invalid TXT record set for _railway-verify.crm.viabilis.be. Your TXT is currently: railway-verify=99d9a10c96835c332deb8beb7a..., which appears to be a copied truncated string. You need to copy the entire string, and it should not contain any dots. A valid TXT record should be like this: railway-verify=<64 char string>
3 months ago
Thanks! You were absolutely right.
The issue was indeed the TXT verification record. I had copied the truncated value displayed in the UI instead of the full string. Using the copy button provided the complete verification token, which fixed the problem.
Thanks a lot for spotting this and taking the time to help—I really appreciate it!
Status changed to Solved medim • 3 months ago