a month ago
Service: Righand (project: hearty-enjoyment, project ID e5dce2f2-ffc6-4677-8f16-d3912934cebd, service ID ff65980e-67ac-4897-a1bc-ff17245b6f76)
Custom domain: righand.gilliomfrontlinedigital.com, target port 8080
The TLS certificate for this custom domain has been stuck in ISSUING for over 3 hours, with no error message. DNS has been correct and fully propagated the entire time: the required CNAME (jla2ge45.up.railway.app) matches the current value exactly, and domain-status reports verified: true. There is no CAA record anywhere in the gilliomfrontlinedigital.com zone that could be restricting the certificate authority.
I've removed and re-added this custom domain four separate times to force a fresh certificate request. Each time, DNS re-verifies within seconds, and the certificate goes straight back to ISSUING and sits there indefinitely.
This isn't a DNS configuration issue — everything checkable from the outside is clean. Please check the actual certificate authority response/error for this domain server-side. Happy to provide any additional logs or IDs needed.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your DNS is correct and the domain is verified, but the certificate issuance workflow stalled. We've re-triggered certificate issuance for this domain, which may take a few minutes to complete.
Status changed to Awaiting User Response brody • about 1 month ago
a month 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 • 28 days ago