a month ago
Subject: SSL Certificate Not Issuing for Custom Domain www.keeevo.com
Hi Railway Support,
I'm having trouble getting an SSL certificate issued for my custom domain www.keeevo.com.
What I've done:
Added custom domain www.keeevo.com (port 8000) to my Railway main app
Configured DNS records in GoDaddy:
CNAME: www → 52jgki4n.up.railway.app
TXT: @ → railway-verify=e5b59ed1375df24fe8a1e6e09c16cdc2c708ee183911d50db14ad64751fc89e7
DNS is resolving correctly globally (verified with dig @8.8.8.8)
The problem:
DNS is live and working
But accessing https://www.keeevo.com gives SSL certificate error: "no alternative certificate subject name matches target host name"
The certificate appears to be issued for the Railway subdomain, not the custom domain
I've waited 60+ minutes since DNS propagated
What I need:
Please manually verify the custom domain or force SSL certificate generation for www.keeevo.com
Details:
App name: deadlyapp.up.railway.app (this is my railway app that is working fine)
Domain: www.keeevo.com. (this is my actual app that I would like to work)
Custom domain was re-added today after initial verification issues
Thank you!
4 Replies
a month 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 1 month ago
a month ago
If you're using www, the TXT record must be on _railway-verify.www, not _railway-verify. If you're using @, then your CNAME must be on @ as well, not www.
a month ago
I have done this already a couple of times now but. this doesn't work, or is not working for me and I have no idea why.
a month ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
0x5b62656e5d
If you're using `www`, the TXT record must be on `_railway-verify.www`, not `_railway-verify`. If you're using `@`, then your CNAME must be on `@` as well, not `www`.
a month ago
I can only use www as godaddy is not accepting @. So based on that I have updated my TXT name to _railway-verify.www instead of @ which was there earlier. Hope this solves.
Status changed to Solved 0x5b62656e5d • 16 days ago