a month ago
The domain-status check has reported currentValue: u9tes93v.up.railway.app instead of the requiredValue: euiau8dz.up.railway.app for over an hour, blocking certificate issuance (stuck on VALIDATING_OWNERSHIP). I've independently verified via direct DNS queries to 1.1.1.1 and 8.8.8.8 that the public CNAME record for crm.tsc-pro.fr correctly and consistently resolves to euiau8dz.up.railway.app. Can you invalidate your DNS checker's cache for this domain or manually trigger a re-check?
1 Replies
a month ago
The CNAME target changed because the domain entry was removed and re-added at some point, which generates a fresh target and a fresh verification token each time. Your CNAME is already pointing at the current required target, so that side is correct. However, the TXT verification record is missing entirely: a record at the verification host shown in your domain's DNS settings (the _railway-verify hostname) needs to be created at your DNS provider with the token value the dashboard displays. The certificate cannot progress past ownership validation until that TXT record is in place and propagated.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved thierrybia13-commits • about 1 month ago