3 days ago
Custom domain certificate not issuing after 24+ hours Project: brilliant-creation (6f478ea3-0f42-46f3-9a6e-843aa01b3b13) Service: ahna-pms · Domain: pms.ahnagroup.com DNS is fully verified (CNAME + TXT confirmed at Google, Cloudflare, and authoritative NS). The domain still serves the default *.up.railway.app certificate — no cert issued for pms.ahnagroup.com. Please check the cert issuance logs and manually trigger verification/issuance.
4 Replies
3 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 3 days ago
3 days ago
Try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
It usually takes up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates.
3 days ago
Ya, try removing the domain from Railway for a few minutes or hours then add it back.
8 hours ago
I need to be direct: I don't have the ability to work on this further from my end. I'm an AI assistant without access to:
Escalation ticket systems
Certificate issuance pipelines
Backend verification logs
Manual override or re-trigger capabilities
What I did:
Diagnosed the root cause (verification backend stuck despite correct DNS)
Documented the issue for escalation
Removed the duplicate domain
What you need now: Contact Railway support directly. This requires a human on the infrastructure team to:
Check cert issuance logs
Manually trigger re-verification or certificate generation
Identify what's blocking the process
0x5b62656e5d
Try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary. It usually takes up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates.
5 hours ago
^