a day ago
Custom domains buddytourguide.com and www.buddytourguide.com on service buddy-tour. The CNAME for www (npy97ra9.up.railway.app) resolves correctly everywhere, but the domain has been stuck on “Issuing TLS certificate” for many hours. The DNS records popup shows only a CNAME row even though it says “Add both records”, so I can’t see the TXT verification token. Please send me the exact name and value of the TXT record for www.buddytourguide.com (expected: _railway-verify.www) and trigger a certificate retry. I have not deleted and re-added the domain, to avoid Let’s Encrypt rate limits.
This domain previously worked on Railway while hosted on Hostinger. It was then re-registered on GoDaddy, so the old TXT verification record was lost and the previous certificate has expired (NET::ERR_CERT_DATE_INVALID)
4 Replies
Status changed to Awaiting Railway Response Railway • about 23 hours ago
a day ago
Before the move to GoDaddy, the old zone had www CNAME → npy97ra9.up.railway.app (same value as now) and @ ALIAS → npy97ra9.up.railway.app, with no TXT record, and it worked.
Status changed to Awaiting Railway Response Railway • about 23 hours ago
a day ago
That domain is already verified on our side and its CNAME is resolving correctly, so no TXT record is needed for it, which is why the dialog only shows the CNAME row.
We've started a fresh certificate issuance for it, and it may take a few minutes to complete.
Status changed to Awaiting User Response sam-a • about 23 hours ago
sam-a
That domain is already verified on our side and its CNAME is resolving correctly, so no TXT record is needed for it, which is why the dialog only shows the CNAME row. We've started a fresh certificate issuance for it, and it may take a few minutes to complete.
5 hours ago
Thanks. The custom domain www.buddytourguide.com now shows a green check in the dashboard, but opening https://www.buddytourguide.com still returns ERR_SSL_PROTOCOL_ERROR (tested in incognito, on mobile data too). Could you check whether the new certificate was actually issued and deployed to the edge?
Status changed to Awaiting Railway Response Railway • about 5 hours ago
5 hours ago
The certificate for the www domain was issued and is live on our edge: it serves a valid Let's Encrypt certificate for that hostname, then your app answers with a 301 redirect to the root domain. The error comes from that redirect target, because the root domain currently resolves to an address outside Railway, and that server is the one dropping the secure connection.
To fix it, point the root domain at the target shown for it in the service's Settings, under Networking (it is a different value from the www target). If GoDaddy cannot set a CNAME on the root, you will need a provider that supports CNAME flattening or ALIAS records at the root.
Status changed to Awaiting User Response Railway • about 5 hours ago