2 months ago
Similar issue to https://station.railway.com/questions/custom-domain-txt-verification-stuck-cn-61486ab9 and https://station.railway.com/questions/custom-domain-stuck-on-txt-verification-8965ecbe and other recent problems.
TXT verification is failing while CNAME verification succeeds for both domains pai.deplanv.com and assistant.polispark.gr.
TXT record is propagated globally. For example I used dnschecker.org and Powershell (Resolve-DnsName) for URL _railway-verify.pai.deplanv.com domain and it shows the correct TXT value.
There is another company that handles the DNS records, so I can't ask them every day to re-add or modify the DNS records because Railway can't see them.
Can you trigger the certificate issuance for these 2 domains?
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your DNS records are correct for both domains. The certificate verification workflow got stuck and never re-ran after the TXT records propagated. We've triggered certificate re-issuance for both pai.deplanv.com and assistant.polispark.gr, which should complete within a few minutes.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved chandrika • about 2 months ago