Why am I unable to bypass HSTS and pinning certificate errors such as "Your connection is not private" or "Cannot connect to the real domain.com" by adding a certificate exception?

Overview:  

Your Connection is Untrusted/Not Private - *.opendns.com or *.cisco.com Certificate Error that cannot be bypassed

Note: A solution for this problem that is easier to manage and persistent for all sites is now available.

As a result, the information below is still applicable but can now be worked around with a permanent solution. Try installing the Cisco Root CA via the Cisco Umbrella documentation: Manage the Cisco Umbrella Root Certificate

This article is a guide for when a certificate error for *.opendns.com or *.cisco.com appears but cannot be bypassed by adding a certificate exception as outlined in the Cisco Umbrella documentation Manage the Cisco Umbrella Root Certificate. In this case, follow the steps below to allow the certificate error to be cleared. 

When you can't bypass the certificate error by adding an exception, this is because of the implementation of HTTP Strict Transport Security (HSTS) or pre-loaded Certificate Pinning in modern browsers.  Communication between certain browsers and certain websites is done in a way that includes the requirement to use HTTPS and no bypass or exception is possible. This extra security for HTTPS pages prevents the Umbrella block page and bypass block page mechanism from working when HSTS is active for a website.

As a result, the page in question cannot be accessed through Block Page Bypass (BPB) (in fact, the Bypass screen may not even appear). The methods below may allow access to the BPB login, but after the login, the certificate error will reappear and deny access. Review the rest of this article if you're seeing a certificate error in Google Chrome, Mozilla Firefox, Safari that cannot be bypassed and you are trying to access the bypass login.

IMPORTANT: If the domain is on the HSTS pinned list, an exception cannot be added since the list is effectively non-bypassable if you're running Chrome, Safari, or Firefox (Internet Exporer (IE) is not affected). Block Page Bypass will not work for sites like this. For a complete list of services using HSTS by these three browsers, please review the Google Chromium Code Search. Notable services in this list include:

• Google (and Google resources, such as Gmail, Youtube, or Google Docs)
• Dropbox
• Twitter
• Facebook

Possible Solutions

There are a few ways to resolve these issues.  First, the following sections will demonstrate how to use more granular policies to work around this issue.  Second, you can use browser configurations, but these are isolated to a subset of the browsers affected by this issue.

Policy management and the roaming client

Note: Cisco announced the End-of-Life for Umbrella Roaming Client on April 2, 2024. Last Date of Support for Umbrella Roaming Client will be April 2, 2025. All Umbrella Roaming Client functionality is currently available in Cisco Secure Client. Cisco will be providing future innovations in Cisco Secure Client only. We recommend that customers begin planning and scheduling their migration now. Please refer to this KB article for guidance on how to migrate from the Umbrella Roaming Client to Cisco Secure Client.

Proper policy management is the best solution to this problem because the browser will not receive a failed validation response in the first place. If some of your users should be permitted to access sites that they would normally need to use Block Page Bypass to access, you should instead configure a separate policy for these users and add the domains that they should be allowed to use to the Allow List. Since the users' requests are never blocked, the browser will never receive a request from a domain with a mismatched certificate. You can use the Umbrella Roaming Client to deliver these specific policies. This means that you are putting certain domains in an allow list for certain users at all times of the day to work around these errors.

Note: The Umbrella roaming client is an effective way to distribute particular policies to multiple users, but if you have enabled Active Directory(AD) integration, you can apply these permitted policies to particular AD users as well.

There can be issues with your network configuration or acceptable usage (HR) policy that prevents this solution. Policy management is not an effective solution if users are allowed to visit these domains only at given times (such as during their lunch break). Umbrella cannot provide a time-based policy application with our service, so simply allowing a user to access the site all the time could be problematic.  On a shared computer, such as a public terminal, the Umbrella roaming client can't differentiate between users and cannot easily allow the right domains for the right people.

Policy management is not as effective when considering non-granular identities, such as Sites or Networks, unless the administrator is comfortable giving all users of that network the same access.  Policy management works best when applied to a subset of users that should be allowed to access sites while the rest of the network cannot, and singling out those users by installing the roaming client on their machines and applying the proper policy hierarchy.