Safari Can't Establish a Secure Connection to the Server: What It Means and What to Check

What the message actually means

When you visit a site whose address begins with https://, your browser and the server perform a brief exchange called a TLS handshake. Both sides confirm that the connection is encrypted and that the server's identity certificate is valid. If any step in that exchange fails, Safari stops and shows the secure connection error rather than load the page over a broken or untrusted channel.

The message is protective — Safari is refusing to proceed because something about the connection does not check out. That something can sit on the website's server, on your network, on your device, or in Safari's own settings.

Is the problem with the site or with your device?

This distinction matters because the fixes are different. A site-side certificate problem is something only the website operator can resolve. A device-side problem is something you can often address yourself.

• If the error appears only on one site and other https:// sites load normally, the problem is almost certainly with that site's certificate or server configuration.
• If the error appears on multiple sites or on sites that were working yesterday, the problem is more likely on your device or network.
• Try the same site in a different browser (Chrome or Firefox). If it loads there, Safari's own settings or certificate trust store may be involved.
• Try the same site on a different device on the same Wi-Fi. If it fails there too, the network may be the factor.

Check your Mac's date and time

TLS certificates carry an expiry date. If your Mac's clock is significantly wrong — even an hour off in the wrong direction — Safari may decide that a valid certificate has expired, or that a certificate is not yet valid. This is one of the most common and most easily overlooked causes of the error.

1. 1

   Open System Settings

   Click the Apple menu, then System Settings (or System Preferences on older macOS versions).

2. 2

   Go to General > Date & Time

   Confirm that 'Set time and date automatically' is turned on and that the correct time zone is selected.

3. 3

   Restart Safari

   Quit Safari fully (Command-Q) and reopen it, then try the site again.

Network and DNS checks

Some Wi-Fi networks — particularly captive portal networks in hotels, airports and workplaces — intercept HTTPS traffic in ways that can trigger this error. A VPN running on your Mac can also interfere with certificate validation.

• Try disconnecting from any VPN and retrying.
• If you are on a captive portal network, open Safari and navigate to a plain http:// address to trigger the sign-in page, complete sign-in, then try your original site.
• Try switching from Wi-Fi to a mobile hotspot to rule out your router or ISP.
• On your Mac, go to System Settings > Network > Wi-Fi and try disconnecting and reconnecting to your network.

Safari-specific checks

Occasionally Safari's website data, an extension, or a security setting can contribute to the error.

1. 1

   Disable Safari extensions temporarily

   In Safari, go to Safari > Settings > Extensions and turn off all extensions. Retry the site. If it loads, re-enable extensions one at a time to identify the culprit.

2. 2

   Clear website data for the affected site

   In Safari > Settings > Privacy, click Manage Website Data, search for the site's domain, and remove its data.

3. 3

   Check Security settings

   In Safari > Settings > Security, confirm that 'Warn when visiting a fraudulent website' is enabled and that nothing unusual is toggled.

macOS and Safari version

Apple periodically updates the list of trusted certificate authorities built into macOS. If your system is significantly out of date, it may not trust certificates issued by newer authorities. Keeping macOS and Safari reasonably current ensures your trust store is current.

Check for updates via Apple menu > System Settings > General > Software Update.

When to stop and what to consider

If the error appears on one specific site and every other https:// site loads normally, you have done what you can. The problem is on the site's server. The site's operator needs to renew or correctly configure their certificate.

If a site you rely on professionally is affected, contact its support team and mention that Safari shows a TLS error. Do not attempt to bypass the warning and load the page anyway unless you have strong reason to trust the site and understand the risk.