Jump to content
Enpass Discussion Forum

David Jameson

  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by David Jameson

  1. OK -- I finally solved this by (a) disconnected Enpass from my NextCloud account  (b) deleting the entire Enpass folder on my NextCloud server  and (c) recreate the connection from Enpass to my NextCloud server (NB using WebDAV as the NextCloud option on Enpass still doesn't work)

    This fixed the problem and all my other devices are now syncing again.

    So something happened inside that Enpass folder (which nothing touches except the Enpass clients) that corrupted it and prevented Enpass from syncing again.

  2. screenshot_6028.png.09c6fb665c6a2153c608a87e618f4c19.png


    Can't give you a demo account - the server is inside my LAN and only intended for use inside - it's not open to the outside world.

    This problem is intermittent --- sometimes it can sync on my Mac and at other times I just get a sync error with a request for the password. And what's interesting is that when I enter the password again, it fails instantly as if it didn't even TRY to connect to the server.

    I would add that the password for that server, albeit a nice randomly generated password, hasn't changed in 7 years since it's not accessible to the outside world.



  3. I ran into exactly the same problem (no VPN though, my machine is on the same LAN with the server)  --- having updated to the version (where search speed is at least respectable), no version of Enpass will log into my nextcloud server, despite the fact that the URL, username and password are identical and other applications using the same credentials have no problem.


    I then updated NextCloud to the latest version (I was several versions behind) and now it seems to work again   , at least on my desktop -- I have not retested my iOS versions yet.

    • Like 1
  4. First of all it looks like they're not doing incremental searching - they seem to be waiting until you stop typing before they do anything


    Secondly, it's crashing

    Thread 18 Crashed:: Thread (pooled)
    0   Enpass                                   0x10ecd2691 0x10ebc8000 + 1091217
    1   Enpass                                   0x10eceaed2 0x10ebc8000 + 1191634
    2   Enpass                                   0x10eea0d00 0x10ebc8000 + 2985216
    3   Enpass                                   0x10ee93f25 0x10ebc8000 + 2932517
    4   Enpass                                   0x10ee6a16d 0x10ebc8000 + 2761069
    5   Enpass                                   0x10ee89636 0x10ebc8000 + 2889270
    6   Enpass                                   0x10f0e05de 0x10ebc8000 + 5342686
    7   Enpass                                   0x10f18d191 0x10ebc8000 + 6050193
    8   Enpass                                   0x11051dd3d 0x10ebc8000 + 26565949
    9   Enpass                                   0x11051a2ff 0x10ebc8000 + 26551039
    10  libsystem_pthread.dylib               0x7ff804cfc4f4 _pthread_start + 125
    11  libsystem_pthread.dylib               0x7ff804cf800f thread_start + 15

  5. Please don’t work on this issue…the workaround is trivial, just use WebDAV and the fix is (presumably) just to add the the rest of the URL automatically just like you tell people to do if they try to connect to NextCloud via WebDAV.

    Fix the damn painfully slow search problem!!!

  6. Abhishek -- I  reported this through your support system many months ago and clearly you forgot that you responded to that report at the time (see second image)

    Somehow, there seems to be a huge disconnect between what is said/reported in this forum vs. what actually gets done to address reported problems. Are there actually any developers still working on this product?

    I too am using the WebDAV workaround (at least that works)

    I am much more concerned about the absurdly slow search, which has also been reported many times in the past and is still not fied.





  7. 3 hours ago, Abhishek Dewan said:

    I have forwarded your concern to the dedicated team. As soon as they reply back with a resolution, I will be sure to update you on this forum. We appreciate your patience in the meantime.

    Really? I reported this issue as well, 6 months ago --- I ran into this NextCloud issue before running into the slow search problem. How can the development team still not know about it? Are they that isolated or disconnected from the company?


  8. It's been almost 6 months since I bought Enpass --- how can it be that you guys (Enpass) still haven't fixed the painfully slow search when running Enpass on a Mac, which presumably has been broken for even more than that 6 months?


  9. I'm running Big Sur on a 3.3 Ghz 12-Core Intel MacPro

    Enpass is version 6.7.3 (888)

    There is no crash --- simply very slow searching.   Below are two animated gifs - one shows Enpass, the other shows 1Password. Both have EXACTLY the same content (I imported 1Password into Enpass)  and in both, I'm doing exactly the same search. You can clearly see the difference.



  10. 1 hour ago, Discordant said:

    I believe Enpass may use an SQLite flat database without an index

    I don't really know much about what is needed to ensure security but if the data is being stored in a SQLite file, then presumably it is encrypted there and the index had better be encrypted as well so searching that directly would require decrypting everything on the fly. That doesn't sound like it would be very efficient.

    Anyhow, I'm not going to speculate on their implementation - simply noting that search is painfully slow and needs serious optimization.

    Everything else seems to work very well so I'm not unhappy I made the investment.

  11. I am switching from 1Password to Enpass on all my devices (because you can buy it without subscription and you can save vault to your own server - both great features)

    I was able to import my 1Password vault (completely, AFAIK) so that's also impressive.

    However, searching for an item is absurdly slow, taking several seconds to search about 900 items. Such a search should be pretty much instantaneous these days.

    Anyone know why it's so slow and/or whether it can be improved?


  12. Thank you - I'm familiar in general with the use of WebDAV but I think the point is being missed. You **specifically** include NextCloud as an option which suggests either (a) you're using a different protocol or (b) you're converting the user info to a WebDAV URL under the covers so the user doesn't have to worry about it.



    In particular note that your options are completely different for WebDAV than they are for Nextcloud, again suggesting that your system **knows** about NextCloud hence it's only necessary to provide the base URL for the latter.

    screenshot_5313.png.ce12f5fd8bf6169e7f20d99da335cf8c.png     screenshot_5312.png.f225213a376637e283f21c23846fb512.png


    Are you therefore saying that even though there is a choice to select NextCloud, I'm supposed to choose WebDAV instead?


  13. Despite the fact that both my regular nextcloud client on my desktop and my browser connection have no problem connecting to my nextcloud server, when I specify the standard URL for my server in Enpass (which I'm hoping can replace 1Password for my entire family), I get the message, "Could not connect to specified Nextcloud server. Please check your URL

    I recognize that one can use WebDAV but since Nextcloud was an explicit choice in the list of servers, I assumed I didn't actually have to use the WebDAV URL


    What's the scoop?

  • Create New...