Privacy & security

Your Connection Is Not Private in Chrome? Check the Cause Safely

The short answer

Keep passwords and payment details out of the blocked page. Record the exact address and error code, check the device clock, and check whether a public Wi-Fi sign-in is waiting. On a computer, an Incognito comparison can help isolate an extension problem; it does not make an unsafe connection safe.

Related sourcesGoogle

Choose the next check from the symptom

Section link

Scroll the table sideways to see every column.

Choose the next check from the symptom
What you seeWhere to start
Clock-related errorCorrect the device date and time
Warning on public Wi-FiCheck the network sign-in portal
Works in Incognito on a computerCompare extensions in the normal window
Managed work computer is affectedAsk IT about the certificate or proxy

01Record the warning before changing settings

Section link

Check the spelling of the website address and note the error code below the warning. A certificate warning can involve the website, network, or device; it does not identify the cause by itself. A red Dangerous warning is different: Chrome has flagged that site through Safe Browsing. Do not enter private information on the warned page. For example, record whether the problem affects a work portal only or unrelated sites too. That comparison gives support a useful starting point without treating the warning as proof of a particular fault.

02Check the date and time if the error mentions the clock

Section link

If Chrome reports NET::ERR_CERT_DATE_INVALID or says the clock is ahead or behind, open the device’s date and time settings. Correct an inaccurate date, time, or time zone, then reopen the original address. Do not deliberately set an incorrect date to make a certificate appear valid. If the clock is correct and the warning remains, keep the error details and continue with the network or site check.

03Finish a public Wi-Fi sign-in separately

Section link

On hotel, cafe, or airport Wi-Fi, the network may require a sign-in before internet access. Open a separate tab and visit http://example.com to check for the network’s sign-in page, as Google suggests. Use the venue’s verified network instructions if the page is unclear. This is a way to reach the Wi-Fi portal, not a reason to replace a shopping or banking site’s HTTPS address with HTTP. After signing in, return to the original HTTPS site and check whether the warning is gone.

04On a computer, compare an Incognito window

Section link

Open the same address in an Incognito window. If it opens there, check whether an extension is involved: temporarily turn off a suspected extension and retry in the normal window. Change one thing at a time so the result is interpretable. Incognito is a comparison, not a security repair. Do not use it as a reason to enter information while a warning remains. Keep the operating system updated using its normal update controls.

05Ask the right owner if it still fails

Section link

If possible, compare another trusted connection, allowing for mobile data charges. Note whether the problem follows the website, the connection, or the computer. This is a clue, not a guaranteed diagnosis. On a managed work computer, HTTPS inspection or a missing organization certificate may need IT attention. Ask the administrator rather than installing a certificate yourself. For a persistent site-specific warning, contact the site owner with the address, error, clock check, and comparison results. Avoid disabling security protection as a routine workaround.

Sources & further reading