日本語
STEP-BY-STEP GUIDE

Safely troubleshoot Chrome NET::ERR_CERT_DATE_INVALID

Troubleshooting guideSources checked: 2026-09-055 stepsFaultNote editorial team

What to do first

Do not bypass the certificate warning; determine whether the device clock or site is responsible.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product
Google Chrome
Versions and conditions
Chrome for computer
Error codes and identifiers
NET::ERR_CERT_DATE_INVALID

Symptoms

  • Chrome says the connection is not private
  • An HTTPS site does not open

Causes and conditions

The device date or time zone may be wrong, or the site certificate may be outside its validity period.

Before you start

  • Record the error code, URL, and time
  • Stop entering passwords or making payments

Precautions

  • Do not ignore the warning and proceed
  • Do not install an unknown root certificate

Tools and official pages used in this guide

Google Chrome troubleshooting sequence: Confirm the code; Synchronize the clock; Update Chrome; Compare sites; Contact the operator
Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

  1. 01

    Confirm the code

    #

    Use Advanced only to inspect the message; record the code and do not proceed.

    Record the Your connection is not private page and code. Even after opening Advanced, do not select any option that bypasses the warning, and do not enter credentials or payment information.

    Record the error code, certificate host, and current PC time together. Do not force the connection through Advanced; correct the Windows clock first.

    Official links for this step

  2. 02

    Synchronize the clock

    #

    Right-click the clock, select Adjust date and time, check the date, time, and time zone, and choose Sync now.

    On Windows 11, open Settings > Time & language > Date & time. Check the year, month, day, and time zone, use automatic settings and synchronization, then confirm that the correct current time appears before retrying.

  3. 03

    Update Chrome

    #

    Open ⋮ > Help > About Google Chrome, update, and retry.

    After updating, close the affected page and open the correct URL in a new tab. If the same code remains on one site after correcting the clock, the provider may need to check the certificate expiration or other site-side condition.

  4. 04

    Compare sites

    #

    Open several known HTTPS sites. If many show the error, ask the administrator to inspect the device and network.

    If many HTTPS sites are affected, corporate traffic inspection or the device certificate environment may be involved. Record whether the behavior changed after installing organization or protection software, and do not manually install an unfamiliar certificate.

  5. 05

    Contact the operator

    #

    If the clock is correct and only one site fails, give its operator the URL, code, and time and wait for correction.

    Tell the operator that the clock is synchronized correctly and include results for other sites. Until the certificate is corrected, do not submit credentials or files to that site; use another contact method published through an official channel.

Check the result

  • The device is synchronized to the correct time
  • The correct domain opens without a warning

If the problem continues

  • On a company device, do not add a certificate yourself
  • Retry after correction is complete

Scope of this guide

Troubleshooting guide — A general diagnostic and recovery procedure based on official support; it does not indicate a current specific incident.

Frequently asked questions

Can I proceed through Advanced?

No. Correct the clock or certificate at the source.

Only one site fails. What should I do?

Give the code and time to the site operator.

Official sources and dates

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

Get more from Google Chrome

← Search English guides