Why Chrome Cannot Open Your JetKVM Web Interface

Table of contents

  • JetKVM
  • JetKVM Mini Ethernet
  • JetKVM Mini W
  • JetKVM Web Interface
  • Loading video stream

Your JetKVM opens instantly in Safari, but Chrome refuses to load it. This is one of the most common support questions we receive, and in most cases it has nothing to do with the device or your network. Chrome has begun forcing local addresses onto HTTPS, while the JetKVM web interface is served over HTTP. This guide explains why it happens, walks you through a one-minute fix, and covers what to do if the setting will not stay changed.

1 The Short Answer

Chrome is upgrading your device address from http:// to https:// before it connects. Your JetKVM serves its local web interface over HTTP only, so the upgraded connection has nowhere to go and fails. Turn the upgrade off and the page loads immediately.

  1. Open chrome://settings/security in Chrome.
  2. Under HTTPS-First Mode, select Disabled. On older Chrome versions this is a switch named Always use secure connections; turn it off.
  3. Restart Chrome completely by opening chrome://restart.
  4. Open your device address again. It should load right away.

Prefer to keep the extra protection? Select Balanced instead of Disabled. Chrome will still try HTTPS first and only fall back to HTTP when the upgrade fails, which is usually enough to open the JetKVM web interface.

2 Why This Happens

Modern versions of Chrome enable HTTPS-First Mode by default in many regions. When it is active, Chrome automatically rewrites http:// addresses to https:// before connecting. The JetKVM web interface is served over HTTP, so there is no HTTPS service to connect to.

You enter: http://<device> Chrome uses: https://<device> JetKVM serves: HTTP only Result: Connection fails

Safari, Edge, and Firefox do not force this upgrade on local addresses, which is why the same address opens normally there. This is a browser policy difference, not a fault in your JetKVM and not a network problem.

This affects more than JetKVM. Any device on your local network that serves a web interface over HTTP can be affected, including routers, NAS devices, managed switches, and printers. The fix below works for all of them.

3 Before You Start: Is This Your Problem?

You are in the right place if at least two of the following apply to you.

  • The device web interface opens in Safari, but not in Chrome.
  • Chrome shows "This site can't provide a secure connection", "This site can't be reached", or ERR_CONNECTION_REFUSED.
  • You type an address such as http://192.168.1.50 and Chrome rewrites it to https://.
  • The page opened once after you clicked Continue to site, but stopped working again later.

Throughout this guide, replace 192.168.1.50 with the actual address of your device. Local addresses usually start with 192.168., 10., or 172..

4 The Fix: Disable HTTPS-First Mode in Chrome

The whole process takes less than a minute and only affects how Chrome handles HTTP addresses.

  1. Open the Chrome security settings: Type chrome://settings/security into the address bar and press Enter. The same page is also available from the Chrome menu: Settings > Privacy and security > Security.
  2. Find "HTTPS-First Mode" and turn it off. Depending on your Chrome version, this setting appears in one of two forms.

    Newer Chrome: a section named HTTPS-First Mode with three options. Select Disabled.

    Older Chrome: a single switch named Always use secure connections. Switch it off.

    ! Do not confuse this with "Use secure DNS". It is a completely different setting, usually shown just above or below this one. Changing it will not solve the problem.
  3. Restart Chrome completely. This setting is linked to your Google Account, so it only takes effect reliably after a full restart. The fastest way on any system is to open chrome://restart. To do it manually:

    Windows: close every Chrome window, then check the system tray to make sure Chrome is not still running in the background.

    macOS: press Command + Q. Closing the window alone is not enough.

    Linux: close all Chrome windows, or run pkill chrome in a terminal.

  4. Open your device address again. The web interface should now load. Check that the address bar still shows http://, and that the device status changes from "Connecting to device..." to connected.

5 If It Still Does Not Work

Work through these checks in order. Each one rules out a different cause.

  1. Check that the setting stayed changed: reopen chrome://settings/security. If it has returned to Strict, skip to Section 6.
  2. Check that you changed the right profile: Chrome stores settings per profile. If you use more than one, click your profile picture in the top-right corner, switch to the profile you use for the device, and change the setting there.
  3. Rule out browser extensions: open the device address in an Incognito window (Ctrl + Shift + N on Windows and Linux, Command + Shift + N on macOS). Incognito windows do not load extensions by default, so if the page opens there, an extension is blocking it. Ad blockers are the most common cause; disable the extension or add your device address to its allow list.
  4. Rule out a device or network problem: open the same address in Safari, Edge, or Firefox. If it fails there too, the issue is not the browser. Confirm that the device is powered on, the network cable is connected, and your computer is on the same network.
  5. Check our documentation: more guides are available in the JetKVM troubleshooting documentation.

