2 months ago
Two custom domains in the same project have been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for hours, while the rest of the project's domains (the *.up.railway.app ones) all have valid Railway-wildcard certs. Both target CNAMEs are DNS_RECORD_STATUS_PROPAGATED. I also added the railway-verify=... TXT records (matching the verificationToken field on customDomain.status) per the pinned solution in this thread, and those are also live globally. State has not advanced.
This is identical to the symptoms in thread 25b7f4f1 where a moderator had to manually kick the pipeline. Asking for the same on these two domains.
Attachments
Pinned Solution
2 months ago
Railway usually issues certificates within a few hours, but it may take up to a day (rare cases). If that’s the case, try removing the domain from Railway, and adding it back after ~10-15 mins.
2 Replies
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
Railway usually issues certificates within a few hours, but it may take up to a day (rare cases). If that’s the case, try removing the domain from Railway, and adding it back after ~10-15 mins.
2 months ago
Also, on a side note, moderators do not have access to Railway’s systems. Railway automatically validates the DNS records and issues certificates at certain intervals.
Status changed to Solved 0x5b62656e5d • 17 days ago