5 days ago
Hi, my custom domain www.mmsupplements.shop is stuck. Railway won't issue an SSL certificate for it despite everything showing as correctly configured.
Details:
- Project ID: a5164571-f6ec-495b-bd6a-faf6b0031d7b
- Service ID: 64c2ad83-4612-4647-83ca-4d23eec612a3
- Environment: production
- Custom domain ID: b3f35df5-506a-4d79-be67-70fd9fca7425
- Domain: www.mmsupplements.shop
- targetPort: 3000
Status:
- DNS shows DNS_RECORD_STATUS_PROPAGATED with currentValue matching requiredValue (meul93a4.up.railway.app)
- certificates array has been empty for 5+ hours
- Edge is still serving the *.up.railway.app wildcard cert instead of a domain-specific one
What I've already tried:
- Delete + recreate the custom domain (twice)
- customDomainIssueCertificate mutation multiple times
- Set targetPort explicitly to 3000
- Multiple service redeploys
- Verified no CAA records blocking Let's Encrypt
- Verified /.well-known/acme-challenge/ path is reachable via HTTP (returns 404 from railway-edge, not a redirect)
Could you trigger ACME issuance manually or check for backend errors on this domain? Thanks.
1 Replies
5 days ago
Your CNAME record is correctly propagated, but the domain is missing its ownership-verification TXT record, which is why the certificate is stuck at "validating ownership." You need to add a TXT record at your registrar (Porkbun) with the host _railway-verify.www and the value shown on the custom domain's settings panel in your Railway dashboard. Once that record propagates, verification will complete and the certificate will issue. Reply here once you've added it and we can confirm propagation.
Status changed to Awaiting User Response Railway • 5 days ago