Chrome shows “This site can’t provide a secure connection” when it cannot establish or validate a secure HTTPS connection to a website. Check the address and your device’s date and time first, then try the steps below; if the warning appears on many sites, investigate your network or device rather than bypassing the warning.
What the error means
HTTPS uses encryption to protect information moving between your browser and a website. During the connection, the browser and server negotiate a secure connection and Chrome checks that the site’s certificate is valid for the address being visited. A failure can come from the site’s server, the connection between your device and the site, or local settings and software.
The exact wording and any accompanying code can help identify the cause. For example, a message mentioning an invalid or expired certificate points toward certificate validation, while a connection reset or protocol error may involve the server, network, or browser. The same-looking warning does not always have the same cause, so note the full message before changing settings.
Start with these safe checks
- Check the address. Make sure the domain is spelled correctly and that you followed a link to the intended site. A typo or an unfamiliar look-alike address can lead to a different server.
- Check date, time, and time zone. Set them automatically in your device’s system settings, if available, and confirm the time zone is correct. An incorrect clock can make valid security certificates appear not yet valid or expired.
- Reload, then try a new tab. A temporary network interruption can clear on a retry. Avoid repeatedly submitting passwords or payment details while the connection is failing.
- Try another website. If several unrelated HTTPS sites fail, the problem is more likely to be your device, network, or security software. If only one site fails, its server or certificate may be responsible.
- Try another network you trust. For example, compare your usual connection with a personal mobile hotspot. If the site works on one network but not another, contact the affected network’s administrator or internet provider rather than weakening browser protections.
Refresh Chrome and clear site data
Make sure Chrome is up to date. Open Chrome’s three-dot menu, choose Help, then About Google Chrome. Chrome checks for updates on that page; follow any prompt to relaunch the browser. Menu wording can vary slightly by operating system.
If the issue is limited to one site, stale cookies or cached files may contribute. In Chrome, open Settings, go to Privacy and security, and choose Delete browsing data. Select a suitable time range and the relevant data types, then confirm. Deleting cookies signs you out of many websites, so try clearing data for the affected site if Chrome offers that option, or make sure you can sign back in before removing all cookies.
You can also open the site in an Incognito window from the three-dot menu. If it works there, an extension or stored site data may be involved. Incognito mode does not make an unsafe connection safe; it is only a troubleshooting comparison.
Check extensions, VPNs, and security software
Some extensions, VPNs, proxies, or security products inspect or filter web traffic. A misconfiguration or outdated component can interfere with HTTPS. If Incognito works, review extensions at More tools > Extensions, then turn off extensions you do not need one at a time and retest. Restore any extension that is not responsible.
If you use a VPN or proxy, disconnecting briefly can help determine whether it is involved, but do so only if permitted and safe on your network. Work or school devices may require that connection. Do not disable antivirus protection, certificate checks, or other security features as a workaround. Instead, check for software updates or ask the product provider or your organization’s support team to investigate.
When the network or website is responsible
Public Wi-Fi sometimes requires a sign-in page before normal browsing works. Open a plain, non-sensitive page or follow the network’s posted sign-in instructions, and do not enter private information on a page that looks suspicious. On managed networks, filtering or a required proxy can also affect certificates; ask the administrator for help rather than installing an unknown certificate.
If one site fails on multiple devices and networks, the site owner may need to repair its HTTPS configuration, renew a certificate, or fix a server problem. Check the site’s official status channel, if it has one, or contact its support team through a separately verified route. A browser warning is not proof that a site is malicious, but it does mean Chrome could not confirm a secure connection at that time.
What not to do
Do not enter passwords, payment information, or other sensitive data after bypassing a certificate warning. Do not install certificates from pop-ups or unfamiliar sites, and do not follow instructions to disable HTTPS protections. Those actions can expose data or train your device to trust an unverified connection.
Also avoid treating every secure-connection error as a reason to reset Chrome or your network immediately. Start with reversible checks—clock, address, update, and network comparison—and make one change at a time. This helps identify the cause and makes it easier to undo a change that does not help.
Frequently Asked Questions
Why does Chrome say a site can’t provide a secure connection?
Chrome could not complete or validate the site’s HTTPS connection. The cause may be the site’s certificate or server, an incorrect device clock, a network issue, or software that interferes with the connection.
Why does the error happen on only one website?
The website may have a certificate or server configuration problem, or its stored data may be causing trouble. Compare the site on another trusted network and device. If it fails consistently, contact the site owner.
Can an incorrect date and time cause this error?
Yes. Certificate validity is checked against time, so a device clock or time zone that is substantially wrong can make a certificate appear invalid. Set the clock automatically and try again.
Is it safe to continue to the website anyway?
Not for sensitive activity. A certificate warning means Chrome cannot verify the secure connection as expected. Do not enter login, payment, or personal details unless the issue is resolved and the connection is verified.
What if the error appears on every HTTPS website?
Check the clock, update Chrome, and compare with another trusted network. If the issue remains, review managed network settings or security software with the relevant administrator or provider; do not disable certificate validation.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Schedule Work Profile Android Phones
- How to Use Microsoft Copilot on Mobile
- How to Enable ChatGPT Plugins and Use Them
- How to Print PowerPoint Slides With Notes
- Fix This App Was Blocked for Your Protection in Windows
- Windows Backup and Restore Stuck? What to Do