16 days ago
Railway reports verified=true for www.mnsignal.com and detects Cloudflare. After one accepted issuance retry on 4 November, the certificate list was still empty and the status was CERTIFICATE_STATUS_TYPE_ISSUE_FAILED with CERTIFICATE_ERROR_TYPE_INTERNAL. A direct TLS check at the Railway origin using www.mnsignal.com for SNI failed hostname verification.
The hostname uses a proxied Cloudflare CNAME. A synthetic HTTPS request under /.well-known/acme-challenge/ redirects to Cloudflare Access. We don't know which challenge Railway attempted. Could Railway staff confirm the actual failed validation or issuance step and advise whether a change is needed? We can provide resource IDs privately.
2 Replies
16 days ago
The certificate for that hostname has now issued and currently shows as valid on our side, and ownership verification is complete.
A plain HTTP request to the ACME challenge path on that hostname currently passes through Cloudflare and reaches our edge with a 200 response, so the Cloudflare Access redirect you saw is not affecting that path right now. Because the hostname is proxied, our record check cannot see the CNAME behind Cloudflare and still lists it as needing an update; the challenge path reaching us is what matters for issuance, and no DNS change is needed for the certificate as it stands.
Status changed to Awaiting User Response Railway • 16 days ago
Railway
The certificate for that hostname has now issued and currently shows as valid on our side, and ownership verification is complete. A plain HTTP request to the ACME challenge path on that hostname currently passes through Cloudflare and reaches our edge with a 200 response, so the Cloudflare Access redirect you saw is not affecting that path right now. Because the hostname is proxied, our record check cannot see the CNAME behind Cloudflare and still lists it as needing an update; the challenge path reaching us is what matters for issuance, and no DNS change is needed for the certificate as it stands.
15 days ago
Thanks — confirmed on our side. The certificate shows as issued, and the plain-HTTP challenge path reaches your edge rather than the Cloudflare Access redirect we saw over HTTPS. We’ll keep /.well-known/acme-challenge/* out of Access and WAF rules so renewals keep working. Marking this solved.
Status changed to Awaiting Railway Response Railway • 15 days ago
Status changed to Solved Railway • 15 days ago