a month ago
Issue: HTTPS certificate is not being issued for the custom domain. The TXT validation record is displaying a yellow warning triangle (⚠️) for over 72 hours, indicating that Railway cannot validate the domain despite the DNS record being present.
Verification completed:
- CNAME record: correctly pointing to Railway-provided value ✓
- TXT validation record: PRESENT in DNS but showing yellow warning ⚠️
- DNS propagation confirmed with dnschecker.org
- No CAA record restrictions (Let's Encrypt authorized)
- DNSSEC configuration verified with dnsviz.net
- Service running and deployed
- Domain configured in service's public networking section
Certificate status: Stuck in "validating challenges" for 72+ hours
Request: Railway is unable to validate the TXT record despite its confirmed presence. Please investigate on the platform side and resolve the HTTPS certificate validation blockage.
4 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again. This usually fixes the stuck state.
darseen
Try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again. This usually fixes the stuck state.
a month ago
ty but I can't because it will change the txt verification and I don't have access to dns for 3 days
a month ago
@railway-support
@support
This is a platform-side issue blocking HTTPS certificate issuance for over 72 hours.
The TXT record is present and propagated but Railway cannot validate it.
Requesting direct support investigation and manual resolution.
a month ago
@support, can you re-run the dns check on this production, please ? thats urgent
Status changed to Solved remlass • about 1 month ago