10 months ago
My custom domain's CNAME is correctly pointing to Railway's target. DNS is working - verified with nslookup via Google DNS (8.8.8.8).
App responds when bypassing SSL cert check:
curl -k --resolve mydomain.com:443:[railway-ip] https://mydomain.com
Returns HTTP 200 with server: railway-edge
Dashboard still shows "Waiting for DNS update" and SSL cert won't issue. Been trying for ~2 hours. Everything works except the
verification is stuck.
16 Replies
10 months ago
What DNS provider are you using?
- Proxy status is set to DNS only (gray cloud, not proxied)
- CNAME record pointing to Railway's target
10 months ago
Have you tried the good 'ol removing the custom domain and readding it?
10 months ago
Worth trying, Railway is having some issues at the moment based on user reports, could be impacted
10 months ago
They often check #✋|help but them seeing this thread is not guaranteed
10 months ago
If nothing happens after idk 24 hours then you could create a thread on station instead
10 months ago
Are you adding your root domain?
10 months ago
Did you add both @ and www in Cloudflare?
9 months ago
I'm seeing this issue as well.
9 months ago
I have this exact same issue with a subdomain, while other domains in the same env that I set up earlier work perfectly fine. This subdomain also does not seem to have the auto-setup with cloudflare option. When I try a different subdomain on the same service, it has the auto-connect with cloudflare option which fails on the first try then succeeds on the second try for setting dns records. I feel like it could be a caching issue on Railway's end for old subdomains that weren't set up properly in the first place?
hello i have a problem i need help with but i cannot make a post so i will just type in here on godaddy (where i bought where i bought my custom domain) it is not letting me use the dns information that railway gave me and is prompting me an error "Record data is invalid." I tryed to switch the time for the TTL and that is still not doing anything