Warning "The connection is not secure"** (or NET::ERR_CERT_INVALID v Google Chrome) is one of the most common problems among users Android. It appears when you try to open a website with an expired, self-signed or untrusted SSL certificate, as well as when connecting to unsecured networks Wi-Fi. In most cases, blocking is justified: this is how the system protects you from phishing, MITM attacks or data leaks. However, sometimes the warning appears erroneously - for example, on corporate resources, local devices or test pages.

In this article we will look at all ways to disable the warning on smartphones Samsung, Xiaomi, Huawei and other brands running on Android 10–14. Important: ignoring SSL errors can lead to interception of logins, banking data or infection with malware. Therefore, we will not only show how to bypass the blocking, but also explain in which cases it is safe and in which it is strictly not recommended.

If you encounter a problem on a specific site (for example 192.168.1.1 for a router or an internal company resource), first check whether the warning is related to the system time settings or antivirus. Often the error disappears after synchronizing the date/time or turning off the VPN.

📊 Where do you most often see the "Connection is not secure" error?
When logging into the router (192.168.x.x)
On work/school sites
In public Wi-Fi (cafes, airports)
On random sites on the Internet
Another option

1. Why does the “Connection is not secure” error appear?

A warning with a code ERR_CERT_AUTHORITY_INVALID, ERR_CERT_DATE_INVALID or NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM means that the browser or system Android does not trust the site’s SSL certificate. The reasons can be divided into 3 groups:

  • 🔴 Problems on the site side:
    • Expired certificate (expired).
    • Self-signed certificate (often used on local devices, for example 192.168.0.1 for a router).
    • The certificate was issued by an unreliable center (CA).
    • Inconsistency between the domain in the certificate and the website address.
  • 📱 Problems on the device side:
    • Incorrect date/time (for example, after resetting the settings).
    • Lack of root certificates CA in the system.
    • Blocking by antivirus or VPN (for example, Kaspersky, Avast).
  • 🛡️ Active attacks:
    • MITM attack (traffic interception through public Wi-Fi).
    • Phishing site with a fake certificate.

Most users encounter an error when trying to log into the router control panel (192.168.1.1 or 192.168.0.1), corporate portals or developer test pages. In these cases, disabling the warning is usually safe. If the error appears on popular sites. (for example, VKontakte, Google), this is a reason to check your device for viruses.

💡

Before disabling protection, try opening the site in another browser (for example, Firefox or EdgeIf there is no error, there is a problem). settings Chrome or system certificates.

2. Method 1: Skip the warning in the browser (Chrome, Edge, Firefox)

The fastest but temporary way is to manually allow access to the site directly in the browser. This method is suitable if you Completely trust the resource (for example, this. your home router or work portal).Instructions for different browsers:

In Google Chrome (and based on Chromium: Edge, Opera, Yandex)

  1. Open the site where the error appears.
  2. Click "Advanced"** (or Advanced in the English version).
  3. Select "Go to site {name} (not safe)" (or Proceed to {site} (unsafe)).

In Mozilla Firefox

  1. Click "Advanced" → "Add exception".
  2. Confirm adding a temporary exception.

⚠️ Attention: This method works only for the current session. After restarting the browser or device, the warning will appear again. In addition, Chrome may block some functions of the site (for example, authorization or payment) even after missing an error.

☑️ Check before skipping. warnings

Done: 0 / 4

3. Method 2: Adding a certificate to the trusted ones (for routers and local sites)

If an error appears when logging in to 192.168.1.1, 192.168.0.1 or another local resource (for example, NAS server or IP camera), the best solution is install the device certificate in the trusted store. This will solve the problem one-time for all browsers and applications.

Instructions for Android 10–14:

  1. Download the certificate from the device (usually it is available via a link like http://192.168.1.1/cert.der or https://[address]/download/cert).
  2. Open Settings → Security → Advanced → Encryption and credentials → Install certificate.
  3. Select "Install from storage"** and specify the downloaded file (format .cer, .der or .pem).
  4. Set the certificate name (for example, “Router”) and confirm the installation.

After rebooting the device, the error “The connection is not secure”** will disappear. This method works for most. models Samsung Galaxy, Xiaomi Redmi/POCO, Huawei and others.

How to download a certificate from the router?

1. Connect to the router’s network via Wi-Fi or cable.

2. Open in the browser 192.168.1.1 (or another IP of your router).

3. Find the “Certificate” or “Security” section (it may be called differently). Keenetic, TP-Link, ASUS it may be called differently).

4. certificate to a file and save it to your phone.

Device/Brand Path to install the certificate Features
Samsung (One UI) Settings → Biometrics and security → Other security settings → Install certificate Requires a PIN or password
Xiaomi (MIUI) Settings → Passwords and security → Privacy → Install certificate You may need to disable “MIUI Protection”
Huawei (EMUI) Settings → Security → Encryption and credentials → Install from storage Supports only certificates in the format .cer
Google Pixel (Stock Android) Settings → Security → Advanced → Encryption and credentials The most universal option

4. Method 3: Changing the date and time (if the certificate is expired)

If the error is related to an expired certificate (code ERR_CERT_DATE_INVALID), a temporary solution may be changing the date to. deviceThis will work if:

  • 📅 The certificate was valid in the past (for example, it expired a month ago).
  • 🔄 You need to access the resource once (for example, download files from an old site).

