Browser extension breaks on failed NFS auto mount
I've been having occasionally weird issue with my 1Password that I've finally isolated to a bizarre scenario. I have several NFS mounts configured with systemd via mount & automount units. If those mounts timeout (due to my NAS being unavailable) then the 1Password browser extension cannot communicate with a 1Password app. In addition, 1Password app takes enormous amount of time to unlock with Master password (5-10 minutes) and showing "processing ring" on password type.
So the symptoms are as follows:
- When mount fails to automount, with unlocked 1Password app upon clicking browser extension, there is a button Open Application rather than showing the usual UI with password, clicking the button does nothing
- When mount fails to automount with locked 1Password app, extension shows Unlock button, upon clicking it, open 1Password app it successfully unlocks, however when trying to access extension again it goes to the scenario above ^
- When mount fails to automount with locked 1Password app, opening 1Password app directly shows window, upon typing a password it takes long time to unlock application (can be very random, but it takes at least several minutes), does not matter if password was typed correctly or incorrectly
I saw this issue occasionally (sometime during heat waves I shutdown my NAS and now when I know I saw that as well during maintenance windows (firmware update etc)), but only lately (due to hot weather and shutdowns) I've noticed the pattern.
1Password Version: 8.10.7
Extension Version: 2.11.0
OS Version: Fedora Linux 38 KDE
Browser:_ Firefox/Chrome
Comments
-
Hi @herr_orange! I just wanted to let you know that we've received the email you sent in about this issue, and a member of the team will be in touch with you there shortly 😄
ref: RTU-18147-146
0 -
@1P_Gem yes, thank you, we're working with support team on my issue, appreciate it!
0
