3 hours ago
My Railway custom domain app.autoswitch.org is verified in Railway: both required CNAME and TXT records show green.
The generated Railway URL https://autoswitch-production.up.railway.app works on both cellular and Wi‑Fi, and the service deployment is healthy.
However, https://app.autoswitch.org fails worldwide on cellular and Wi‑Fi with Chrome error ERR_SSL_PROTOCOL_ERROR.
DNS is hosted at Namecheap. There is exactly one CNAME for host app pointing to the Railway-provided *.up.railway.app target, the Railway TXT verification record is present, no CAA records exist, and DNSSEC is disabled.
Could you inspect or retry TLS certificate issuance for app.autoswitch.org?
1 Replies
Status changed to Awaiting Railway Response Railway • about 3 hours ago
3 hours ago
The CNAME for this domain at Namecheap is pointing at your service's generated Railway URL, not at the CNAME target Railway assigned to the custom domain. Those are two different values, and requests only reach your service over HTTPS on the custom domain when the record points at the custom domain's own target.
Open the custom domain's entry under your service's Settings, in the Networking section, copy the CNAME target shown there, and set it as the value of the app CNAME record at Namecheap. Your TXT verification record and certificate are already in place, so the CNAME is the only change needed.
Status changed to Awaiting User Response Railway • about 3 hours ago