A TLS error caused the secure connection to fail Browser Origin: On your device Last updated 15 Oct 2026

Safari: Safari Can’t Open the Page — A TLS error caused the secure connection to fail

Safari could not set up a secure TLS connection — an expired or untrusted certificate, an outdated server configuration or interference from a proxy/VPN.

Exact message you may see A TLS error caused the secure connection to failThis Connection Is Not PrivateSafari can’t verify the identity of the websiteNSURLErrorDomain error -1200
Explore the map of this error Full error map →
Seen on: Safari macOS iOS

Meaning

Safari enforces App Transport Security-style rules: TLS 1.2+, strong ciphers and valid certificates with proper chains. Failing sites often have an expired certificate, missing intermediates, a very old protocol, or the device clock is wrong.

Common causes

  • Expired, mismatched or untrusted certificate
  • Missing intermediate certificates in the server chain
  • Server limited to old TLS versions or weak ciphers
  • Wrong date/time on the device
  • Intercepting proxy/VPN or content filter

⚡ Quick fix

  1. Check date and time (Set Automatically)
  2. Owners: install the full certificate chain and enable TLS 1.2/1.3
  3. Test with an SSL checker and try without VPN/profile

Detailed fix by platform

macOS

  1. System Settings → General → Date & Time → Set time and date automatically
  2. openssl s_client -connect example.com:443 -servername example.com to inspect the chain

Nginx

  1. ssl_certificate fullchain.pem; ssl_protocols TLSv1.2 TLSv1.3; then reload

How to diagnose

  1. Certificate — Valid, trusted, full chain?
  2. Protocol — TLS 1.2+ offered?
  3. Device — Date correct, no TLS proxy?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

ERR_CERT_AUTHORITY_INVALID — NET::ERR_CERT_AUTHORITY_INVALID (Your connection is not private) (JavaScript)ERR_CERT_AUTHORITY_IN…ERR_CERT_DATE_INVALID — NET::ERR_CERT_DATE_INVALID (certificate expired) (JavaScript)ERR_CERT_DATE_INVALIDERR_CONNECTION_CLOSED — Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED (Browser)ERR_CONNECTION_CLOSEDERR_SSL_OBSOLETE_VERSION — Chrome: Connection not secure — ERR_SSL_OBSOLETE_VERSION (old TLS 1.0/1.1) (Browser)ERR_SSL_OBSOLETE_VERS…ERR_SSL_VERSION_OR_CIPHER_MISMATCH — Chrome: This site can’t provide a secure connection — uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH (Browser)ERR_SSL_VERSION_OR_CI…NET::ERR_CERT_REVOKED — Chrome: Your connection is not private — NET::ERR_CERT_REVOKED (the certificate was revoked) (Browser)NET::ERR_CERT_REVOKEDSafari can’t find the server — Safari: Safari Can’t Open the Page because Safari can’t find the server (Browser)Safari can’t find the…SSL_ERROR_NO_CYPHER_OVERLAP — Firefox: Secure Connection Failed — SSL_ERROR_NO_CYPHER_OVERLAP (no common cipher) (Browser)SSL_ERROR_NO_CYPHER_O…A TLS err…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.