a month ago
DNS verified correct each time.
Project 2acf4e52-cde5-4bdc-af9e-c60369075b4b (dependable-beauty), environment 2192ba9c-1648-4537-afb7-92081e6127fb, service 85711c2a-5c01-48c7-8146-96f72ee174ab, hostname compliance.loanloom.ai, port 8080.
Domain ids tried (delete + recreate), in order: 3fe1833b-6f78-45a1-a9bb-5477afeb0758, 3facb77c-1d92-481c-8c13-6bfd6bd7c2e3, 0a861a53-b4ff-45e2-928b-123175a24b64 (current). Each issued a new CNAME target (ccus8sq3, 6zflfw6c, ertpaplm.up.railway.app); each was set in Cloudflare as a DNS-only CNAME and confirmed at both authoritative nameservers and 1.1.1.1 within seconds. Your DNS check reports DNS_RECORD_STATUS_PROPAGATED, currentValue == requiredValue, one required record, no TXT challenge. Cert never leaves VALIDATING_OWNERSHIP (45+ min polls each attempt); the edge serves CN=*.up.railway.app.
With the record briefly proxied through Cloudflare, requests reached your edge and returned 404 Application not found with x-railway-fallback: true — request ids wjzEsQE0Sw204kjeCYBc-A, G0SHckBtQcGIN8AsWUN5dQ — so the hostname is not routed.
Two things worth checking: (1) loanloom.ai already has working custom domains (api.loanloom.ai, loanloom.ai) in a different project on this account, lovely-motivation — is apex/zone ownership scoped per project? (2) customDomain(id:) intermittently returns Not Authorized / INTERNAL_SERVER_ERROR while serviceInstances.domains reads the same domain fine.
Ask: unstick validation for 0a861a53-b4ff-45e2-928b-123175a24b64, or tell me what input is missing.
Note: the affected service (probo, 85711c2a-5c01-48c7-8146-96f72ee174ab) does not appear in this form's service picker despite being deployed and serving on probo-production-53cf.up.railway.app; selecting a sibling service in the same project.
1 Replies
a month ago
The CNAME is propagated and traffic reaches our edge, but the certificate cannot issue because the TXT ownership-verification record is missing. Custom domains require both a CNAME (for traffic routing) and a TXT record (for ownership verification). In your service's Settings under Networking, expand the domain entry to see the required records, including the TXT record and its host and value. Add that TXT record in Cloudflare as DNS-only, and once it propagates, verification and certificate issuance will resume automatically.
Status changed to Awaiting User Response Railway • 28 days ago
21 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 • 21 days ago