6 If the Setting Keeps Reverting

If the setting changes back on its own, or if you are an IT administrator configuring many computers at once, apply a managed policy. Managed policies take priority over browser settings and account sync, so they cannot be overwritten.

! Administrator access is required. This section is intended for IT administrators. It is not needed for a normal home or office computer.

macOS: open Terminal and run the following commands, then fully restart Chrome.

sudo defaults write "/Library/Managed Preferences/com.google.Chrome.plist" HttpsOnlyMode -string disallowed sudo chown root:wheel "/Library/Managed Preferences/com.google.Chrome.plist" sudo chmod 644 "/Library/Managed Preferences/com.google.Chrome.plist"

Then open chrome://policy and confirm that HttpsOnlyMode is set to disallowed.

Windows: apply the Chrome policy HttpsOnlyMode with the value disallowed using Group Policy or the registry, then fully restart Chrome and verify at chrome://policy.

ChromeOS, Linux, and managed fleets: push the same HttpsOnlyMode = disallowed policy through your device management platform, such as the Google Admin Console or your MDM.

To undo the macOS change later:

sudo defaults delete "/Library/Managed Preferences/com.google.Chrome.plist" HttpsOnlyMode

7 Frequently Asked Questions

The questions we receive most often about this issue.

Why does the page open in Safari but not in Chrome?

Chrome upgrades local http:// addresses to https:// before connecting. JetKVM serves its web console over HTTP only, so the upgraded connection fails. Safari does not force this upgrade on local addresses.

Does disabling this make Chrome less secure?

It stops Chrome from automatically upgrading plain HTTP sites. Sites that already use HTTPS are still loaded over HTTPS, and Chrome still warns you about insecure pages. If you prefer to keep the protection, select Balanced instead of Disabled.

I cannot find "HTTPS-First Mode". Where is it?

Go directly to chrome://settings/security instead of navigating the menus, since menu layouts differ between versions. You can also type HTTPS into the search box at the top of the settings page. This works even when Chrome is not in English, because "HTTPS" is not translated.

Will this change affect my other websites?

No. It only affects whether Chrome automatically upgrades HTTP to HTTPS. Your account, passwords, bookmarks, extensions, and history are untouched.

Why did it work before and stop working later?

Clicking Continue to site on the Chrome warning page grants access for about 15 days. When that permission expires, Chrome blocks the page again. Follow Section 4 for a permanent fix.

The option is greyed out and I cannot change it.

Your computer is managed by your organization, and the setting is locked by policy. Ask your IT administrator to apply the method in Section 6.

Is this a bug in my JetKVM?

No. The device is working as designed. This is a change in Chrome's default security behaviour, and it affects any local device that serves a web console over HTTP.

I use Edge, Brave, or another Chromium browser. Do I need to change anything?

Possibly. Chromium-based browsers share the same upgrade behaviour and usually offer a similar setting, often named "HTTPS-First Mode", "Always use secure connections", or "HTTPS upgrades". Firefox does not force this upgrade on local addresses.

Does this affect remote access to my device?

No. This setting only changes how your browser handles local HTTP addresses. Remote access through the JetKVM app or a remote address is unaffected.

Do I have the same problem with a domain name instead of an IP address?

Yes, it can happen. The upgrade applies to any HTTP address, not only IP addresses. If you use a hostname such as jetkvm.local, the same fix applies.

ⓘ Conclusion
Chrome now upgrades local HTTP addresses to HTTPS by default, which is why your JetKVM web interface stops loading there while Safari continues to work. Setting HTTPS-First Mode to Disabled and fully restarting Chrome solves the problem in under a minute, and it applies to every HTTP-only device on your local network. If the problem continues after following Section 4, please contact our support team with your Chrome version (open chrome://version), a screenshot of the message Chrome shows, your device model and address, and the result when you open the same address in another browser.

Related products

Back to blog

Leave a comment

Please note, comments need to be approved before they are published.