rptr

Hopefully this might be of some help – to users with issues or for the Enpass developers troubleshooting. I ran into a similar issue while moving from Microsoft Edge to Firefox. My fields did not get populated, Enpass extension froze with the Enpass application crashed shortly after. At the time was running: macOS 13.2 Enpass 6.8.4 Enpass extension (don’t remember the exact version number, but latest version pre- 6.8.3 as it stands today) 2 vaults I tried re-installing Enpass, Enpass extension and Firefox. Also tried different versions of Firefox with no luck. I then tried setting up a new Enpass environment on a different computer running the same macOS and Firefox version and to my surprise it worked. This got me thinking that something in my Enpass settings/configuration was causing it to crash so backed up my vaults, completely removed Enpass app and extension, started over and imported the backed up vaults. The issue however was still there. While troubleshooting I noticed that I always tended to try the same website with my logins associated with it. In my case it was a Microsoft login (which I had multiple of). When troubleshooting the individual logins connected to the same Microsoft URL (by removing autofill for those URL’s and the URL field within the login) it started working and has been running fine for a couple of weeks now. I cannot for sure say which of those steps actually did the trick or if it was a combination of them, but it might point to that the Enpass app might have some troubles handling multiple login accounts to the same website or service. Hopefully this will be of some help to users running into this issue and for the developers of Enpass to patch this issue in the future. If some of you are going to try this out I strongly suggest that you make a fresh backup of your vaults and read the documentation about backup and re-installing Enpass before continuing. Though looking through your logins to see you have multiple accounts pointing to the same URL would be a harmless first step.

This issue can be marked as resolved. It was related to the time being off just ever so slightly. Re-synched my devices to NTP servers. Managed to find another similar thread in the forum which pointed me in the right direction. Thanks!

Hello, Recently I noticed an odd behaviour with the multi-factor auth within Enpass. I kept locking myself out of different services which I at first thought to be a timing issue where the 'one time code' ran out before I managed to copy and paste it from the Enpass app. But now when I'm looking a bit closely on this, it seems that the 'one time code' is generating the wrong digits when added into Enpass. When setting up a new multi-factor auth (tried both with QR-scan and entering hashed code manually) I was not able to complete the multi-factor auth setup due to the code generated in Enpass not being accepted. However when i try the same process in another authenticator app, it works fine. When adding the same hashed code manually in Enpass and a different authenticator the 'one time code' shown differs. I'm running macOS 12.4 with Enpass 6.8.2 (build 1082) I've also tried this on Windows 10 and iPhone which generate same results. Assistance would be much appreciated.