“Safari Can’t Establish a Secure Connection”: Causes and Fixes

The “Safari can’t open the page because Safari can’t establish a secure connection to the server” error means Safari couldn’t create an encrypted (HTTPS) connection with the site you’re visiting. It can appear on iPhone, iPad and Mac. Sometimes the problem is only on your device (clock settings, VPN, content restrictions), and sometimes it comes from the site’s SSL configuration.

In this article we explain the causes and step-by-step fixes on iPhone and Mac, and in the last section what site owners need to do.

What Causes the Error?

• Wrong date and time: SSL certificates are valid between certain dates. If the device clock is wrong, a valid certificate looks invalid.
• Screen Time restrictions: the “Limit Adult Websites” option can block some sites with this error.
• VPN, proxy or content blocker: apps that reroute or filter traffic can break the encrypted connection.
• Network issues: Wi-Fi networks with a login page (captive portal) in hotels, cafés and schools, or filtering on the network.
• Private DNS or iCloud Private Relay: some networks and sites may not work well with these features.
• An old iOS / macOS version: outdated systems may not recognise new certificate and encryption standards.
• An SSL problem on the site: an expired certificate, an incomplete intermediate certificate chain or old TLS versions that are no longer supported.

Quick Checks First

1. Try opening the same site in another browser (Chrome, Firefox) or on another device. If it doesn’t open anywhere, the problem is most likely on the site.
2. Switch from Wi-Fi to mobile data (or vice versa) and try again. If it opens on another network, the problem is the network.
3. Make sure you typed the address correctly and it starts with https://.
4. Close Safari completely and reopen it; restart the device if needed.

Fixes on iPhone and iPad

1. Set the date and time automatically

Turn on Set Automatically under Settings → General → Date & Time.

2. Check Screen Time content restrictions

Under Settings → Screen Time → Content & Privacy Restrictions → App Store, Media, Web & Games → Web Content, try the Unrestricted option. Menu names may vary slightly by iOS version. If the device is managed by a parent or organisation, you may need their permission to change this setting.

3. Turn off VPN and content blockers

Turn off the VPN and try the site again. Temporarily disable blockers under Settings → Safari → Extensions (or Content Blockers). For the steps, see our article how to turn off a VPN.

4. Temporarily turn off iCloud Private Relay

If you use iCloud+, temporarily turn off the feature under Settings → [your name] → iCloud → Private Relay and try again. To turn it off for a specific Wi-Fi network, tap the (i) icon next to the network in Wi-Fi settings.

5. Clear Safari history and website data

Settings → Safari → Clear History and Website Data. This also signs you out of open sessions.

6. Update iOS

Install the latest version under Settings → General → Software Update.

7. Reset network settings

If the other steps don’t work, go to Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings. Saved Wi-Fi passwords and VPN settings are deleted.

Fixes on Mac

1. Date and time: turn on automatic setting under System Settings → General → Date & Time.
2. Safari extensions: temporarily turn off extensions under Safari → Settings → Extensions.
3. Website data: delete the relevant site’s data under Safari → Settings → Privacy → Manage Website Data.
4. VPN and proxy: disconnect the VPN under System Settings → Network and make sure proxy settings are off.
5. Keychain: if you previously marked a certificate as “Always Trust” or “Never Trust” manually, check it in the Keychain Access app.
6. macOS update: System Settings → General → Software Update.

DNS-Related Cases

A DNS server you set manually or a DNS filtering profile can redirect the site to a different address and cause a certificate mismatch. Try removing the DNS profile you use and switching back to automatic DNS.

If You Own the Site: What to Check on the Server

If your visitors get this error in Safari and there are similar warnings in other browsers, the problem is on your site.

• Certificate validity: make sure the certificate hasn’t expired and automatic renewal works.
• Certificate chain: check that intermediate certificates are fully installed. An incomplete chain can work in some browsers but fail in Safari.
• Domain match: verify that the certificate covers both yourdomain.com and www.yourdomain.com.
• TLS version: make sure your server supports TLS 1.2 and TLS 1.3; the old TLS 1.0 and 1.1 aren’t supported by current browsers.
• Testing: test your certificate and encryption settings with free tools such as Qualys SSL Labs.

If you use cPanel, our guide to installing an SSL certificate in cPanel can help.

Frequently Asked Questions

What should I do if the error only appears on one site?

Try the site in another browser and on another network. If you get the same error everywhere, the problem is the site’s certificate; let the site owner know.

What could cause the error on all sites?

The most common causes are a wrong date/time, a VPN or proxy, a DNS profile and filtering on the network you’re connected to.

What do similar errors look like in Chrome?

In Chrome they usually appear as “Your connection is not private” or ERR_SSL_PROTOCOL_ERROR. For the latter, see our article fixing ERR_SSL_PROTOCOL_ERROR.

Is it safe to ignore the error and continue to the site?

No. Especially on sites where you’ll enter passwords or card details, don’t proceed if a secure connection can’t be established.