iOS 'Cannot Verify Server Identity' error: fix it now

You're trying to check your work email on your iPhone, or maybe you just connected to a hotel Wi-Fi and a login page pops up. Then you see it: 'Cannot Verify Server Identity' with a scary warning about a certificate. You tap Details, and nothing helps. I know this error is infuriating because it blocks you from doing something simple, like sending an email or browsing the web. It usually happens with self-signed certificates, expired certificates, or when your iOS device doesn't have the right root CA certificate installed. Let's fix it.

Why this happens

Your iPhone checks the server certificate against a list of trusted root certificates Apple ships with iOS. If the server uses a self-signed certificate, a certificate from an untrusted CA (like some corporate internal CAs), or a certificate that's expired, iOS throws this error. It's a security feature, not a bug. But it's annoying when you know the server is legit — like your company's mail server or a network login page.

Common triggers:

• Connecting to a corporate Exchange or IMAP mail server with a self-signed certificate
• Using a captive portal Wi-Fi (airports, hotels, cafes) that presents a certificate for the login page
• Accessing a site via Safari that uses an old or misconfigured SSL certificate
• Using a VPN that proxies traffic through an internal server with a non-standard cert

How to fix it

The fix depends on where the error appears. I'll walk you through each scenario. Skip the steps that don't apply.

Fix 1: Trust the certificate manually (for mail servers or VPNs)

1. When the error pops up, tap Details.
2. You'll see the certificate info. Tap Trust (if available) — but often it's grayed out.
3. If Trust isn't available, you need to install the certificate as a profile. Ask your IT admin for the server's root certificate (usually a .cer or .pem file). Email it to yourself or put it on a web server.
4. Open the attachment on your iPhone, tap Install, then go to Settings > General > About > Certificate Trust Settings.
5. Find the certificate in the list and turn on the switch next to it. This will trust it system-wide. Now try your mail again.

Note: If you're using iOS 16 or later, you might see 'Install Profile' instead of a direct trust option. Same process.

Fix 2: Bypass for captive portal Wi-Fi

If you're on a Wi-Fi login page and see this error, it's usually because the portal uses a self-signed cert. Your iPhone blocks it because it can't verify the identity. The quickest fix:

1. Tap Details on the error.
2. If you see 'Visit this website' or 'Continue' — tap it. It'll bypass the warning and load the login page anyway.
3. If that doesn't work, open Safari and type captive.apple.com. This sometimes triggers the portal properly.
4. Still stuck? Go to Settings > Wi-Fi, tap the (i) next to the network, turn off Auto-Join, then forget the network and reconnect. The portal might present a cleaner page.

Fix 3: Update or reinstall the mail account

For email, sometimes the error means the server certificate changed and your iPhone cached the old one. Here's the real fix:

1. Go to Settings > Mail > Accounts.
2. Tap the account showing the error.
3. Tap Delete Account (don't worry, your emails are on the server).
4. Re-add the account using the same settings. iOS will fetch the new certificate and prompt you to trust it if needed.
5. When it asks, tap Trust.

Fix 4: Check the date and time

Your iPhone uses the device time to validate certificate expiration. If the time is wrong, legitimate certificates appear expired.

1. Go to Settings > General > Date & Time.
2. Turn on Set Automatically.
3. If it's already on, toggle it off, wait 10 seconds, then turn it back on.
4. Try the connection again.

I've seen this trip up people flying across time zones — their phone doesn't update right away, and suddenly every secure connection fails.

What to check if it still fails

If none of the above worked, it's time to dig deeper:

• Is the certificate expired? Ask your IT team to check the server certificate's validity. If it expired, they need to renew it.
• Are you on a corporate network with a proxy? Some proxies intercept SSL and present their own cert. You'll need to install that proxy's root certificate as a profile (see Fix 1).
• Try a different network — connect via cellular or another Wi-Fi to see if the error is tied to that specific network.
• Reset network settings — this is a nuclear option but works for persistent captive portal issues. Go to Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. This clears saved Wi-Fi passwords, Bluetooth pairings, and VPN configs. Reconnect to the network and try again.

Last thing: if you're using an older iOS version (pre-15), upgrade to iOS 17 or 18. Apple tightened certificate validation in recent releases, but they also improved the error messages and trust flows. A fresh iOS update can sometimes resolve the underlying issue.

This error is one of those that looks scary but is usually fixable in minutes. Start with the simplest fix — check the date — then work up to installing a certificate profile. Your iPhone isn't broken; it's just being security-conscious. You just need to tell it to trust the right thing.