Troubleshooting GateKeeper Browser Extension 2.3.0

Overview

GateKeeper recently released version 2.3.0 of the GateKeeper browser extension for Chrome, Edge, Firefox, and other supported browsers.

Starting with version 2.3.0, the GateKeeper browser extension communicates with the GateKeeper Client application exclusively through Native Messaging.

Earlier versions of the browser extension could communicate with the local GateKeeper Client over HTTPS as a fallback method. This HTTPS fallback is no longer used in browser extension version 2.3.0.

Native Messaging support was introduced in the GateKeeper Client application starting with the 3.16 release in early 2025. To ensure the browser extension works properly, the workstation must be running a GateKeeper Client version that supports Native Messaging.

Recommended Client Version

Please confirm that the workstation is running the latest version of the GateKeeper Client application.

The latest GateKeeper Client version is:

3.18.14.0

The latest version can be downloaded from your GateKeeper Hub or from the download link provided by GateKeeper Support.

Common Cause

If the GateKeeper browser extension is not working after updating to extension version 2.3.0, the most likely causes are:

• The installed GateKeeper Client version does not support the Native Messaging workflow required by browser extension version 2.3.0.
• The Native Messaging host registration is missing or incorrect on the workstation.
• The browser extension was updated, but the local GateKeeper Client application was not updated.
• Reinstalling only the browser extension was attempted, but the issue is related to the local Client or Native Messaging registration.

Important Note

Please do not uninstall the GateKeeper Client application as a first troubleshooting step.

Reinstalling only the browser extension usually will not resolve the issue if the problem is caused by the local GateKeeper Client version or the Native Messaging host registration.

Native Messaging Registry Locations

The Native Messaging host should be registered in both the 64-bit and 32-bit registry locations when applicable.

Google Chrome

Registry paths:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.untetheredlabs.nativemessaging

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\com.untetheredlabs.nativemessaging

Expected value:

• Key Name: Default
• Type: REG_SZ
• Data: C:\Program Files (x86)\Untethered Labs\GateKeeper Client\chromium.json

Microsoft Edge

Registry paths:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Edge\NativeMessagingHosts\com.untetheredlabs.nativemessaging

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Edge\NativeMessagingHosts\com.untetheredlabs.nativemessaging

Expected value:

• Key Name: Default
• Type: REG_SZ
• Data: C:\Program Files (x86)\Untethered Labs\GateKeeper Client\chromium.json

Mozilla Firefox

Registry paths:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\NativeMessagingHosts\com.untetheredlabs.nativemessaging

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Mozilla\NativeMessagingHosts\com.untetheredlabs.nativemessaging

Expected value:

• Key Name: Default
• Type: REG_SZ
• Data: C:\Program Files (x86)\Untethered Labs\GateKeeper Client\mozilla.json

Troubleshooting Steps

1. Confirm the GateKeeper browser extension version.
   • Open the browser extension page.
   • Confirm the GateKeeper extension is version 2.3.0 or later.
2. Confirm the GateKeeper Client version.
   • Make sure the workstation is running a GateKeeper Client version that supports Native Messaging.
   • We recommend updating to the latest GateKeeper Client version, 3.18.14.0.

3. Confirm the GateKeeper Client application is installed.

   • The expected installation path is:

   C:\Program Files (x86)\Untethered Labs\GateKeeper Client

4. Confirm the Native Messaging JSON file exists.

   • For Chrome and Edge, confirm the following file exists:

   C:\Program Files (x86)\Untethered Labs\GateKeeper Client\chromium.json

   • For Firefox, confirm the following file exists:

   C:\Program Files (x86)\Untethered Labs\GateKeeper Client\mozilla.json

5. Confirm the Native Messaging registry entries exist.
   • Check the appropriate registry paths for Chrome, Edge, or Firefox.
   • Confirm the Default value points to the correct JSON file.
6. Restart the browser.
   • Fully close the browser.
   • Reopen the browser and test the GateKeeper extension again.
7. Restart the GateKeeper Client service or reboot the workstation.
   • This can help confirm the Client and browser extension reconnect properly after the Native Messaging registration is corrected.

If the Issue Continues

If the browser extension still does not work after confirming the Client version and Native Messaging registration, please contact GateKeeper Support and provide the following information:

• GateKeeper Client version
• GateKeeper browser extension version
• Browser name and version
• Screenshot of the browser extension issue
• Screenshot of the relevant Native Messaging registry path
• GateKeeper Client logs from the affected workstation

Summary

GateKeeper browser extension version 2.3.0 requires Native Messaging to communicate with the local GateKeeper Client application. The older HTTPS communication fallback is no longer used.

To resolve most extension communication issues, confirm that the workstation is running the latest GateKeeper Client version and that the Native Messaging host registration exists for the browser being used.

For any additional questions or concerns regarding faster 2FA, proximity settings, computer locking, password management, or compliance, please contact GateKeeper Enterprise support using the Support Ticket form on https://gkaccess.com/support/ or email [e-mail].