15 days ago
DNS is correct and has been for hours — verified from both 8.8.8.8 and 1.1.1.1:
CNAME pay.p4companies.com → wxa7iciu.up.railway.app
TXT _railway-verify.pay.p4companies.com → railway-verify=059cd2911208a1896b702f4b8cca105885adc43029a9db1c3c1bdbed9b057f12
There is no CAA record on p4companies.com, so Let's Encrypt is permitted to issue. There is no conflicting A record — the address resolves through the CNAME chain to 69.46.46.115, the same IP as wxa7iciu.up.railway.app.
Your edge already recognises the hostname: http://pay.p4companies.com returns 301 → https://pay.p4companies.com. On 443 it presents CN=*.up.railway.app rather than a certificate for the domain, so routing is configured but issuance never ran.
Please re-trigger verification/issuance for the existing domain entry. I'd prefer not to remove and re-add it, as that would regenerate the CNAME target and verification token and require new DNS changes.
2 Replies
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
Your DNS is correct. The certificate pipeline for pay.p4companies.com got stuck - the original issuance workflow ended before your DNS records were in place, and it never re-ran once they propagated. We've re-triggered certificate issuance, which will also complete domain verification. It should finish within a few minutes.
Status changed to Awaiting User Response Railway • 15 days ago
Status changed to Solved sam-a • 15 days ago
sam-a
Your DNS is correct. The certificate pipeline for pay.p4companies.com got stuck - the original issuance workflow ended before your DNS records were in place, and it never re-ran once they propagated. We've re-triggered certificate issuance, which will also complete domain verification. It should finish within a few minutes.
14 days ago
thanks!
Status changed to Awaiting Railway Response Railway • 14 days ago
Status changed to Solved Railway • 14 days ago