Andreas M.

Oh please, are you serious? Letting your users do work on a bug that you should already be aware of. That's exactly the same bug as reported e.g. in these threads noted below - and it has been buggy for months and it has nothing to do with the specific WebDAV server of specific users. It is one thing to not get it fixed in a timely manner, but pretending that some user action would help although you know or at least should know about the bug since long ago is really really bad.

Hi @Manish Chokwal, I now used a completely different WebDAV server (different WebDAV server software, different physical machine) with a completely newly created vault – and the error happened again after just a week of using it. So this is NOT related to anything server-specific, and not even seems to be limited to WebDAV (see report on Dropbox showing the same error here). Unfortunately, I turned on logging just now after the error re-occurred. But it would be really great to see some effort to get this fixed, as this bug kills an essential function for me … Edit: The only syncing info I get now, after the error occurred, in the logs: Info: [HTTP] Using AUTO Proxy detection Info: [HttpClient] https://WEBDAVSERVER/Enpass/vault.enpassdbsync curlresultcode: 0 responseheaders: HTTP/1.1 207 Multi-Status Date: Fri, 19 Nov 2021 11:10:47 GMT Server: Apache Content-Length: 864 Content-Type: text/xml; charset="utf-8"

Hey @Manish Chokwal, thank you for you reply. I just noted that this problem is *independent of WebDAV*, as I just had the exactly same error message that my password on the server changed for the Wifi sync I used now as an alternative. My Enpass versions are 6.7.2 (887) on Mac (web version) and the most recent 6.7.1 from the App Store on iOS and iPadOS. Does enabling logging on the Mac help for finding the problem? Thanks for your help.

Hi @Abhishek Dewan and @Manish Chokwal, this is IMHO another instance of the same error reported in this thread. Would be great to see this fixed, as it re-occurs every few days even after completely resetting sync. Thank you!

Hi @Manish Chokwal, thank you for your answer. I have done exactly this already twice, but after a few days, sync starts failing again with the same error.

@Abhishek Dewan This seems to be the same issue reported here and here for WebDAV servers. Sync just seems to be completely broken for some people - this error message appears without having changed any password anywhere. As the WebDAV sync was the main reason I bought into Enpass, it would be great to see this fixed soon. Thank you.

This is a more general problem with WebDAV, it seems. I have the same issue with another WebDAV server, using 6.7.2 which is the latest for the Mac website version.

I see exactly the same behavior using Mac / iOS devices. I already reset the sync completely, but after a few days the same error occurred again …

Thank you, have been seeing this same issue for a long time, would be great to have it fixed!