NET::ERR_CERT_AUTHORITY_INVALID in Chrome

• Estimated time: 5 min
• Easy
• Low risk

Scope determines whether to investigate the site or the environment shared by connections.

1. Record the exact code and try two known HTTPS sites without proceeding through warnings. Do not enter credentials or payment information on the blocked page. Note the network and device you are using.

2. If only one fails, follow the site branch. If several fail, check the portal first on public Wi-Fi; on a work or school device, contact the administrator before changing certificates or protection.

• Estimated time: 5 min
• Easy
• Low risk

A comparison narrows the problem without making unsafe access a test.

1. Check the typed address and, if another device and authorized network are available, compare the same site without bypassing warnings. A shared failure strengthens the site path; working elsewhere does not rule out network or trust differences on the first device.

2. Contact the site owner through a known channel. Do not install a certificate offered through the error page just to gain access. If other sites also start failing, switch to the multiple-site branch.

• Estimated time: 5 min
• Easy
• Low risk

A network requiring sign-in can interfere before you reach the requested site.

1. Use the network sign-in notification or ask its operator for the portal address. Do not give your email or banking password to a screen claiming to provide Wi-Fi access, or install certificates to sign in.

2. After legitimate sign-in, retry the original site. If the error remains, do not repeat login: compare an authorized trusted network and continue according to the observed scope.

• Estimated time: 10 min
• Easy
• Low risk

The comparison isolates differences rather than bypassing the warning.

1. Open the same site in Incognito. If it works there, review extensions that do not run in that mode, disabling one suspect at a time and comparing again in the normal window. Preserve managed-device restrictions.

2. If Incognito also fails, check supported system updates and recent network or security-software changes. An error limited to one network or HTTPS protection product points toward that layer’s owner; it does not justify leaving protection disabled.

3. Ask the security-software vendor about its HTTPS inspection. This guide does not require disabling antivirus to browse or independently installing trust roots.

• Estimated time: 5 min
• Easy
• Low risk

A proxy may present certificates whose trust must be deployed by the organization.

1. Tell IT the code, affected sites, and whether it changes outside the corporate network, if that comparison is authorized. Google identifies missing or incorrectly installed proxy certificates as one cause of this error.

2. Stop local modifications: the administrator needs to check the proxy and trust deployment. Do not download certificates from forums or try to bypass policies.