Fix 'Your Connection Is Not Private' in Chrome Safely
Source-checked · About 10 minutes
Answer
Do not bypass Chrome's 'Your connection is not private' warning. Read the code below it: for NET::ERR_CERT_DATE_INVALID, correct Windows at Settings > Time & language > Date & time; on public Wi-Fi, open http://example.com and complete the network sign-in; otherwise test Incognito and update Chrome and Windows. If the warning remains on the same site or a managed work device, contact the site owner or administrator before entering any private information.
Copy the hostname and code shown below the warning, such as NET::ERR_CERT_DATE_INVALID, NET::ERR_CERT_AUTHORITY_INVALID, or ERR_CERT_COMMON_NAME_INVALID. Do not select an unsafe proceed option, especially for sign-in, banking, payment, health, work, or private information.
2
Correct a date or clock error
For Your clock is behind, Your clock is ahead, or NET::ERR_CERT_DATE_INVALID, open Windows Settings > Time & language > Date & time and turn on Set time automatically and the correct time-zone setting. Return to Chrome and reload only after Windows displays the correct local date and time.
3
Complete a public Wi-Fi sign-in
If you are on hotel, airport, cafe, or other public Wi-Fi, open a new tab and visit http://example.com to trigger its sign-in portal. Complete only the network's expected sign-in, then reload the original HTTPS address and confirm the certificate warning is gone.
4
Test Chrome without extensions
Open More > New Incognito window and enter the same address. If it opens there, return to a normal window, select More > Extensions > Manage extensions, turn extensions off, and re-enable them one at a time until the warning returns.
5
Update Chrome and Windows
In Chrome, select More > Help > About Google Chrome and select Relaunch if offered; then install pending Windows updates through Settings > Windows Update. Reopen the exact hostname and check whether Chrome now shows the normal site controls instead of the privacy warning.
6
Escalate a remaining trust failure
If only one site still fails, send its owner the exact hostname, certificate code, time, and affected devices without entering private data. For NET::ERR_CERT_AUTHORITY_INVALID on a managed device that uses HTTPS inspection, contact the administrator; Google advises against installing the required certificate yourself.
Video walkthrough
If it does not work
If the warning appears only on one public network, finish its portal sign-in or use another trusted network. Do not accept a certificate merely because the network asks you to.
If Incognito fixes the warning, disable extensions through Manage extensions and restore them one at a time. Do not clear all browsing data before identifying whether an extension is responsible.
If every current device reports the warning for the same hostname, treat it as a site certificate problem and contact the owner. Local resets cannot repair the site's certificate.
If a work proxy produces NET::ERR_CERT_AUTHORITY_INVALID, provide the code to the administrator. Do not install a downloaded root certificate or turn off HTTPS protection yourself.
ⓘ Sources and verification
Checked against official documentation on . Scope: Windows.
Google documents separate branches for captive portals, Incognito and extensions, operating-system updates, managed HTTPS interception, and incorrect clocks. The warning must not be treated as a generic cache or network-speed problem.
