--- title: "Safari can’t establish a secure connection to the server: fix on Mac · Kilobat Guides" url: "https://kilobat.app/guides/safari-cant-establish-secure-connection.html" description: "Safari can't open a page because it can't establish a secure connection to the server. Find what blocks the TLS connection and fix it." --- 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 1. Open a different website. If no site opens, the problem is the connection, not this site. 2. Open the site in another browser, and on a different network, such as your phone's hotspot. 3. In Terminal, show the TLS handshake. The last lines show where it stops. ``` curl -v -o /dev/null https://example.com ``` 4. Look for filters and network extensions. Choose Apple menu > System Settings > General > Login Items & Extensions. 5. Click the Info button next to Network Extensions. Note each extension that is on. ## How to fix it 1. If you are on public Wi-Fi, sign in to the network first. See [Wi-Fi login page does not appear on a Mac](https://kilobat.app/guides/captive-portal-not-appearing.html). 2. If a VPN, proxy or security app is on, turn it off for a short test. Turn it on again after the test. 3. If Private Relay is on, choose View > Reload and Show IP Address in Safari. See [iCloud Private Relay breaks some websites](https://kilobat.app/guides/icloud-private-relay-sites.html). 4. If the site works on another network, ask the network's administrator about it. 5. Update macOS. Safari updates come with macOS updates. 6. If every network fails, contact the site owner. ## With Kilobat 1. 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 ``` 2. 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](https://kilobat.app/guides/recipes/why-cant-it-connect.html). ## 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](https://kilobat.app/guides/connection-not-private-mac.html). **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](https://kilobat.app/guides/err-cert-date-invalid.html). ## 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)](https://developer.apple.com/documentation/foundation/urlerror/code/secureconnectionfailed) - [Apple Support: If Safari doesn't work as expected on Mac](https://support.apple.com/en-us/102564) - 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 ` in Terminal. ## Related guides - [“This Connection Is Not Private” and certificate warnings on a Mac](https://kilobat.app/guides/connection-not-private-mac.html): Safari shows a certificate warning when it cannot confirm the identity of a website. - [A content filter blocks websites on a Mac](https://kilobat.app/guides/content-filter-blocking.html): A content filter examines web traffic and blocks some sites. - [Little Snitch, LuLu and other network extensions conflict on a Mac](https://kilobat.app/guides/network-extension-conflicts.html): Firewalls, VPNs and content filters on macOS use network extensions. - [iCloud Private Relay breaks some websites](https://kilobat.app/guides/icloud-private-relay-sites.html): iCloud Private Relay sends Safari traffic through two relays. - [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-connect.html): When the internet works but one address fails, Kilobat checks each layer in turn.