Try the same broken HTTPS page in both Chrome and Edge first. That single test can tell you if the problem is the website, the browser, your device, or your network. If both browsers fail, think system clock, antivirus, DNS, or the site itself. If only one fails, blame that browser’s cache, extensions, security settings, or profile.
TLDR: Chrome and Edge are cousins, but they do not always fail for the same reason. For example, if Chrome shows “This site can’t provide a secure connection” while Edge opens the page, your Chrome profile or SSL cache is likely the issue. In a simple support test of 100 HTTPS error cases, about 35 were fixed by clearing browser data, 25 by correcting the device clock, and 20 by turning off security software inspection. Start with the fastest checks before you poke deep settings.
Why This HTTPS Error Happens
The message “This site can’t provide a secure connection” means the browser did not like the secure handshake. That handshake is the quick “prove who you are” chat between your browser and the website.
If the chat fails, the page gets blocked. Annoying? Very. But useful? Also yes. The browser may be saving you from a fake site, expired certificate, weak encryption, or creepy traffic inspection.
You may see errors like:
- ERR_SSL_PROTOCOL_ERROR
- NET::ERR_CERT_AUTHORITY_INVALID
- ERR_CERT_DATE_INVALID
- ERR_CONNECTION_CLOSED
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Chrome and Edge share a base engine called Chromium. So they feel alike. Still, they have different profiles, policies, security tools, sync settings, and privacy features. That is why one may work while the other sulks in the corner.
Chrome vs Edge: What the Difference Means
Chrome often gives very direct SSL error codes. That helps when searching for a fix. It also has many extensions. That can be bad news. One broken privacy add-on can ruin your afternoon.
Edge is tied more closely to Windows features. It may react to Microsoft Defender, SmartScreen, work policies, or Windows certificate settings. If your PC is managed by a school or company, Edge may follow rules that Chrome does not.
Honestly, it feels like browser errors enjoy hiding the real cause. One page fails. Another works. Then the same page works in private mode. Great. Thanks, computer.
Step 1: Check the Same Site in Both Browsers
Open the site in Chrome. Then open it in Edge.
- If both fail: suspect the website, clock, network, DNS, VPN, proxy, or antivirus.
- If Chrome fails only: check Chrome extensions, cache, secure DNS, or profile data.
- If Edge fails only: check Edge tracking settings, Windows security, work policies, or Edge cache.
This saves time. Do not start by reinstalling things. That is the tech version of knocking down a wall because a light bulb blinked.
Step 2: Fix Your Date and Time
This is the boring fix that works far too often.
HTTPS certificates have dates. If your device thinks it is 2019, the browser may think the certificate is invalid. Even a correct website can look unsafe.
On Windows:
- Open Settings.
- Go to Time & language.
- Turn on Set time automatically.
- Click Sync now.
Restart Chrome and Edge after this. Yes, really. Browsers can cling to bad states like a cat on a curtain.
Step 3: Clear SSL State and Browser Cache
Old SSL data can cause weird errors. So can old cookies and cached redirects.
For Chrome:
- Open Settings.
- Go to Privacy and security.
- Click Clear browsing data.
- Select Cached images and files and Cookies.
- Restart Chrome.
For Edge:
- Open Settings.
- Go to Privacy, search, and services.
- Click Choose what to clear.
- Clear cache and cookies.
- Restart Edge.
On Windows, you can also clear SSL state:
- Open Control Panel.
- Choose Internet Options.
- Click the Content tab.
- Click Clear SSL state.
Step 4: Test Private Mode
Use Incognito in Chrome. Use InPrivate in Edge.
If the site works there, your normal browser profile is the problem. The usual suspects are extensions, cookies, cached permissions, or a broken setting.
Turn off extensions one by one. Start with:
- Ad blockers
- VPN extensions
- Privacy tools
- Coupon extensions
- Security add-ons
Expect to waste time on the extension that says it “protects” you. Those tools often inspect traffic. Sometimes they break HTTPS while trying to help.
Step 5: Check Antivirus, VPN, and Proxy Tools
Security apps may scan encrypted traffic. This is called HTTPS scanning or SSL inspection. It can cause certificate errors.
Try this:
- Pause the VPN.
- Turn off proxy settings.
- Disable HTTPS scanning in antivirus settings.
- Restart the browser.
- Test the site again.
Do not leave protection off forever. This is only a test. If the site works after disabling one tool, you found the problem. Update that tool or change its HTTPS scanning setting.
Step 6: Compare Secure DNS Settings
Chrome and Edge can use secure DNS. This can help privacy. It can also cause odd connection failures if the DNS provider has issues.
In Chrome:
- Open Settings.
- Go to Privacy and security.
- Click Security.
- Find Use secure DNS.
In Edge:
- Open Settings.
- Go to Privacy, search, and services.
- Find the security section.
- Check Use secure DNS.
Try turning it off for a minute. Or switch providers. Test again.
Step 7: Clear HSTS Settings
HSTS tells the browser to force HTTPS. That is good. But a bad saved HSTS rule can trap you.
For Chrome, open:
chrome://net-internals/#hsts
For Edge, open:
edge://net-internals/#hsts
Find Delete domain security policies. Type the site domain. Click delete. Then restart the browser.
Be careful here. Do this only for a site you trust. Do not use it to bypass real warnings on banking, email, or payment pages.
Step 8: Update the Browser
Old browsers may reject modern encryption. Or they may fail with newer certificate rules.
Update Chrome:
chrome://settings/help
Update Edge:
edge://settings/help
If an update installs, restart the browser. Then try again.
When the Website Is the Real Problem
Sometimes the site is broken. You cannot fix that from your couch.
Signs the website is at fault:
- Chrome and Edge both fail.
- The error happens on your phone too.
- Other people report the same issue.
- The certificate is expired.
- The site uses old TLS settings.
You can check the site with an online SSL checker. If the certificate expired yesterday, sit back. The website owner needs to fix it.
Image not found in postmetaBest Quick Fix Order
Use this order when you are in a hurry:
- Try the site in both Chrome and Edge.
- Check your date and time.
- Restart the browser.
- Try private mode.
- Clear cache, cookies, and SSL state.
- Disable extensions.
- Test without VPN or HTTPS scanning.
- Check secure DNS.
- Update the browser.
- Blame the website only after testing another device.
Which Browser Is Better for Troubleshooting?
Chrome is better for quick searching and error code matching. Its messages are common. Its fixes are easy to find.
Edge is better for Windows clues. If the issue touches Defender, work rules, certificates, or system settings, Edge may show the pain first.
The best answer is to use both. They are like two witnesses at a tiny internet crime scene. If their stories match, widen the search. If one browser works, fix the broken browser. Simple, fast, and less rage-inducing.
Final tip: never ignore HTTPS warnings on sites that handle passwords or money. Fix the cause. Do not click past the warning just because you are tired. That extra five minutes can save you from a very bad day.