Bebef

Thanks for that answer, but how is that supposed to fix a server that wont accept uploads over a certain size and therefore effectlvely inhibit syncing? I mean, I did all this over and over again. It LOOKED like it worked, over and over again. Just by chance I noticed that in reality, it didn't. It would SAY sync was totally fine when in reality it didn't sync. That's the nasty part about that bug. You think everything is in order when it really isn't. Once again, the root cause was the server, and Enpass failed to notice that properly.

Hi everyone! Investigating more on issue Sync Error 1308413 on Portable (Windows) - Windows PC - Enpass Discussion Forum, I have found that a misconfiguration of the webserver prohibited file uploads of a certain size. The vault.enpassdb file was too large to be uploaded. which resulted in an error when connecting new clients. However, as I hade had changed the server (physically), I did not re-setup any Enpass client, as they claimed(!) that everything was just fine. So, Enpass would claim that it synced and that everything was in perfect order, when in reality it couldn't upload vault.enpassdb, which clearly is wrong! I thought that everything was in order, but only recognized the error, when clients started not seeing new items from other clients. I think this is a serious bug, as it's quite misleading to the user. Enpass should not report sync as being OK when clearly it isn't (vault.enpassdb couldn't be uploaded). I assume you can replicate the issue if you configure a DAV server not to accept files over a certain size. In my particular case, I used the Nextcloud docker installation. That should give the same error right out of the box. Cheers, Steffen

Hi everyone, I'm using portable on my computer. As I have set up a new computer, I have set up an entirely new sync from scratch. Sync is done trough Nextcloud WebDAV. I can initially set up the vault ONCE. It syncs and I see all the current vault data. After that, I cannot sync a second time. I can see that it actually does something, as it does a login against Nextcloud, but all I get is the error "Sync Error Something went wrong while syncing with Nextcloud. Error code: 1308413" I tried to set everything up again. This time, when opening Nextcloud (after closing it after the initial setup), I get error code 1304401. Disconnected, set up sync again, now it's 1308413 again. Regardless, pattern stays the same. I can set it up ONCE, after that it breaks and does no longer sync. Cheers, Steffen

Hi Manish, here's the information you've asked for: Enpass 6.7.1.572 Android 12, Security update April 2022 Cheers

Hi everyone! Every other day, I get a notification from "Android System" which says: Check access settings Enpass can view and control your screen. Tap to review. When I tap the notification, it will take me to the Accessibility -> Enpass settings. "Use Enpass" of course is enabled, as I want to make use of this feature. How do I get rid of this? Thanks

I can confirm that the issues seem to be fixed in the 6.4.0.627 beta version.

I already tried 6.3.3 and the issue still is the same.

Hi @Kashish, thanks for the update! Cheers

Still nothing? I chose Enpass for the support of Linux. However, I wonder whether there actually is support for Linux...

Have you tried 6.1.0? See also

Any updates on this? @Kashish Although others already answered this: 600+ items, sync via WebDAV, no change of location. All other platforms are on 6.3.x already, I wonder why Linux still is on 6.2.0... @Kashish How far may versions diverge and still sync properly? Thanks

A reaction from the developers sure would have been nice.

I'm using Enpass 6.1.0.407 which is the latest version that works properly for me. Both 6.1.1.451 and 6.2.0.537 tend to lock up or take a very long amount of time (minutes) when searching and displaying an entry. The UI just locks up and it takes quite some time to come back. All issues are gone once I switched back to 6.1.0.407 I'm running Ubuntu Budgie 19.04 on X11. Please advise