If the 1Password browser extension doesn’t unlock when you unlock the 1Password app

Make sure you’re using a supported browser

If the 1Password browser extension doesn’t lock or unlock when you lock or unlock the 1Password desktop app, make sure you’re using a supported browser:

Make sure 1Password and your browser are up to date

Make sure you have the latest version of the 1Password desktop app, the 1Password browser extension, and your browser installed.

Check your settings

If that doesn’t fix the issue, make sure you have the appropriate settings turned on in both the app and the browser extension:

If you’re using macOS Ventura or later

If you’re using macOS Ventura or later, make sure 1Password has permission to perform tasks in the background:

1. Choose Apple menu > System Settings.
2. Click General in the sidebar, then click Login Items.
3. In the Allow in the Background section, make sure 1Password is turned on.

If you’re using a Windows PC

If your Windows username contains characters other than numbers and letters (for example: & or spaces), 1Password for Windows may not be able to communicate with 1Password in your browser.

To check for special characters in your Windows username:

1. Click the Start button and type “Command Prompt”, then press Enter.

2. Copy and paste the following command, then press Enter:

    whoami
   

If you see any special characters in your username, such as a space, follow these steps:

1. In your browser, copy and paste the appropriate address below into your address bar, then press Enter:
   • Chrome: chrome://flags/#launch-windows-native-hosts-directly
   • Edge: edge://flags/#launch-windows-native-hosts-directly
   • Brave: brave://flags/#launch-windows-native-hosts-directly
2. Click the menu for Force Native Host Executables to Launch Directly and choose Enabled.

If you continue to have issues after you change this setting, or if you use a different browser, contact 1Password Support for help.

If you’re using a Linux computer

If you installed 1Password for Linux or your browser using a containerized package manager such as Snap or Flatpak, the app won’t be able to communicate with 1Password in your browser.

To use 1Password for Linux with the 1Password browser extension, make sure you’ve installed both 1Password for Linux and your preferred browser using an installation method other than Snap or Flatpak, such as through your distribution’s built-in package manager.

To reinstall 1Password for Linux

To reinstall 1Password for Linux from a 1Password repository:

1. Uninstall 1Password for Linux using the package manager you installed it with.
2. Install 1Password for Linux using the steps for your Linux distribution.

To reinstall your browser

If your browser is installed through a containerized package manager, uninstall the default version of your browser and reinstall it using a traditional package manager. For example, you can install the Firefox .deb package on Debain-based Linux distributions after you uninstall the containerized version of Firefox.

If your computer is managed by your organization

If your computer is managed by your organization, make sure your IT team allows browser extensions to communicate with apps on your computer through native messaging:

1. In your browser, copy and paste the appropriate address below into your address bar, then press Return or Enter:
   • Chrome: chrome://policy
   • Edge: edge://policy
   • Brave: brave://policy
2. Copy and paste NativeMessagingUserLevelHosts into the policy filter box in the top right.

If you see a result for NativeMessagingUserLevelHosts with a value set to false, contact your IT team for further assistance. The 1Password browser extension won’t be able to connect with the 1Password desktop app unless this policy is changed.

Get more help

If you’re still having trouble:

1. Try to unlock 1Password in your browser, then save a console log.
2. Create a diagnostics report on your computer.
3. Contact 1Password Support with a description of the problem and the name of the browser you’re trying to use. Make sure to attach both the diagnostics report and console log.