3 hours ago
Hello Railway Support,
I'm migrating our production application to Railway. Our frontend is deployed and running successfully, but Railway failed to issue an SSL certificate for our custom domain.
Project: raqmm-agency-core
Environment: production
Service: agency-web
Custom domain: agency.raqmm.org
The domain ownership verification succeeded. DNS was correctly configured to point to Railway, and public DNS propagation was confirmed.
Railway initially showed ISSUING for several hours, then changed to ISSUE_FAILED with this error:
An internal error occurred. Please retry or contact support.
The certificate status also indicated retryable: true.
We investigated DNS propagation, authoritative DNS, CAA records, DNSSEC, and Railway edge routing. We found no DNS configuration issue that explains the failure.
Current production situation:
To avoid disrupting users, we temporarily restored DNS to our Hostinger VPS. The VPS now acts only as a Caddy reverse proxy to our Railway production frontend. The application itself continues running on Railway.
We want to complete the migration and have Railway serve agency.raqmm.org directly, without depending on the VPS.
Could you please:
Investigate the internal certificate issuance failure.
Determine whether the certificate can be repaired or reissued without requiring us to interrupt production traffic.
Advise on the safest procedure to restore direct DNS routing to Railway.
We can provide the certificate failure evidence and deployment details if needed.
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • about 3 hours ago
Status changed to Solved mohamedkhair1209 • about 3 hours ago
3 hours ago
Hello Railway Support,
I'm following up on this production SSL certificate issue.
The issue is still unresolved. I checked the production custom-domain configuration again, and Railway still requests the CNAME record for agency.raqmm.org.
Our current DNS intentionally points to our Hostinger VPS (187.126.25.114), which is running a temporary Caddy reverse proxy to our Railway production frontend. This keeps the application accessible while we resolve the certificate issue.
We do not want to change production DNS or risk interrupting users just to retry certificate issuance.
Could your team please investigate the previous internal certificate issuance failure (ISSUE_FAILED) and advise whether you can repair or reissue the certificate while our current DNS configuration remains in place?
Please reopen this request and keep it open until the issue is resolved.
Thank you.
Status changed to Awaiting Railway Response Railway • about 3 hours ago
Status changed to Solved mohamedkhair1209 • about 3 hours ago