How to Fix the SSL Connection Error on iPhone

An SSL error on an iPhone means iOS refused to open an encrypted connection to a website or to an app’s server. Safari usually reports it as This Connection Is Not Private, while apps tend to fail with a shorter complaint about a secure connection that could not be made.

Sometimes the problem really is your device, and two taps clear it. More often the certificate on the website is at fault, and no setting on your iPhone will change that. This guide shows you how to tell the two apart first, then works through the fixes that apply on current iOS.

Table of Contents

1. What Is an SSL Error on iPhone?
2. The Error Messages iOS Actually Shows
3. Is It Your iPhone or the Website?
4. Causes of the SSL Connection Error on iPhone
5. How to Fix the SSL Error on iPhone
6. What Will Not Fix an SSL Error on iPhone
7. If You Own the Website
8. Frequently Asked Questions

What Is an SSL Error on iPhone?

Every time your iPhone opens an HTTPS connection, it runs a check before any data moves. During the SSL handshake, the server presents its SSL certificate, and iOS verifies three things: that the certificate was issued by a Certificate Authority it trusts, that it covers the exact hostname you are visiting, and that the current date falls inside its validity window.

If any one of those checks fails, iOS stops. It does not load the page in a degraded state, and it does not warn you and continue. SSL, or Secure Sockets Layer, and its successor TLS exist precisely so that a connection either encrypts data and is verified, or does not happen at all.

That is why the same error message covers very different problems. A clock that is three days behind and a certificate that expired last month produce identical symptoms on your screen, even though one is fixed in Settings and the other can only be fixed by the site owner.

The Error Messages iOS Actually Shows

iOS words the failure differently depending on which app hit it. Recognizing the wording helps, because it tells you which part of the system rejected the certificate:

• This Connection Is Not Private, in Safari, often followed by a line saying the website may be impersonating the domain you asked for. This is Safari’s standard certificate warning and the most common one people search for.
• Safari can’t verify the identity of the website, a related Safari wording that appears with a certificate the browser cannot validate.
• An SSL error has occurred and a secure connection to the server cannot be made, which is what third-party apps usually surface when their network request fails validation.
• Cannot Verify Server Identity, the alert the Mail app shows when your mail server presents a certificate iOS will not accept.

If a browser other than Safari is involved, you may instead see a Chrome or Firefox style code such as NET::ERR_CERT_DATE_INVALID or NET::ERR_CERT_AUTHORITY_INVALID. Those codes are more specific than Safari’s wording, so they are worth reading before you start changing settings.

Is It Your iPhone or the Website?

Three checks separate a device problem from a server problem in under a minute, and they save you from working through fixes that were never going to apply.

1. Open the same page on another device on the same network. If a laptop or a second phone shows a warning too, the certificate is the problem and your iPhone is reporting it correctly.
2. Turn Wi-Fi off and load the page over cellular data. If it works on cellular and fails on Wi-Fi, the network is interfering with the connection, not your phone and not the site.
3. Scan the domain. Run it through our free SSL Checker, which reports the expiry date, the hostnames the certificate covers, and whether the intermediate chain is complete. Those are the three things iOS rejects a certificate for, and the scan answers all three from outside your device.

If the scan comes back clean and the page still fails only on your iPhone, the cause is on your device or on your network, and the fixes below apply. If the scan reports a problem, skip ahead: nothing you change in Settings will repair someone else’s certificate.

Causes of the SSL Connection Error on iPhone

Wrong date and time on your device

Every certificate carries a fixed validity window, and iOS compares that window against your device clock. If the clock is wrong by enough, a perfectly valid certificate reads as expired or not yet valid, and the handshake fails. This is the single most common device-side cause, and it is the one worth checking first because the fix takes seconds.

Expired SSL certificate on the server

Certificates have a deliberate lifespan, after which they stop being valid. It is a safety feature: it stops old, potentially compromised certificates from being used indefinitely. When one lapses, the server can no longer prove its identity, and your iPhone refuses the connection.

