a month ago
Custom-domain SSL stuck on "Validating ownership" ~24h. Project amk-crm-live (production), service amk-crm-live, domain app.amktravelsindia.com. CNAME points to the Railway target and the dashboard shows the DNS record "Propagated", but the certificate never issues — even after removing/re-adding the domain and redeploying. Requests to the domain return 403 x-deny-reason: host_not_allowed, so it isn't attaching at your edge. Please force-issue / re-sync it.
1 Replies
a month ago
The certificate is stuck because the TXT ownership-verification record has not been created at your DNS provider. Your CNAME is resolving to our edge correctly, but both records are required: the CNAME for traffic routing and a TXT record for domain ownership verification. Open your service's Settings, find the domain under Networking, expand "Show DNS records," and create the TXT record at your registrar with the exact host and value shown there. Once it propagates, verification and certificate issuance will resume automatically, and the 403 will clear.
Status changed to Awaiting User Response Railway • 26 days ago
19 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 • 19 days ago