Custom domain stuck: certificate never issues despite propagated DNS and manual trigger
sroemer-crhvac
HOBBYOP

14 days ago

Custom domain admin.crhvacpro.com (project 57d9698d-6304-4bad-81ba-f6290433b1e4) never gets a certificate. The API shows the CNAME as propagated with currentValue matching requiredValue exactly, but status.certificates stays empty for over an hour — on two separate registrations of the domain (deleted and re-created once, DNS updated and re-verified). The customDomainIssueCertificate mutation returns true but nothing happens. The domain has no CAA or DNSSEC and Let's Debug (http-01) passes clean. Looks stuck server-side — can someone take a look?

Solved

2 Replies

Railway
BOT

14 days ago

The CNAME for admin.crhvacpro.com is correctly propagated, but the domain is still unverified because the required TXT ownership-verification record is not present at your registrar. Certificates will not issue until verification passes. You can find the exact TXT record name and value on the domain's settings page in your project, and once you add it and it propagates, the certificate should begin issuing.


Status changed to Awaiting User Response Railway 14 days ago


You need to add a TXT record to _railway-verify.admin.crhvacpro.com. If you’re using the API, you can find the content for the record from the verificationToken property under status.


Status changed to Awaiting Railway Response Railway 14 days ago


Status changed to Awaiting User Response Railway 14 days ago


Railway
BOT

7 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 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...