22 days ago
Service: seds-river-club (project: seds-river-club)
2 custom domains stuck unable to get SSL cert for 15+ min:
- club.seds-kanchanaburi.com
DNS is correctly propagated (verified via Google/Cloudflare DNS) but certificate stays stuck at validating ownership. Dashboard also shows Waiting for DNS update even though DNS is actually correct. Based on similar threads on this forum, this looks like the certificate verification workflow stalling and needing a manual re-trigger from Railway staff. This has happened consistently across 3 different domain additions on this same service.
Can you manually re-trigger certificate issuance for this service?
3 Replies
22 days ago
We can only find the www subdomain variant on your service. Its traffic CNAME is set correctly, but there is no TXT record published at the verification host (the one starting with _railway-verify). Certificates require both the CNAME and this TXT ownership record. Create a TXT record at the host shown in that domain's DNS settings in your service's Settings, with the value railway-verify=15fec92904ffabd95cb4c61d924d7de6322c0870620f5235ad4880815a3cd82c. The non-www variant does not appear on your Railway service and would need to be added separately.
Status changed to Awaiting User Response Railway • 22 days ago
Railway
We can only find the `www` subdomain variant on your service. Its traffic CNAME is set correctly, but there is no TXT record published at the verification host (the one starting with `_railway-verify`). Certificates require both the CNAME and this TXT ownership record. Create a TXT record at the host shown in that domain's DNS settings in your service's Settings, with the value `railway-verify=15fec92904ffabd95cb4c61d924d7de6322c0870620f5235ad4880815a3cd82c`. The non-`www` variant does not appear on your Railway service and would need to be added separately.
22 days ago
Thanks - I've added the missing TXT record (_railway-verify.www.club) matching the value you provided, and confirmed it's propagated via Google/Cloudflare DNS. Certificate status is still stuck at VALIDATING_OWNERSHIP though. Could someone manually re-trigger the certificate issuance for this domain, similar to what was done in a similar thread?
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Update: the certificate came through and is now VALID/verified - both domains are live and working. Thanks for the help!
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Solved Railway • 22 days ago