a month ago
Railway agent tells me to contact Railway but this is the only option I have...
Project ID: 3b3f67a0-7529-4c6f-8438-144211c5e8af
Request ID: 4MSPbobYR_m39GrV5nX1uw
Both custom domains fail: www.puurnatuurtuin.nl and puurnatuurtuin.nl
DNS resolves correctly but requests return "Not Found"
The Railway domain works fine: https://puurnatuurtuin-website-production.up.railway.app
Pinned Solution
a month ago
You need to add a TXT record to _railway-verify.<DOMAIN>, where <DOMAIN> is the domain you’re trying to add. If you’re using the API, you can access the token for the TXT record from the verificationToken property under status.
5 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.<DOMAIN>, where <DOMAIN> is the domain you’re trying to add. If you’re using the API, you can access the token for the TXT record from the verificationToken property under status.
a month ago
new issue now
Project ID: 3b3f67a0-7529-4c6f-8438-144211c5e8af
Custom domains: www.puurnatuurtuin.nl and puurnatuurtuin.nl
Both domains verified (TXT records added)
DNS resolves correctly
But SSL certificate is still *.up.railway.app instead of the custom domain
It's been over an hour since verification
a month ago
- Confirm both domains show a green checkmark (verified) in Railway. Both puurnatuurtuin.nl and www.puurnatuurtuin.nl need to be added and verified separately. If only one is verified, the other won't get a cert.
- Check for CAA records on puurnatuurtuin.nl. This is the most common post-verification blocker. If you have CAA records, they must allow Let's Encrypt (letsencrypt.org). If you have no CAA records at all, that's fine, that allows any CA, so it's not your problem.
- Check DNSSEC. If misconfigured, it can silently block the ACME validation. Either fix or temporarily disable it at your registrar.
- If you're behind Cloudflare (proxy/orange cloud): temporarily set the record to DNS-only (grey cloud), wait for Railway to show the green checkmark and issue the cert, then re-enable the proxy. Cloudflare in the validation path can block Let's Encrypt's challenge from reaching Railway.
- No conflicting A/AAAA records for the same hostnames, only the CNAME plus the verify TXT.
If all of that checks out and it's still serving the default cert past ~1 hour, the issuance is likely stuck on Railway's backend. The standard fix is to remove the domain and re-add it once (this triggers a fresh issuance cycle). Do it only once, since Let's Encrypt rate-limits to 5 duplicate certs per domain per week, and burning that limit blocks you for 7 days.
ioriorior
new issue now Project ID: 3b3f67a0-7529-4c6f-8438-144211c5e8af Custom domains: www.puurnatuurtuin.nl and puurnatuurtuin.nl Both domains verified (TXT records added) DNS resolves correctly But SSL certificate is still *.up.railway.app instead of the custom domain It's been over an hour since verification
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.
Status changed to Awaiting User Response Railway • about 1 month ago
ioriorior
new issue now Project ID: 3b3f67a0-7529-4c6f-8438-144211c5e8af Custom domains: www.puurnatuurtuin.nl and puurnatuurtuin.nl Both domains verified (TXT records added) DNS resolves correctly But SSL certificate is still *.up.railway.app instead of the custom domain It's been over an hour since verification
a month ago
By the way, I'm still not able to find a CNAME on puurnatuurtuin.nl and TXT on _railway-verify.puurnatuurtuin.nl. Your www seems fine though.
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 28 days ago