What an Android certificate error means
If you are trying to open a website, sign in to an app, or connect to Wi‑Fi and Android shows a certificate error, the device is warning that it cannot verify trust.
This usually points to a problem with time settings, network interception, outdated software, or a server-side certificate issue.
Understanding the source matters because the right fix depends on whether the error appears in Chrome, a banking app, Gmail, or a captive portal on public Wi‑Fi.
The steps below cover the most common causes and the safest ways to resolve them.
Why certificate errors happen on Android
Android uses a certificate chain to confirm that a website or app server is legitimate.
When that chain cannot be validated, the device may block the connection or display a security warning.
- Incorrect date and time on the phone
- Expired or invalid server certificate
- Outdated Android system components such as Android System WebView, Chrome, or Play Services
- Custom DNS, VPN, or proxy interfering with secure connections
- Captive portals on hotel, airport, or office Wi‑Fi
- Cached app data causing old security state to persist
- Rooted devices or user-installed certificates that change trust behavior
Check the date and time first
One of the most common causes of an Android certificate error is a clock mismatch.
Certificates have strict validity windows, so if your phone time is wrong, Android can treat a valid certificate as expired or not yet valid.
How to fix it?
- Open Settings.
- Tap Date & time.
- Enable Use network-provided time and Use network-provided time zone.
- If automatic time is already on, toggle it off and back on.
- Restart the phone and try again.
This fix is simple, but it solves a large share of browser and app certificate warnings on Android.
Update Android, Chrome, and WebView
Security validation depends on system trust stores and browser components.
If Android System WebView, Google Chrome, or the operating system is outdated, certificate handling can fail even when the site itself is fine.
- Go to Settings > System > System update and install available updates.
- Open the Google Play Store and update Chrome, Android System WebView, and Google Play services.
- Restart the device after updating.
On many Android devices, in-app web pages rely on WebView, so a WebView update can fix errors that do not appear in Chrome itself.
Test a different network
If the certificate error appears only on one Wi‑Fi network, the problem may be with that network rather than your phone.
Some public or enterprise networks intercept traffic, use login portals, or block secure connections until authentication is complete.
What to try
- Switch from Wi‑Fi to mobile data.
- Connect to another trusted Wi‑Fi network.
- Forget the current network and reconnect.
- Open a non-HTTPS page, such as a captive portal detection page, to trigger the login screen if required.
If the error disappears on a different network, your Android device is likely working correctly and the original network may need administrator attention.
Clear browser and app cache
Corrupted cache can cause an app or browser to reuse stale connection data.
Clearing cached files forces Android to rebuild the connection state and may remove the certificate warning.
For Chrome
- Open Settings > Apps > Chrome.
- Tap Storage & cache.
- Select Clear cache.
For an affected app
- Open Settings > Apps.
- Select the app showing the error.
- Tap Storage & cache.
- Choose Clear cache first, then test again.
If clearing cache does not help, you can try Clear storage or reinstall the app, but be aware this may remove sign-in data and local settings.
Turn off VPN, proxy, or custom DNS temporarily
A VPN, proxy, private DNS service, or security app can interfere with certificate checks by rerouting traffic or filtering encrypted connections.
This is especially common with corporate VPNs, ad blockers, and parental control tools.
- Disable the VPN and test the site again.
- Remove manual proxy settings from the Wi‑Fi network.
- Set Private DNS to Off or Automatic under network settings.
- Temporarily pause security or filtering apps if they inspect HTTPS traffic.
If the problem stops after disabling one of these features, re-enable them one at a time to identify the exact cause.
Check whether the site’s certificate is actually broken
Sometimes the issue is not on your Android device at all.
If a website has an expired certificate, a mismatched domain name, or an incomplete certificate chain, every visitor may see a warning.
Signs that the issue is server-side include:
- The same error appears on other phones, computers, and browsers.
- The problem affects only one website or service.
- The certificate warning mentions the site name, issuer, or expiration date.
In that case, there is little to fix on the device beyond confirming your clock and network are correct.
The website owner, hosting provider, or IT team must renew or replace the certificate.
Remove suspicious user-installed certificates
Android allows some certificates to be installed manually for work, school, VPN, or security purposes.
A bad, outdated, or unwanted user certificate can create trust conflicts, especially on rooted or heavily managed devices.
How to review installed certificates
- Open Settings.
- Search for Encryption & credentials or Security.
- Check Trusted credentials and User credentials.
- Remove certificates you do not recognize, but only if you are sure they are not required for work or school access.
If the device is managed by an employer or school, contact IT before changing any credential settings.
Refresh Google services and sign-in state
Some certificate and sign-in failures are tied to Google Play services, account sync, or authentication tokens.
A stale account session can make secure apps fail unexpectedly.
- Restart the device after updates.
- Open Settings > Accounts and verify your Google account sync is active.
- Remove and re-add the account only if other steps fail and you are comfortable reconfiguring sync and app permissions.
For apps that rely heavily on Google identity or Firebase authentication, this can resolve errors that appear to be certificate-related but are actually sign-in trust failures.
When to reset network settings
If you have changed VPNs, proxies, DNS, or Wi‑Fi profiles multiple times and the error persists, resetting network settings can clear hidden misconfigurations.
Before you reset
- Save Wi‑Fi passwords.
- Record VPN profiles and custom DNS settings.
- Note any work or school network requirements.
Then go to Settings > System > Reset options and choose Reset Wi‑Fi, mobile & Bluetooth.
Afterward, reconnect to Wi‑Fi and retest the site or app.
How to avoid certificate errors in the future
Preventing Android certificate problems is mostly about keeping trust-related components current and avoiding unnecessary network interception.
- Keep Android and apps updated.
- Leave automatic date and time enabled.
- Use reputable VPN and DNS services.
- Avoid installing unknown root certificates.
- Check public Wi‑Fi login portals before opening secure sites.
- Contact site owners when a certificate warning appears on only one domain.
If you regularly manage sensitive accounts such as banking, email, or enterprise apps, these habits reduce the chance of repeated certificate interruptions and improve connection reliability across Android.