CristDBLab

Programming

ChromeThe website uses HSTS Network errorsthis page will probably work later

19 September 2026 · 10 min read

ChromeThe website uses HSTS Network errorsthis page will probably work later

Encountering the dreaded “Chrome: The website uses HSTS. Network errors…this page will probably work later” message can be frustrating. This error signifies that your Chrome browser is having trouble connecting to a website that uses HTTP Strict Transport Security (HSTS). HSTS is a security mechanism that forces browsers to connect to a website using only HTTPS, ensuring that all communications are encrypted and secure. While designed to protect you, misconfigurations or temporary network issues can trigger this error, leaving you unable to access the desired site. Understanding the root causes and available solutions can quickly restore your browsing experience and prevent future occurrences. We’ll explore the common culprits behind this error and provide practical steps to resolve it, allowing you to get back online with confidence.

Understanding HSTS and Its Implications

HTTP Strict Transport Security (HSTS) is a web security policy mechanism designed to protect websites against man-in-the-middle attacks, such as protocol downgrade attacks and cookie hijacking. When a website declares an HSTS policy, it instructs browsers to only connect to it using HTTPS, preventing them from using insecure HTTP connections. This is crucial for maintaining data integrity and confidentiality. HSTS policies are communicated through an HTTP response header, which specifies the duration for which the browser should remember to only use HTTPS. If a browser encounters an HTTP connection to a site with an active HSTS policy, it will automatically upgrade the connection to HTTPS, if possible. The “Chrome: The website uses HSTS. Network errors…this page will probably work later” error occurs when Chrome detects a potential conflict between a site’s HSTS policy and a network issue preventing a secure connection.

HSTS plays a vital role in modern web security. By enforcing HTTPS, it eliminates the risk of attackers intercepting sensitive data transmitted over unencrypted HTTP connections. This is especially important for websites that handle personal information, financial transactions, or other confidential data. However, HSTS can also present challenges. If a website’s HSTS policy is misconfigured or if there are temporary network issues, users may encounter errors that prevent them from accessing the site. Therefore, it’s essential to understand how HSTS works and how to troubleshoot related issues. According to Google’s Security Blog, “HSTS is a critical component of a secure web, and its widespread adoption has significantly reduced the attack surface for many websites.” [1]

One potential issue is the “max-age” directive in the HSTS header. This directive specifies how long the browser should remember to connect to the site using HTTPS. If the max-age is set to a very long duration, and the website later experiences issues with its SSL/TLS certificate or HTTPS configuration, users may be unable to access the site until the max-age expires. This highlights the importance of carefully configuring HSTS policies and ensuring that SSL/TLS certificates are properly maintained. This is why understanding the Chrome: The website uses HSTS. Network errors…this page will probably work later error is important for web developers and users alike.

Common Causes of the “Chrome: The website uses HSTS” Error

Several factors can contribute to the “Chrome: The website uses HSTS. Network errors…this page will probably work later” error in Chrome. One of the most common is a temporary network connectivity issue. If your internet connection is unstable or experiencing interruptions, Chrome may be unable to establish a secure HTTPS connection to the website, triggering the error. Another potential cause is a problem with the website’s SSL/TLS certificate. If the certificate is expired, invalid, or not properly configured, Chrome will refuse to connect to the site to protect your security.

Browser cache and cookies can also play a role. If your browser has cached outdated or corrupted data related to the website’s HSTS policy, it may interfere with the connection process. Clearing your browser’s cache and cookies can often resolve this issue. Additionally, conflicts with browser extensions or third-party security software can sometimes trigger the error. These extensions might interfere with the secure connection or modify the HSTS policy, leading to the error message. Finally, in rare cases, the error might stem from a misconfiguration on the website’s server itself, particularly related to its HSTS policy settings. According to Mozilla’s documentation on HSTS, “Incorrectly configured HSTS policies can lead to accessibility issues for users.” [2]

Here’s a featured snippet-optimized paragraph: The “Chrome: The website uses HSTS. Network errors…this page will probably work later” error typically arises from network connectivity issues, SSL/TLS certificate problems, outdated browser cache, or conflicts with browser extensions. Addressing these potential causes can often resolve the error and restore access to the website. Troubleshooting steps include checking your internet connection, clearing your browser’s cache and cookies, disabling browser extensions, and verifying the website’s SSL/TLS certificate.

Troubleshooting Steps to Resolve the Error

When faced with the “Chrome: The website uses HSTS. Network errors…this page will probably work later” error, a systematic approach to troubleshooting is essential. Start by verifying your internet connection. Ensure that you have a stable and active internet connection. Try accessing other websites to confirm that the issue is specific to the website displaying the error. If your internet connection appears to be working correctly, proceed to the next step. Clearing your browser’s cache and cookies is often an effective solution. Cached data can sometimes interfere with the secure connection process, so clearing it can resolve the error.

Next, disable any browser extensions that might be interfering with the connection. Some extensions can modify HSTS policies or interfere with SSL/TLS certificates, leading to the error. Disable extensions one by one to identify if any particular extension is causing the problem. You can also try using Chrome’s incognito mode, which disables all extensions by default, to see if the error persists. If the error disappears in incognito mode, it’s likely that an extension is the culprit. If the problem persists, consider checking the website’s SSL/TLS certificate. You can use online SSL checker tools to verify if the certificate is valid, properly configured, and not expired. Incorrect SSL configurations can be a major cause of HSTS issues.

Here’s an ordered list of troubleshooting steps:

  1. Check your internet connection.
  2. Clear your browser’s cache and cookies.
  3. Disable browser extensions.
  4. Verify the website’s SSL/TLS certificate.
  5. Try accessing the website using a different browser.

