a month ago
Custom domain "meetings.tpcinternet.com" on project "tpc-meetings-api" / service "api" has been stuck on TXT verification (yellow ⚠ in the DNS records modal) for 7 days.
Diagnostic info I've already verified:
- CNAME meetings.tpcinternet.com → 3ukx6k22.up.railway.app (resolves correctly via 8.8.8.8 / 1.1.1.1, returns 66.33.22.253 — same as the underlying Railway service IP, confirming no Cloudflare proxy interference)
- TXT _railway-verify.meetings.tpcinternet.com → railway-verify=89d7e807d31ea14c843f1e0e2ffe5bf1c6fb09032f2864acf5e9bd00a11e56e6 (resolves correctly via 8.8.8.8 / 1.1.1.1, matches the value shown in your DNS records modal exactly)
- DNS provider: Cloudflare (DNS-only, no proxy)
- Per your docs, cert issuance should happen within 1 hour of DNS being live; we're at 7 days.
Please trigger re-verification on your side. I'd prefer not to delete/re-add since that would force a new TXT token and another DNS request to our infra team.
Pinned Solution
a month ago
Unfortunately the only suggestion I have for you is to remove the domain from Railway and add it back after ~10-15 mins.
1 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Unfortunately the only suggestion I have for you is to remove the domain from Railway and add it back after ~10-15 mins.
Status changed to Solved 0x5b62656e5d • 7 days ago