There is not much you can do about an expired certificate. It is a server-side issue, and the only useful step is to notify the site owner so they can renew the certificate. Until they do, avoid sending anything sensitive to that site, since you have no way to confirm who is on the other end.

A certificate your iPhone does not trust

An installed certificate is what triggers the padlock and the HTTPS protocol, but only if iOS trusts the authority that issued it. Apple ships its own trust store, so a certificate signed by an internal corporate CA, an untrusted Certificate Authority (CA), or a self-signed certificate is rejected. These certificates still encrypt traffic, but they do not prove the site’s identity, which is the part iOS insists on.

Apple also publishes its own baseline for what it will trust. A TLS server certificate must present the server’s DNS name in the Subject Alternative Name extension, since names in the Common Name field are no longer trusted; it must be signed with a SHA-2 family algorithm; and RSA keys must be at least 2048 bits. Apple states that connections to servers violating these requirements fail outright, so a certificate that misses any of them is refused by iOS even when older or less strict clients still accept it.

An incomplete certificate chain

This is the classic cause behind “the site works on my laptop but not on my iPhone”. A server is supposed to send its own certificate plus every intermediate certificate that links it back to a trusted root. When an intermediate is missing, desktop browsers often paper over the gap: they can download it on the fly using the Authority Information Access extension, and they may already hold it from an earlier visit to another site issued by the same Certificate Authority. iOS does neither reliably, so the chain stays broken and the connection fails.

A scan will name the missing intermediate, and the fix is on the server. See our guide on the expired intermediate SSL certificate error for the related case where the intermediate is present but out of date.

Something on the network is intercepting HTTPS

This is the most common real cause of a certificate warning on an iPhone that is otherwise configured correctly. Anything that sits between your device and the site has to present a certificate of its own, and iOS will not accept it:

• Captive portals on hotel, airport, and cafe Wi-Fi redirect your first request to a login page. When your phone tries to reach an HTTPS address before you have signed in, the redirect breaks the connection.
• VPN apps and DNS profiles reroute traffic, and a misbehaving or expired one produces certificate errors across every app at once.
• Content blockers and filtering services, including parental control and ad-filtering products, inspect traffic and can break the handshake for sites they do not recognize.
• Corporate proxies on managed devices. If your iPhone is enrolled in mobile device management, a proxy may be decrypting traffic using a company root certificate that is missing or no longer trusted.

Treat a certificate warning on public Wi-Fi as a stop sign rather than an inconvenience. On an untrusted network, it is one of the few visible signs that somebody may be reading the connection.

A manually installed certificate that was never trusted

If you installed a root certificate yourself, by opening it from an email or downloading it from a webpage, iOS does not automatically trust it for SSL. Apple treats installing and trusting as two separate decisions, so the certificate sits on the device doing nothing until you enable it under Certificate Trust Settings. This trips up almost everyone connecting to an internal or development server for the first time.

Certificates delivered through mobile device management or Apple Configurator are the exception: those are trusted for SSL automatically when they are installed.

Outdated iOS or an outdated app

The list of root certificates your iPhone trusts ships with iOS, and so does its support for current TLS protocol versions. An iPhone that has not been updated in a long time can be missing a root that a Certificate Authority started using after that release, which makes newly issued certificates look untrustworthy even though nothing is wrong with them.

Apps have their own version of this problem. Some pin a specific certificate or issuer in the app binary, so when the site rotates its certificate, the installed app rejects it until a new build ships. That is why an SSL error inside one app while Safari works normally usually points at the app, not at the phone.

Network settings on the device

Misconfigured network settings do not break TLS directly, but they can send you somewhere you did not intend to go:

• DNS settings translate a domain name into an IP address. If they resolve a name to the wrong server, that server answers with a certificate issued for a different hostname, and iOS reports a certificate error rather than a DNS one.
• Proxy settings configured manually or pushed by a configuration profile route your traffic through another machine that terminates the connection first.
• Stale saved state for a specific site, held in Safari’s website data, can keep an error on screen after the underlying problem has already been fixed.

How to Fix the SSL Error on iPhone

