20 days ago
My domain www.osteosarralbe.fr has been stuck on "Validating domain ownership".
The CNAME points to toljezk4.up.railway.app, and the _railway-verify.www TXT record is publicly visible through Google DNS and Cloudflare DNS.
The nameservers are managed by IONOS. There are no CAA or DNSSEC DS records.
My Django application is running correctly on Railway, and a direct request to the Railway IP (69.46.46.10) using the custom hostname returns HTTP 200. However, HTTPS certificate verification fails with a hostname mismatch.
Could you check whether the domain verification or certificate issuance workflow is stalled and re-trigger it if necessary?
5 Replies
20 days ago
Your TXT record matches and domain ownership is already verified, and the CNAME resolves correctly to your Railway target.
What is holding the certificate is the HTTP check that runs before issuance: a recent attempt was not answered by us, and in our own test a plain HTTP request to the domain was first answered by a different server (a Microsoft IIS host, not Railway) that redirected to HTTPS. That usually means some DNS resolvers still have the previous host cached for this name, or a leftover A/AAAA record or IONOS redirect/forwarding setting still exists on the www subdomain alongside the CNAME. Please check in IONOS that the CNAME is the only record on www and that no web forwarding is enabled for it. Once every resolver consistently reaches us, issuance continues automatically without needing to re-add the domain.
Status changed to Awaiting User Response Railway • 20 days ago
Railway
Your TXT record matches and domain ownership is already verified, and the CNAME resolves correctly to your Railway target. What is holding the certificate is the HTTP check that runs before issuance: a recent attempt was not answered by us, and in our own test a plain HTTP request to the domain was first answered by a different server (a Microsoft IIS host, not Railway) that redirected to HTTPS. That usually means some DNS resolvers still have the previous host cached for this name, or a leftover A/AAAA record or IONOS redirect/forwarding setting still exists on the www subdomain alongside the CNAME. Please check in IONOS that the CNAME is the only record on www and that no web forwarding is enabled for it. Once every resolver consistently reaches us, issuance continues automatically without needing to re-add the domain.
20 days ago
Thanks for your response. I've completed further troubleshooting.
Both Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) correctly resolve www.osteosarralbe.fr to toljezk4.up.railway.app (69.46.46.10).
However, my local SFR router DNS (192.168.1.254) still returns the previous hosting IP (207.180.248.220).
A direct HTTP request to Railway IP 69.46.46.10 returns HTTP 301 with the x-railway-67 header, confirming that Railway is handling HTTP traffic correctly.
The Railway dashboard still displays "Validating domain ownership", although your previous response confirmed that ownership was already verified.
Could you please check whether the HTTP challenge or certificate issuance is stalled, and manually restart the validation or certificate issuance process if necessary?
There are no conflicting A or AAAA records for www in my IONOS DNS configuration.
Status changed to Awaiting Railway Response Railway • 20 days ago
20 days ago
Your CNAME and TXT records are correct and ownership is verified, so the dashboard label reflects the certificate step, which has not completed yet. The most recent check before issuance ran at 04:22 UTC and still could not complete. When we tested the domain again just now, the first plain HTTP request still went to the previous host (207.180.248.220, the same address your SFR router returns), and that host redirected it to HTTPS before it ever reached us.
Your IONOS records don't need any more changes. The remaining issue is DNS resolvers that still have the old address cached, and they keep serving it until the old record's TTL runs out. Re-triggering issuance now would fail the same way, because the check needs every request to reach us over plain HTTP. Once those cached entries expire, the check passes and the certificate is issued automatically.
Status changed to Awaiting User Response Railway • 20 days ago
Railway
Your CNAME and TXT records are correct and ownership is verified, so the dashboard label reflects the certificate step, which has not completed yet. The most recent check before issuance ran at 04:22 UTC and still could not complete. When we tested the domain again just now, the first plain HTTP request still went to the previous host (207.180.248.220, the same address your SFR router returns), and that host redirected it to HTTPS before it ever reached us. Your IONOS records don't need any more changes. The remaining issue is DNS resolvers that still have the old address cached, and they keep serving it until the old record's TTL runs out. Re-triggering issuance now would fail the same way, because the check needs every request to reach us over plain HTTP. Once those cached entries expire, the check passes and the certificate is issued automatically.
20 days ago
I need this escalated to a Railway engineer, please.
My domain www.osteosarralbe.fr remains stuck in "Validating domain ownership", even though Railway has confirmed that ownership is verified and both the CNAME and TXT records are correct.
I found similar Railway support cases where the certificate issuance workflow had stalled and a Railway engineer manually triggered certificate re-issuance:
https://station.railway.com/questions/custom-domain-stuck-in-validating-owners-67fcac3b
https://station.railway.com/questions/custom-domain-stuck-in-validating-owners-a386b840
Please investigate whether my domain is experiencing the same issue and manually re-trigger the ownership validation/certificate issuance workflow if appropriate.
The production website is inaccessible securely through its official domain. I need human technical assistance rather than another automated DNS troubleshooting response.
Status changed to Awaiting Railway Response Railway • 20 days ago
20 days ago
We checked the domain again just now, and public DNS is returning both your CNAME to the Railway target and a separate A record for 207.180.248.220 on the same www name. That is the previous host, and it is still what answers the certificate check: a plain HTTP request to the challenge path lands on that server, which redirects it to HTTPS and returns a 404, so it never reaches us.
This corrects our earlier reply. This is not only resolver caching, so an IONOS change is still needed. A CNAME can't coexist with an address record on the same name, and resolvers are using the A record. Even though no A or AAAA record appears in your IONOS record list, something on the IONOS side is still publishing 207.180.248.220 for www, and it has to be removed so the name resolves through the CNAME alone. Re-triggering issuance before then would fail the same way, because the check would still reach that server. Once www resolves only to the Railway target, the certificate check can complete.
Status changed to Awaiting User Response Railway • 20 days ago
13 days 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 • 13 days ago