a month ago
Hi Railway team,
I’m trying to attach a custom domain to my web service, but it seems stuck in fallback / certificate provisioning.
Service:
- Environment: production
- Service: WEB
- Custom domain: www.cosmofinder.com
- Target port: 8080
Current situation:
- Railway asks me to configure:
- CNAME www -> 7k4xdqv7.up.railway.app
- TXT _railway-verify.www -> railway-verify=34fd375df568142aa2a35241d9a0b4c59fb8d6553afb87a801cf11812fdbb000
- These DNS records are correctly set at Namecheap BasicDNS.
- Authoritative DNS checks return the expected values.
- However, Railway still shows “Waiting for DNS update” / does not finish provisioning.
- Accessing https://www.cosmofinder.com returns a Railway fallback response.
- Response headers include: x-railway-fallback: true
- SSL certificate is not issued for www.cosmofinder.com and browsers show a certificate mismatch.
Important notes:
- The generated Railway domain for the service is working correctly.
- The custom domain exists only on this WEB service, not on backend/admin.
- DNS has already propagated on the authoritative nameservers.
Could you please check whether the custom domain binding or SSL provisioning is stuck on Railway’s side?
Thanks.
3 Replies
Status changed to Open Railway • about 1 month ago
a month ago
It may take Railway up to a few hours (maybe even a day, but rarely) to validate the DNS and issue a certificate. If it doesn’t happen by then, try removing the domain from Railway and add it back after ~10-15 mins. (I'd check DNS as well, your domain's pointing elsewhere.)
0x5b62656e5d
It may take Railway up to a few hours (maybe even a day, but rarely) to validate the DNS and issue a certificate. If it doesn’t happen by then, try removing the domain from Railway and add it back after ~10-15 mins. (I'd check DNS as well, your domain's pointing elsewhere.)
a month ago
Hi,
I’ve been waiting for days for this custom domain to validate and provision an SSL certificate, but it still hasn’t completed.
I have already retried the process multiple times:
- removed the domain from Railway
- waited
- added it back again
- verified the DNS records again and again
The DNS is correctly configured on Namecheap BasicDNS:
- CNAME: www -> 7k4xdqv7.up.railway.app
- TXT: _railway-verify.www -> railway-verify=34fd375df568142aa2a35241d9a0b4c59fb8d6553afb87a801cf11812fdbb000
Authoritative DNS checks return the correct values, but Railway still does not complete validation / SSL provisioning.
The custom domain continues to return a Railway fallback response, and the certificate is still not issued for www.cosmofinder.com.
I have already waited much longer than a few hours, and I have repeated the remove/re-add flow several times without success.
Could you please check whether the domain binding or certificate provisioning is stuck on Railway’s side?
Thanks.
a month ago
I’d fix DNS before waiting on Railway here.
From my side, www.cosmofinder.com is not pointing to the Railway target you pasted. It resolves as:
www.cosmofinder.com -> 59d32fee4e9256e4.vercel-dns-017.comRailway asked for:
www -> 7k4xdqv7.up.railway.appI also don’t see the _railway-verify.www.cosmofinder.com TXT record publicly from here.
So I don’t think this is cert provisioning being slow yet. Railway is probably still seeing the domain attached to the old/Vercel target, or not seeing the ownership TXT.
In Namecheap, I’d check for any Vercel integration, URL redirect, parking record, or duplicate www record. You want exactly:
www CNAME 7k4xdqv7.up.railway.app
_railway-verify.www TXT railway-verify=34fd375df568142aa2a35241d9a0b4c59fb8d6553afb87a801cf11812fdbb000Then verify from outside Namecheap:
dig +short CNAME www.cosmofinder.com
dig +short TXT _railway-verify.www.cosmofinder.comOnce those show the Railway values, then remove/re-add the domain only if Railway still doesn’t pick it up. Right now I’d treat this as DNS still not matching what Railway expects.
Status changed to Solved 0x5b62656e5d • 7 days ago