Work through these in order. They run from the quickest and most likely to the most disruptive, and the paths below follow current iOS, which is iOS 26 at the time of writing. On older releases some items sit one level higher in Settings, which is noted where it matters.

1. Set the date and time automatically

1. Open Settings and tap General.
2. Tap Date & Time.
3. Turn on Set Automatically.
4. Confirm the iPhone has a working Wi-Fi or cellular connection, because automatic time needs the network to sync.
5. Reopen the page or restart the app that showed the error.

If Set Automatically is already on and the clock is still wrong, restart the iPhone and check again once it reconnects to the network.

2. Clear Safari’s website data

Clearing Safari’s stored data removes any cached state it is holding for the site, which is what you want when the certificate was recently fixed but the warning keeps appearing.

1. Go to Settings, tap Apps, then select Safari. The Apps section arrived in iOS 18; on earlier releases, Safari appears directly in the main Settings list.
2. Scroll down and tap Clear History and Website Data.
3. Confirm the timeframe you want to clear, then tap Clear History.

If you would rather keep your browsing history, take the narrower route instead: Settings > Apps > Safari > Advanced > Website Data, then tap Remove All Website Data. That clears cookies and cached site data while leaving history intact.

3. Test the same page on cellular data

Turn Wi-Fi off in Settings or Control Center and load the page again over cellular. If it works, the Wi-Fi network is the problem, and you have narrowed the search from your whole phone to one network.

On a guest or public network, open a plain HTTP page first so the captive portal login screen can appear, sign in, and only then retry the HTTPS site. Never accept a certificate warning in order to get through a portal login.

4. Turn off VPNs, content blockers, and DNS profiles

If the error shows up in several apps at once, something is filtering traffic device-wide. Check these three places:

• Settings > General > VPN & Device Management lists every configuration profile installed on the device, including VPN and DNS profiles. Disable or remove anything you do not recognize.
• Settings > Apps > Safari > Extensions shows content blockers. Turn them off temporarily and retry the page.
• Quit any VPN app fully rather than just disconnecting it, since some keep a network extension running in the background.

On a work phone, a profile may be there deliberately. Ask your IT team before removing it, because deleting a profile also deletes the settings, apps, and data tied to it.

5. Enable trust for a certificate you installed yourself

This is the step most guides leave out, and it is the one that fixes internal, staging, and development servers. Installing a root certificate is not enough on its own: you have to switch trust on afterwards.

1. Go to Settings > General > About.
2. Scroll to the bottom and tap Certificate Trust Settings.
3. Under Enable full trust for root certificates, turn on the switch next to your certificate.

If Enable full trust for root certificates does not appear at all, no additional certificates are installed on the device, and the certificate you thought you added never made it. Check Settings > General > VPN & Device Management to confirm the profile is there.

Enable trust only for a root you obtained from a source you control or trust completely. A root certificate you trust can be used to issue a certificate for any website, which means whoever holds its private key can read connections your iPhone believes are private.

6. Update iOS

Updates refresh the trusted root store and the TLS stack, which resolves errors caused by certificates issued under newer roots.

1. Connect the iPhone to Wi-Fi and to power.
2. Go to Settings > General > Software Update. The installed version is shown, along with any update available.
3. Tap Download and Install and follow the onscreen instructions.

While you are on that screen, tap Automatic Updates and turn it on so the device keeps its trust store current without you having to think about it.

7. Update the app that shows the error

If the failure happens in one app while Safari loads the same site normally, the app is the thing to update. Apps that pin a certificate stop working the moment the service rotates it, and the developer’s fix arrives as an app update.

1. Open the App Store.
2. Tap the account button or your photo at the top of the screen.
3. Tap App Updates, then tap Update next to the app, or Update All.

If the app is already current and still fails, report it to the developer. There is nothing to change on your side.

8. Change your DNS servers

Switching to a public resolver rules out a DNS server that is answering with the wrong address or failing lookups. iOS stores DNS settings per Wi-Fi network, so you set them on the network you are having trouble with, and they do not follow you to other networks or to cellular.