Advanced Solutions and Prevention

If the basic troubleshooting steps fail to resolve the “Chrome: The website uses HSTS. Network errors…this page will probably work later” error, more advanced solutions may be necessary. One option is to clear Chrome’s HSTS settings. This will remove any stored HSTS policies for the website, allowing Chrome to attempt a new connection without being restricted by the previous policy. To do this, you can visit chrome://net-internals/hsts in your Chrome browser and delete the domain’s HSTS settings.

Another approach is to temporarily disable HSTS in Chrome. However, this should only be done as a last resort, as it weakens your browser’s security. To disable HSTS, you can use command-line switches when launching Chrome. For example, you can add the –ignore-certificate-errors flag. However, be aware that this will disable certificate validation, making your browser vulnerable to man-in-the-middle attacks. For website owners, ensuring proper HSTS configuration is crucial. This includes setting an appropriate max-age value, including the includeSubDomains directive, and considering the preload directive to have your site included in Chrome’s HSTS preload list. Proper HSTS configuration enhances website security and prevents users from encountering errors. You can learn more about HSTS preloading on the HSTS Preload List website. [3] As an expert, I can tell you that proper HSTS configuration minimizes user friction.

Here are some additional points to consider:

  • Regularly update your browser to the latest version.
  • Use a reliable and secure DNS server.
  • Monitor your website’s SSL/TLS certificate for any issues.
Infographic here
FAQ: Chrome HSTS Errors -----------------------
What does "Chrome: The website uses HSTS. Network errors...this page will probably work later" mean?
This error indicates that Chrome is trying to connect to a website using HTTPS due to its HSTS policy, but is encountering network issues preventing a secure connection.
How do I fix the "Chrome: The website uses HSTS" error?
Try checking your internet connection, clearing your browser's cache and cookies, disabling browser extensions, and verifying the website's SSL/TLS certificate. See other steps listed above in this article.
Is it safe to disable HSTS in Chrome?
Disabling HSTS weakens your browser's security and should only be done as a last resort for troubleshooting purposes. Make sure to re-enable HSTS when finished.
Can a website owner fix this issue?
Yes, by ensuring proper HSTS configuration, including setting an appropriate max-age value, including the includeSubDomains directive, and considering HSTS preloading.
- Always prioritize secure connections (HTTPS). - Regularly check your website's SSL/TLS certificate.

Addressing the “Chrome: The website uses HSTS. Network errors…this page will probably work later” error requires a methodical approach, ranging from basic troubleshooting to more advanced solutions. By understanding the underlying causes and following the steps outlined above, you can effectively resolve the error and ensure a secure and seamless browsing experience. Remember, HSTS is designed to protect your data, so disabling it should only be a temporary measure. Regularly updating your browser and maintaining a secure network environment are essential for preventing future occurrences. For more information on web security and browser configurations, consider exploring resources from reputable sources like OWASP. If you’re interested in learning more about web security best practices and how they can affect your browsing experience, consider exploring related topics.

1 Google Security Blog: https://security.googleblog.com/ 2 Mozilla HSTS Documentation: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security 3 HSTS Preload List: https://hstspreload.org/

Question & Answer :
I am developing against localhost. This morning right after I used fiddler I started getting this error on chrome (works correctly in firefox)

“You cannot visit localhost right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.” enter image description here

Now localhost works in chrome only if fiddler is running. I already made sure the proxy redirects that fiddler makes are corrected when fiddler shuts down.

I also tried importing the certificate to my trusted root and restarting the browser (and also the machine).

One very quick way around this is, when you’re viewing the “Your connection is not private” screen:

type badidea

type thisisunsafe (credit to The Java Guy for finding the new passphrase)

That will allow the security exception when Chrome is otherwise not allowing the exception to be set via clickthrough, e.g. for this HSTS case.

This is only recommended for local connections and local-network virtual machines, obviously, but it has the advantage of working for VMs being used for development (e.g. on port-forwarded local connections) and not just direct localhost connections.

Note: the Chrome developers have changed this passphrase in the past, and may do so again. If badidea ceases to work, please leave a note here if you learn the new passphrase. I’ll try to do the same.

Edit: as of 30 Jan 2018 this passphrase appears to no longer work.

If I can hunt down a new one I’ll post it here. In the meantime I’m going to take the time to set up a self-signed certificate using the method outlined in this stackoverflow post:

How to create a self-signed certificate with openssl?

Edit: as of 1 Mar 2018 and Chrome Version 64.0.3282.186 this passphrase works again for HSTS-related blocks on .dev sites.

Edit: as of 9 Mar 2018 and Chrome Version 65.0.3325.146 the badidea passphrase no longer works.

Edit 2: the trouble with self-signed certificates seems to be that, with security standards tightening across the board these days, they cause their own errors to be thrown (nginx, for example, refuses to load an SSL/TLS cert that includes a self-signed cert in the chain of authority, by default).

The solution I’m going with now is to swap out the top-level domain on all my .app and .dev development sites with .test or .localhost. Chrome and Safari will no longer accept insecure connections to standard top-level domains (including .app).

The current list of standard top-level domains can be found in this Wikipedia article, including special-use domains:

Wikipedia: List of Internet Top Level Domains: Special Use Domains

These top-level domains seem to be exempt from the new https-only restrictions:

  • .local
  • .localhost
  • .test
  • (any custom/non-standard top-level domain)

See the answer and link from codinghands to the original question for more information:

answer from codinghands