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

 

Thank you for sharing these detailed findings and your experience.

We’ve shared the information you've provided with our Product Team for further investigation. Your input helps us improve Enpass, especially in identifying misleading sync status in scenarios like the one you've outlined.

We'll keep you posted with any updates or follow-ups from the team. If we require any additional details, we’ll be sure to reach out.

#SI-4358

Please follow these steps:

1. Disconnect sync on all your devices.

2. Ensure that the date and time settings are set to automatic on all devices.

After completing these steps, proceed as follows:

1. Reconnect sync on all devices.

2. Add a new item on one device and verify if it syncs across all other devices.

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.

Could you please provide the number of items and attachments you are syncing with the WebDAV server? Additionally, we would appreciate it if you could share the size of the database by taking a backup of the vault you are attempting to sync with WebDAV.