1. Open Settings and tap Wi-Fi.
2. Tap the information button next to the network you are connected to.
3. Scroll down to DNS and tap Configure DNS.
4. Switch from Automatic to Manual.
5. Remove the existing entries, tap Add Server, and enter the addresses below.
6. Tap Save, then reload the page.

Google Public DNS:

8.8.8.8
8.8.4.4

OpenDNS:

208.67.222.222
208.67.220.220

To undo the change later, return to Configure DNS and switch back to Automatic.

9. Reset network settings

This is the fix for corrupted network settings, and it belongs last because of what it takes with it.

1. Go to Settings and tap General.
2. Tap Transfer or Reset iPhone, then tap Reset.
3. Tap Reset Network Settings and confirm.

Be careful not to pick Erase All Content and Settings, which wipes the device. Resetting network settings removes saved Wi-Fi networks and their passwords, cellular settings, and VPN and APN settings that were not installed by a configuration profile. It also renames the device back to iPhone and, importantly, changes manually trusted certificates back to untrusted.

That last detail matters for the order you do things in. If you resolved the error in step 5 by trusting your own root certificate, a network reset undoes it and you will have to enable trust again.

10. Contact the website owner

When the certificate itself is the problem, reporting it is the fix. Site owners frequently do not know, because their own browsers may be masking a missing intermediate that iOS will not tolerate.

• Take a screenshot of the error so they can see the exact wording.
• Find a contact route: an email address, a contact form, or a support number on the site or in the app listing.
• Try social media if nothing else is published. Support accounts often respond faster than contact forms.

Include the full URL, your iOS version, and whether the page also fails over cellular. That combination tells them within minutes whether they are looking at a broken certificate or at a single network.

If you have to open the page anyway

Safari lets you continue past the warning. Tap Show Details, tap visit this website, then confirm with Visit Website.

Do this only when you know exactly why the certificate is failing, for example a test server of your own. Never bypass the warning to reach banking, email, shopping, or any page where you sign in, and never bypass it on public Wi-Fi. The warning exists because iOS cannot confirm who is on the other end of the connection, and continuing means accepting that risk yourself.

What Will Not Fix an SSL Error on iPhone

Several widely repeated fixes have no effect on certificate validation at all. Skipping them saves time:

• Turning on Location Services. Your location is not an input to TLS or to certificate validation, and no Apple documentation connects the two. The confusion comes from time zones: with Set Automatically enabled, iOS uses Location Services to choose your time zone. Certificate validity is evaluated against absolute time, not against the zone your clock displays, so the zone cannot make a valid certificate fail. Fix the clock, not the location permission.
• Installing an antivirus or firewall app. iOS does not give third-party apps the ability to filter another app’s traffic the way desktop security software does. Products marketed that way on iPhone operate as VPNs or content blockers, and those are far more likely to cause a certificate warning than to clear one.
• Bypassing the warning as a routine step. Continuing past the error loads the page, but it does not repair anything. The connection stays unverified every time you use it.

If You Own the Website

If visitors report SSL errors on iPhone while the site loads fine on your desktop, the certificate is almost always the cause. Four checks cover it:

• Scan the domain with our SSL Checker and read the chain section, not just the expiry date.
• Serve the complete chain. Your server must send the leaf certificate and every intermediate above it. A missing intermediate is the most frequent reason a site works on desktop browsers and fails on iOS.
• Meet Apple’s certificate requirements. The hostname must appear in the Subject Alternative Name extension, the signature must use a SHA-2 family algorithm, and RSA keys must be 2048 bits or larger. Connections that violate these fail outright in Safari.
• Automate renewal. With the maximum lifetime already down to 200 days and heading to 47 by 2029, manual renewals are the wrong approach. Tools built on ACME certificate automation request, install, and renew certificates before they lapse.

If the certificate has already lapsed, you will need to install a valid certificate on the server before mobile visitors can reach the site again.

Frequently Asked Questions

For more SSL error troubleshooting, check our detailed tutorials about fixing different SSL errors, including the SSL connection error on Android.