Name mismatch on every site
Likely causes
- - Interception presenting its own certificate
- - Pinned profile config
Verified remedy
Remove interception tools from the path; a tunneling proxy never rewrites names.
Proxy troubleshooting
Ranked causes, ordered diagnostics, and a verified remedy for err_cert_common_name_invalid through a proxy - ending with a final connection check.
Quick answer
Fix: certificate common name mismatch through a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Ranked causes, ordered diagnostics, and a verified remedy for err_cert_common_name_invalid through a proxy - ending with a final connection check.
Fix: certificate common name mismatch through a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Likely causes
Verified remedy
Remove interception tools from the path; a tunneling proxy never rewrites names.
The action completes and the exit IP matches the endpoint.
If curl also fails, the endpoint is unhealthy: swap to a spare.
Facts last reviewed 2026-09-01.
Keep one profile on one static endpoint, verify exit IPs daily, and rotate credentials on a documented schedule.
Work the diagnosis tree top to bottom, confirm endpoint values, test with curl through the endpoint, then run the final connection check.
Buy self-serve now, or talk with us about a larger agency inventory.