a month ago
Project: caring-bravery (ed8f960d-fd37-4aee-a0cd-91f4ef30b872), environment: production
This affects all 3 services in the project, not just correpedido-app:
- api.correpedido.com.br -> correpedido-api
- painel.correpedido.com.br -> correpedido-painel
- app.correpedido.com.br -> correpedido-app
DNS: each CNAME points to its per-domain target (vao69yl2 / eo8ekex1 / hx5qug0a
.up.railway.app). Railway shows DNS status PROPAGATED. DNS-only (no Cloudflare
proxy). No CAA records on the zone. Zone is active.
HTTP validation works: Server: railway-edge, and /.well-known/acme-challenge/
responds. But certificateStatus never leaves
CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP, and certificateErrorType /
certificateErrorMessage are both null. HTTPS serves the default *.up.railway.app
cert, so the domains show the "Not Found / train has not arrived" page.
Example request ID from that page: 7_Ajmo_kQ4yLkPWvnPRhug
Already tried, no effect:
- Deleted and recreated all 3 custom domains with fresh targets
- Called customDomainIssueCertificate on all 3 via the API
Please check the cert pipeline logs and/or manually trigger issuance for these
3 domains.
1 Replies
a month ago
All three custom domains have their CNAME records correctly propagated, but each is missing the required TXT ownership-verification record. Certificates cannot issue until verification passes. For each domain, add a TXT record at the hostname shown under "Show DNS records" in the service's Networking settings (it follows the pattern _railway-verify.<subdomain>.<zone>) with the verification value shown there. Once the TXT records propagate, verification will complete and certificates will issue automatically.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago