a month ago
My custom domain won't activate, stuck on "Waiting for DNS update" for several hours.
Plan: Hobby (paid).
Domain: klientska-zona.upsddown.cz
Expected target (Railway "Show DNS records"): nrw4rzcx.up.railway.app
Port: 8080
Everything on my side is verified correct:
-
CNAME klientska-zona.upsddown.cz → nrw4rzcx.up.railway.app, confirmed on the authoritative
nameservers (ns1.websupport.cz) AND public resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1,
Quad9 9.9.9.9).
-
nrw4rzcx.up.railway.app resolves to your edge (69.46.46.32).
-
No CAA records; hyphen in the label is valid and resolves fine.
-
The app is healthy and serves the login page on the generated *.up.railway.app domain.
https://klientska-zona.upsddown.cz returns HTTP 404 with "x-railway-fallback: true", and TLS
still serves the default *.up.railway.app certificate — so the custom domain was never
activated and no certificate was issued, despite correct DNS.
I removed/re-added the domain a couple of times earlier (target changed sjnvylm7 → nrw4rzcx),
which may have jammed the validation/cert queue. Please force re-validation and certificate
issuance for this domain. Th
Pinned Solution
a month ago
You need to add a TXT record to _railway-verify.klientska-zona.upsddown.cz. If you’re using the API, you can find the content for the record from the verificationToken property under status.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
You need to add a TXT record to _railway-verify.klientska-zona.upsddown.cz. If you’re using the API, you can find the content for the record from the verificationToken property under status.
Status changed to Solved 0x5b62656e5d • about 1 month ago