Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

jasn's Achievements


Newbie (1/14)



  1. As reported in these, (1.,2., 3.), forum threads as of last Thursday, (2019-09-05), iCloud authorization/sync is no longer working with Enpass across Windows, Linux and Mac OS platforms. In my case, the following specific combinations result in the iCloud Authentication errors, reported at the top of this thread; Windows 10 Pro, Version 1903, OS build 18362.329 Enpass 6.1.2 (432) Firefox 69.0 (64-bit) Microsoft Edge 44.18362.329.0 Manjaro Linux 18.0.4 Enpass 6.1.1 (451) Firefox 69.0 (64 bit) (current versions of most of the other browsers available in the Arch repositories, including Chrome, Chromium, Brave, Opera, etc.) Android version 9 Enpass (current version) Chrome (current version) Firefox (current version) In this thread, Mac OS users have also reported the same failure with the Mac Enpass client. The only combination that would allow me to sync my Enpass client with my iCloud account correctly was the following OS/Browser/Enpass client combination; Windows 10 Pro, Version 1903, OS build 18362.329 Enpass 6.1.2 (432) Internet Explorer Version 11.295.18362.0 It would be helpful if these issues were consolidated into a single thread since this is impacting multiple platforms. Thanks..
  2. Anshu, This issue exists across clients and platforms. I reported in this thread here, that I'm having the same issue with the Windows, Linux, and Android, Enpass clients. It would be helpful if there was some consolidated response to this iCloud sync issue as it does not only apply to Mac Enpass clients. Thanks, Jason
  3. I've also discovered that I can no longer reauthorize my Enpass client on my Android phone using either Chrome or Firefox, with my iCloud account.
  4. The Linux Enpass client has a three pane view with the menu options available horizontally across the top of the app, and the left panel displays the Categories, Tags, and Audit information. The Windows client has the menu options running vertically, and the same panel that's visible on the left side of the Linux client, is collapsed in the Windows client and must be opened to look at the categories, etc. How can I make the Windows client layout be identical to the Linux client 3 pane layout? TIA..
  5. I have had this problem consistently on my PC running Windows 10 Pro, Version 1903, OS build 18362.329, using Enpass 6.1.2 (432), as well as when running Manjaro Linux 18.0.4, using Enpass 6.1.1 (451). When Enpass instructed me to reauthorize with my iCloud account, I first tried resyncing, and then I disconnected and tried to setup the iCloud sync as new. After multiple attempts over a 12 hour period, I consistently received the same "Authentication Error This action could not be completed" error messages described in this thread. Under Windows 10 I tried both of the following browsers without success; Firefox 69.0 (64-bit) Microsoft Edge 44.18362.329.0 However, when I switched to the following browser; Internet Explorer Version 11.295.18362.0 And attempted to sync to my iCloud account, I was able to successfully complete the action. Unfortunately under Linux, I was not able to find any browser that would let me sync with my iCloud account successfully. P.S. Why does this forum disallow posting while connected through VPNs? That makes using the forum pretty cumbersome for me.
  6. Thanks djsmiley! I just copied your ebuild to my local overlay, digested it, and then emerged Enpass 6 into my system. I did manually chmod+x both /opt/enpass/Enpass and /opt/enpass/importer_enpass. However, then not only did the new Enpass icon show up correctly in my Gnome Applications -> Accesories menu, but when I setup my Enpass sync, the enpassauth call was correctly handled by Firefox, and I was asked if I wanted to open Enpass to handle the link. I clicked to open it in Enpass, and sync was correctly setup. I didn't need to do anything else. Jason
  7. Thanks very much Vinod. Installing sys-process/lsof and then a reboot, indeed fixed my browser connection issue completely. Now everything appears to be working fine. In terms of the "QSQLCIPHER driver not loaded" error condition, I'm not sure exactly what the issue was. The thing I was seeing was when I selected "Minimize App to System Tray", the app would autorun, (even though I had not selected it to), and I would get the error condition described. I was confused as to how exactly Enpass could be set to autorun, when I had not specifically selected it. Right now I'm running the 5.5 beta, with "Minimize App to System Tray" selected, (and not autorun), and everything appears to be working correctly, so I'll keep it there for now. Thanks again, Jason
  8. I performed a clean install of 5.4.1 using the Enpass installer, in favor of the Gentoo ebuild. One of the reasons is that the installer installs a decent uninstall tool, which does not get installed with the Gentoo ebuild. I also specifically installed the software as sudo/root, and installed Enpass into /opt/Enpass. I think that I recreated the "QSQLCIPHER driver not loaded" condition when I specifically select the "Minimize App to System Tray" option in the Enpass settings. Prior to selecting that option, I rebooted my system several times and Enpass didn't autostart, and I could open my wallet without issue. Then I selected "Minimize App to System Tray", and reboot, and Enpass autostarts, and generates the error condition described. Then I decided to try the Linux 5.5 beta, and I configured it with the "Minimize App to System Tray" option, and rebooted, and it appears to be working correctly. I'm not sure this is the issue, but if anyone else is experiencing similar issues, they can try uninstalling Enpass and the Enpass data, and then reinstalling the app completely. Then after running Enpass, don't select the "Minimize App to System Tray" option, and see if Enpass works correctly through a reboot of the system. Alternatively you can try the beta 5.5 to see if this addresses the issue. As far as the browser connection error, still no fix for this issue on my system. Thanks..
  9. Hello, I'm having two problems with Enpass 5.4.1 on a new Gentoo Linux / KDE Plasma 5 system. The initial installation works fine and I can sync and open my wallet without issue. However, the first problem is that I cannot get a connection to any browser. I've tried Firefox, Chromium, and Vivaldi, with the plugin installed from their respective official sites, and they all give the Enpass connection error page. The only similar thread reporting this problem here is this one, and they mentioned that starting Enpass first, and then the browser, worked for them, however it doesn't work for me in this case. The second problem is that after a reboot, the Enpass app autostarts, (without my setting this in the app), and asks me to unlock my wallet. It won't recognize my master password, and I get the "QSQLCIPHER driver not loaded" error message in my .xsession-errors file, as reported in these two threads, (1., 2.), and probably this one too. If I uninstall the Enpass application, and delete my data, then I can reinstall and resync, and everything is fine, until I reboot. BTW, after the reboot, when I enter my master password into Enpass, the following lines are generated in my .xsession-errors; QSqlDatabase: QSQLCIPHER driver not loaded QSqlDatabase: available drivers: QSQLITE QMYSQL QMYSQL3 In terms of installation, there is an unofficial Gentoo ebuild maintained in the ssnb overlay, here, which I used to install Enpass 5.4.1. In the Gentoo ebuild system you can rename the ebuild to the current version number, and it will typically install the named version. So even though the last Enpass ebuild in the ssnb overlay is for version 5.3, renaming it to 5.4.1, and installing it in my local overlay, allowed me to install Enpass 5.4.1 successfully, (in /opt/Enpass). However, I also downloaded the Enpass Linux installer and followed the instructions here, which don't specify running the installer as root, and the app was in installed in my user home directory. Feel free to ask for any additional information that may help identify these problems. At this point, an answer to the second issue is the higher priority, as, for the time being, I can live with the first. Also I have two questions regarding Enpass; 1) Is it recommended to install the app for all users? (If so, does running the Enpass installer as sudo/root accomplish this?) Or should the Enpass installer be run as a user, and installed in the user's directory structure? 2) How can Enpass autostart when I didn't enable it? There is nothing in my ~/.config/autostart directory. Does the Enpass autostart option install an autostart file somewhere else? Where should I look? Thanks..
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy