2 months ago
I just went through this with another web app - pay.p4companies.com presented identically and needed a manual re-trigger.. Apologies on my end...
DNS has been correct for hours, verified from 8.8.8.8 and 1.1.1.1:
CNAME ops.p4companies.com → c8fw10cy.up.railway.app (→ 69.46.46.83)
TXT _railway-verify.ops.p4companies.com → railway-verify=600cf570caab0d261b30da6d229efe8cbe97c174549aeb8a948abe9e2c22e544
No CAA on p4companies.com, no conflicting A record. Your edge already routes the host - http://ops.p4companies.com returns 301 → https - but 443 presents CN=*.up.railway.app, so routing is configured and issuance never ran. The dashboard still shows the TXT as unverified, which does not match public DNS.
Please re-trigger verification/issuance on the existing domain entry - removing and re-adding would regenerate the CNAME target and token and require new DNS changes.
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your DNS is correct and we've started a certificate re-issue for the domain, which should complete within a few minutes.
Status changed to Awaiting User Response brody • about 2 months ago
2 months ago
cheers, thanks!
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved Railway • about 2 months ago