What does ERR_SSL_PROTOCOL_ERROR mean?

Chrome tried to start an encrypted connection and the server answered with something that is not valid TLS. In almost every case the server is offering a protocol version or cipher the browser refuses, the certificate is broken, or something on the network is intercepting the handshake.

Device-specific

ERR_SSL_PROTOCOL_ERROR on iPhone

Why it happens on iPhone

Safari and iOS Chrome share the system TLS stack, so a configuration profile, a content blocker, or a VPN profile can break the handshake for every browser at once.

The fix on iPhone

Settings → General → VPN & Device Management: remove unknown profiles. Turn off any VPN, then Settings → Safari → Clear History and Website Data.

Is ERR_SSL_PROTOCOL_ERROR happening on your domain?

The SSL checker reads the live handshake: protocol versions offered, cipher suites, chain completeness and expiry. If it cannot complete the handshake either, the fault is server-side and not your browser.

Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

If that didn't fix it

iPhone has its own failure mode, but ERR_SSL_PROTOCOL_ERROR has a wider set of causes that apply everywhere. The most common one overall is: the server only offers tls 1.0 or tls 1.1, which every current browser has disabled.

All causes and fixes for ERR_SSL_PROTOCOL_ERROR

ERR_SSL_PROTOCOL_ERROR on other platforms and devices

Monitor this continuously with LemWatch

A one-off err_ssl_protocol_error monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

Last verified: 16 October 2026 by the Lemwatch research team.