2 months ago
Hi Railway team,
My custom domain has been pointing to Railway for over 48 hours but the SSL certificate has not been provisioned. The site is unreachable for users.
Project: CoverageAI
Railway URL:https://coverage-ai-production.up.railway.app (works fine)
Custom domain:www.getscriptcoverage.com
What I've confirmed on my end:
• CNAME is correctly set: www.getscriptcoverage.com → 6f6za9k7.up.railway.app
• DNS has fully propagated — resolves to 151.101.2.15
• Domain is added in the Railway dashboard
The actual error:
SSL: no alternative certificate subject name matches target host name 'www.getscriptcoverage.com'Railway is serving the *.up.railway.app wildcard cert instead of issuing one for www.getscriptcoverage.com. The SSL cert provisioning appears stuck or failed on Railway's side.
Please trigger SSL certificate issuance for www.getscriptcoverage.com or advise on next steps.
Thanks,
David
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your CNAME is correctly propagated, but the SSL certificate is stuck because the TXT verification record has an incorrect value. The record at _railway-verify.www.getscriptcoverage.com currently contains railway-verify=railway-verify=b3b28... (the railway-verify= prefix is doubled). The correct value should be railway-verify=b3b28180d49dd984f34c592f5b5647f06a601353704b2eaae054ed74e061f8a5. Please update the TXT record in your DNS provider to remove the extra railway-verify= prefix, and the certificate will issue automatically once the corrected record propagates.
Status changed to Awaiting User Response Railway • about 2 months ago
angelo-railway
Your CNAME is correctly propagated, but the SSL certificate is stuck because the TXT verification record has an incorrect value. The record at `_railway-verify.www.getscriptcoverage.com` currently contains `railway-verify=railway-verify=b3b28...` (the `railway-verify=` prefix is doubled). The correct value should be `railway-verify=b3b28180d49dd984f34c592f5b5647f06a601353704b2eaae054ed74e061f8a5`. Please update the TXT record in your DNS provider to remove the extra `railway-verify=` prefix, and the certificate will issue automatically once the corrected record propagates.
2 months ago
Fixed that. Appreciate your fast response.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved brody • about 2 months ago