24 days ago
Project: SkopeNow Alerts · Service: skopenow-alerts · Environment: production
Domain: skopenow-alerts.p4secure.com (target port 8080)
The CNAME shows verified, but the _railway-verify TXT has shown as pending for more than 2 hours. The record has been live on public DNS the whole time and matches the value in the dashboard exactly:
_railway-verify.skopenow-alerts.p4secure.com TXT "railway-verify=8d0c2810365ed97a4f286936f8a654374f2ac60222fd8f57ecd6b31e31b2a230"
It resolves on the authoritative nameservers (ns03/ns04.domaincontrol.com), on 1.1.1.1 and on 8.8.8.8. There is no CAA record on the domain. The edge still serves the default *.up.railway.app certificate for this hostname.
We can’t easily change DNS again, so please re-run verification and issue the certificate without removing and re-adding the domain.
1 Reply
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
Your CNAME and verification TXT record are both correct and live, and the TXT value matches exactly, but ownership verification hadn't re-run against it. We've started verification and certificate issuance again for the domain, with no DNS changes or remove-and-re-add needed, and the certificate may take a few minutes to issue.
Status changed to Awaiting User Response sam-a • 24 days ago
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago