41 minutes ago
Hello Railway Community,
Our custom domain, contact.intergroup.asia, has been stuck in certificate issuance for more than seven days.
Current situation:
- Railway displays “Waiting for DNS update”
- The required CNAME and TXT verification records are publicly resolving and match the values provided by Railway
- CNAME: contact → k8o57yzh.up.railway.app
- The service is healthy at https://inter-group-contact.up.railway.app/
- contact.intergroup.asia presents the default *.up.railway.app certificate, resulting in NET::ERR_CERT_COMMON_NAME_INVALID
I also tried:
railway domain certificate retry contact.intergroup.asia
However, the CLI returned:
Certificate retry is only available after certificate issuance fails.
Current status: CERTIFICATE_STATUS_TYPE_ISSUING.
This appears identical to the following resolved case, where Railway manually started certificate reissuance:
https://station.railway.com/questions/custom-domain-stuck-at-certificate-statu-7b728e8d
Could someone from Railway please help restart or reissue the certificate? Is there anything else we can do while the status remains stuck at ISSUING?
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 39 minutes ago
27 minutes ago
Your DNS records are correctly configured and the verification TXT record matches, but the certificate workflow stalled before it could pick up those records. We've started a certificate re-issuance for your domain, which should complete within a few minutes.
Status changed to Awaiting User Response sam-a • 27 minutes ago