a month ago
Hi,
My custom domain pmoiraq.com won't get an SSL certificate issued, despite DNS being correctly configured.
Project details:
- Project name: capex25-app
- Project ID: e052bc32-c2ca-4de9-94de-10731ed850ea
- Service ID: 65280e36-200d-4195-a2ab-3f17f9260ab0
- Custom domain ID: d221c86d-f8f1-49c9-84f1-f1671d95e6b0
- Custom domain: pmoiraq.com
Status:
- DNS is fully propagated — Railway's API confirms currentValue: 60qqw1yp.up.railway.app and status DNS_RECORD_STATUS_PROPAGATED
- However, customDomain.certificates is empty [] — no cert has been issued
- Visiting https://pmoiraq.com/ returns Railway's 404 fallback (x-railway-fallback: true) and serves the *.up.railway.app wildcard cert instead of a
domain-specific Let's Encrypt cert
- I have already tried: redeploying the service, deleting and re-adding the custom domain, and updating the CNAME/ALIAS target in DNS — none of these
triggered cert issuance
- No CAA records on the domain are blocking Let's Encrypt
- The domain has been waiting for a cert for over 6 hours
Could you please force-trigger Let's Encrypt cert issuance on your end, or investigate why the automated cert provisioning is stuck for this domain?
Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago
a month ago
I ran nslookup on your domain and I couldn't find any CNAME records attached to the root domain...
I'd try removing all associated records from Railway and your DNS provider, waiting for ~10-15 mins, then readding them back.