#Domain stuck on "Waiting for DNS update"

17 messages · Page 1 of 1 (latest)

terse spade
#

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.

torn carbonBOT
cyan jackal
terse spade
#

cloudflare

#
  • Proxy status is set to DNS only (gray cloud, not proxied)
    • CNAME record pointing to Railway's target
cyan jackal
#

Have you tried the good 'ol removing the custom domain and readding it?

terse spade
#

Ha! I have twice. Third time is a charm maybe?

cyan jackal
#

Worth trying, Railway is having some issues at the moment based on user reports, could be impacted

terse spade
#

First time on this discord. Does staff see all help threads?

cyan jackal
#

If nothing happens after idk 24 hours then you could create a thread on station instead

terse spade
#

Thanks for the help!

silent valley
terse spade
#

Yes. I added my root domain . No leading www or https,

silent valley
#

Did you add both @ and www in Cloudflare?

torn carbonBOT
torn carbonBOT
#

New reply sent from Central Station thread:

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?

You're seeing this because this thread has been automatically linked to the Central Station thread.