an hour ago
I'm experiencing an issue with SSL certificate provisioning for a custom domain purchased and managed through Railway.
The domain is attached to a frontend service, and the Railway-generated URL works correctly. However, the custom domain remains stuck with the following status:
"Certificate Authority is validating challenges"
When attempting to access the domain over HTTPS, I consistently receive:
SEC_E_WRONG_PRINCIPAL (0x80090322)
Troubleshooting completed:
- Verified that the domain's DNS resolves correctly.
- Confirmed the DNS target matches the Railway-provided target.
- Verified that the domain ownership TXT record is publicly accessible.
- Removed and reattached the custom domain.
- Confirmed the frontend service is running correctly.
Unfortunately, the certificate validation issue persists.
Has anyone experienced something similar with Railway-managed domains? Is there a way to manually restart certificate provisioning, or is this something that needs to be resolved on Railway's side?
Any suggestions would be appreciated. Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • 17 minutes ago
a minute ago
Update: Additional DNS verification completed
I've completed some additional troubleshooting:
- The domain's ANAME target resolves correctly.
- The domain verification TXT record is publicly accessible.
- A DNS CAA lookup returned no CAA records, so there appear to be no certificate authority restrictions.
- The application works through its Railway-generated domain.
- Removing and reattaching the custom domain did not resolve the issue.
The custom domain continues to show "Certificate Authority is validating challenges", and HTTPS requests fail with SEC_E_WRONG_PRINCIPAL.
Is there a known issue with SSL certificate provisioning for Railway-purchased domains, or a way to restart the ACME validation process?
Any guidance would be appreciated.
Status changed to Awaiting Railway Response Railway • 1 minute ago