25 days ago
Project: upcar · Service: upcar-app · Environment: production · Plan: Hobby (active billing, card on file)
Two custom domains have been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for over an hour, with no error message:
upcar.safecodex.com.br (added ~2h ago)
app.safecodex.com.br (added ~40 min ago, DNS correct from the start)
For both: the CNAME points to the Railway target and the dashboard shows the DNS record as PROPAGATED. No CAA record on the zone, DNSSEC is not enabled, no conflicting A/AAAA. The app itself works fine on upcar-app-production.up.railway.app. Hitting the edge with the correct Host header returns 404, and http:///.well-known/acme-challenge/… also returns 404, so no challenge token is being served.
Please force a fresh Let's Encrypt order / investigate why ownership validation is not completing for this account.
1 Replies
25 days ago
The first domain is not present in our system at all, so it may need to be re-added from the service's settings. For the second domain, the traffic CNAME is correctly propagated, but the TXT ownership-verification record is missing. Custom domains require both a CNAME for routing and a TXT record at _railway-verify.app (your DNS provider appends the zone) set to the verification token shown in the domain's setup panel in Settings, Networking. Once that TXT record is published and propagates, ownership validation and certificate issuance will resume automatically.
Status changed to Awaiting User Response Railway • 25 days ago
18 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 • 18 days ago