Error messages

“Safari can’t establish a secure connection to the server” on Mac

Safari shows this when the secure connection to the server fails before the page loads. Often software or a network in the path causes it, not the site.

Applies to: Safari on macOS 13 Ventura and later. The text was checked on macOS 27.2.Checked: 29 October 2026

Symptoms

Safari says: “Safari can’t open the page … because Safari can’t establish a secure connection to the server …”.
Apps show “A TLS error caused the secure connection to fail.” This is the same failure in the URL Loading System.
The site opens on another network or another device.

Likely causes

Security, VPN or filter software. Software that inspects or filters secure connections can break the handshake.
A network that blocks or changes the connection. Company firewalls, school filters and hotel networks can stop secure connections to some sites.
A Wi-Fi login page. Until you sign in, some public networks answer for every site.
iCloud Private Relay. Some networks and sites do not work with Private Relay.
A problem on the server. If every device and network fails, the server's TLS setup can be the cause.

How to check

Open a different website. If no site opens, the problem is the connection, not this site.
Open the site in another browser, and on a different network, such as your phone's hotspot.
In Terminal, show the TLS handshake. The last lines show where it stops.
```
curl -v -o /dev/null https://example.com
```
Look for filters and network extensions. Choose Apple menu > System Settings > General > Login Items & Extensions.
Click the Info button next to Network Extensions. Note each extension that is on.

How to fix it

If you are on public Wi-Fi, sign in to the network first. See Wi-Fi login page does not appear on a Mac.
If a VPN, proxy or security app is on, turn it off for a short test. Turn it on again after the test.
If Private Relay is on, choose View > Reload and Show IP Address in Safari. See iCloud Private Relay breaks some websites.
If the site works on another network, ask the network's administrator about it.
Update macOS. Safari updates come with macOS updates.
If every network fails, contact the site owner.

With Kilobat

Kilobat's connection doctor tests the site layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.
```
kilobat why https://example.com
```
These Kilobat checks are free. AI agents run them through MCP with diagnose_connection and diagnose_network. See Find why one site or API won't connect.

Questions

Is this the same as “This Connection Is Not Private”?

No. That warning means that Safari got a certificate but cannot trust it. This error means that the secure connection did not complete. See “This Connection Is Not Private” and certificate warnings on a Mac.

Does the date on my Mac matter?

A wrong date usually causes certificate warnings instead. Make sure the date is correct anyway. See NET::ERR_CERT_DATE_INVALID in Chrome on Mac.

Sources

Error text in Safari.framework, macOS 27.2 (Localizable.strings)
Error text in CFNetwork.framework, macOS 27.2 (Localizable.loctable)
Apple Developer: URLError.Code secureConnectionFailed (-1200)
Apple Support: If Safari doesn't work as expected on Mac
curl(1), man page installed with macOS 27.2

Sources checked on 29 October 2026. Man pages are the ones installed with macOS; open one with man <name> in Terminal.