Instructions:

  1. Open Settings → System → Date and time.
  2. Disable the option "Automatic date and time"**.
  3. Set the date within the validity of the certificate (for example, if it expired on May 1, 2026, set to April 1, 2026).
  4. Restart the browser and try to open the site.

⚠️ Attention: This method may disrupt the operation of other applications (for example WhatsApp, Telegram or banking services) that are tied to the exact time. After completing the work, return automatic. synchronization!

💡

Changing the date is a temporary solution. For permanent access to a site with an expired certificate, it is better to add it to exceptions or update the certificate on the resource side.

5. Method 4: Disabling SSL verification in applications (for developers)

If the error "The connection is not secure"** appears in a mobile application (for example, when testing an API or connecting to a local server), you can disable SSL verification at the code level. This method is only suitable for developers or users with root access.

For Android applications on Java/Kotlin add the following class to the code (example for OkHttp):

val client = OkHttpClient.Builder()

.sslSocketFactory(


TrustAllCertificates.createSSLSocketFactory(),


TrustAllCertificates.trustAllManager


)


.hostnameVerifier { _, _ -> true }


.build()

For WebView (if there is an error in the mini-browser inside the application):

webView.setWebViewClient(object : WebViewClient() {

override fun onReceivedSslError(


view: WebView?,


handler: SslErrorHandler,


error: SslError


) {


handler.proceed() // Ignore the error SSL


}


})

⚠️ Attention: Disabling SSL verification in an application makes it vulnerable to attacks. Use this method For testing purposes only in a controlled environment (such as an emulator or test device).

💡

To test APIs with self-signed certificates, use tools like Postman or Charles Proxy —they allow you to temporarily disable SSL verification without changing the code.

6. Method 5: Using alternative browsers (to bypass blocking)

Some browsers (for example, Kiwi Browser, Brave or Firefox Nightly) offer advanced security settings that allow you to bypass SSL errors. Consider two options:

Option 1: Kiwi Browser (Chromium-based with extensions)

  1. Install Kiwi Browser from Google Play.
  2. Open the site with an error.
  3. Click on the 🔒 icon in the address bar → "Site settings" → "Unsafe content" → "Allow"**.

Option 2: Firefox with manually adding an exception

  1. Open the problematic site in Firefox.
  2. Click "Advanced" → "Add exception".
  3. Confirm adding a permanent exception for the domain.

The advantage of this method is no need to change system settings or installing certificates, however, some site functions (for example, authorization via OAuth) may work. incorrect.

7. Risks of disabling SSL protection: when is it dangerous?

Ignoring the warning "Connection not possible" protected"** can lead to:

  • 🕵️ Traffic interception: Attackers on the same network Wi-Fi will be able to read your logins, passwords or banking data.
  • 🎣 Phishing: Fraudsters can spoof the site (for example, instead of vk.com show vk-secure.ru).
  • 💻 Installation of malware: On unprotected sites there is a higher risk of downloading a virus instead of the desired file.
  • 🔄 Data loss: Some services (for example, Google Drive) block downloading files over an unsecured connection.

⚠️ Attention: Never disable SSL verification on the following types of sites:

  • 🏦 Banking services (SberBank Online, Tinkoff, VTB).
  • 🛒 Payment systems (PayPal, WebMoney, crypto exchanges).
  • 🔑 Postal services (Gmail, Mail.ru, Yandex Mail).
  • 🆔 Social networks (VKontakte, Facebook, Telegram Web).
  • 🏥 Medical portals (for example, Public Services Health).

If an error appears on such resources, do not skip it better check your device for viruses or contact site support.

8. Frequently asked questions (FAQ)

❓ Why does the error appear only on the phone, but on the computer the site opens normally?

This may be due to:

  • The lack of root certificates on Android (on Windows/macOS they are usually installed by default).
  • Blocked by an antivirus or VPN on your phone.
  • Unsynchronized time (on a PC, the time is often updated automatically).

Try updating the certificates manually or check the date/time settings.

❓ Is it possible to permanently remove this warning for a specific site?

Yes, if:

  • Add the site certificate to the trusted ones (method 2).
  • Use Firefox with a permanent exception.
  • Configure local DNS or VPN with the correct certificate.

B Chrome a permanent exception cannot be made - you will have to click every time "Advanced"**.

❓ Is it dangerous to disable SSL verification for a router (192.168.1.1)?

For local devices (router, NAS, IP camera) the risk is minimal if:

  • You are connected to them via cable or home Wi-Fi (not a public network).
  • The router has a strong administrator password.
  • You do not enter sensitive data (for example, bank passwords) on the router page.

For additional security, configure it on your router HTTPS with a self-signed certificate and add it to the trusted list on your phone.

❓ Why did the error appear again after resetting the settings?

When resetting (hard reset) the following are deleted:

  • All user certificates (including those added manually).
  • Date/time settings (synchronization may be lost).
  • Exceptions in browsers.

Restore certificates and settings again. If the error remains, check whether the antivirus is blocking the traffic or VPN.

❓ Can an antivirus cause the “Connection is not secure” error?

Yes, many antiviruses (Kaspersky, Avast, Dr.Web) scan HTTPS traffic, replacing certificates. after installing the antivirus:

  1. Open the antivirus settings.
  2. Find the section "Network protection" or "HTTPS scanning".
  3. Disable scanning of encrypted traffic.

If after this the sites open normally, the problem was in the antivirus.