Error: You can't visit <Hostname> right now because the website uses HSTS when accessing vSphere client or host client

Products

• VMware vSphere ESXi

Issue/Introduction

When managing VMware infrastructure, users may encounter browser-based connectivity issues following SSL certificate updates. This article addresses errors where access to the management UI is blocked by strict browser security policies.

• Inaccessible web UI for vCenter Server or ESXi host after certificate regeneration.

• The below error message is seen when trying to access to UI client.

<HOSTNAME> uses encryption to protect your information. When Microsoft Edge tried to connect to <HOSTNAME> this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be <HOSTNAME>, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Microsoft Edge stopped the connection before any data was exchanged.

You can't visit right now because the website uses HSTS

Environment

• VMware vSphere ESXi 7.x

• VMware vSphere ESXi 8.x

• VMware vCenter Server 7.x

• VMware vCenter Server 8.x

Cause

• Browsers store HSTS (HTTP Strict Transport Security) settings for specific domains.

• When an attempt is made to connect over a broken or misconfigured HTTPS connection such as one with an expired certificate or hostname mismatch the browser strictly enforces a secure connection and blocks any attempt to bypass the error page.

Resolution

Clear the HSTS settings in the affected browser to allow a fresh connection.

For Google Chrome:

1. Enter chrome://net-internals/#hsts in the address bar.
2. Under Delete domain security policies, enter the vCenter Server or ESXi hostname in the Domain field.
3. Click the Delete button.

For Microsoft Edge:

1. Enter edge://net-internals/#hsts in the address bar.
2. Under Delete domain security policies, enter the vCenter Server or ESXi hostname in the Domain field.
3. Click the Delete button.

Note: Once cleared, log in to the web UI. If the error remains, test on another browser or machine to rule out local browser settings.