7 days ago
Custom domains api.kiai.gg (service: server) and app.kiai.gg (service: frontend) are stuck at VALIDATING_OWNERSHIP for 1h+.
Project: Kiai_FGC (ID: edf457a8-d3e1-41de-83a7-057e4268ff4c) Environment: production (ID: 126af380-9620-42e1-8106-6f7333ebdc6e) Services:
server (ID: 5915624c-7c42-4f2a-ae9d-940d8f2d0d6e)
frontend (ID: 632ae7c5-4dca-4f6a-a8f1-de2aeb33a984)DNS Status:
CNAME records propagated ✓
currentValue == requiredValue ✓
syncStatus: ACTIVE ✓
No CAA/DNSSEC restrictions
No AAAA records on targets
No domain conflicts across environments
Registrar: Porkbun (DNS-only)Troubleshooting done:
Delete + recreate domains (no change)
Verified DNS propagation multiple times3 Replies
7 days ago
I don't see the _railway-verify.api.kiai.gg and _railway-verify.app.kiai.gg TXT records
Thanks @astrid!!! that was it! Adding the _railway-verify.api.kiai.gg and _railway-verify.app.kiai.gg TXT records fixed it. Both domains flipped to verified: true and the Let's Encrypt certs issued within a couple of minutes. api.kiai.gg and app.kiai.gg are now live with valid TLS.
One bit of feedback in case it's useful: I set these domains up via the railway CLI (railway domain ...), and the CLI only ever returned the CNAME record it never surfaced the required _railway-verify TXT record. So everything looked correct (DNS PROPAGATED, syncStatus: ACTIVE) while the cert sat at VALIDATING_OWNERSHIP with no indication that a verification TXT was missing. The dashboard shows it, but the CLI doesn't might be worth having railway domain print both records like the dashboard does.
Thanks again for the quick catch!
7 days ago
Checking, are you on the latest version of the cli?