Jump to content
Enpass Discussion Forum

Andreas M.

  • Posts

  • Joined

  • Last visited

Posts posted by Andreas M.

  1. 9 hours ago, Gulshan Dogra said:

    Hi @Black1210,

    Please DM me the details of your WebDAV demo account and share its login id and password along with the URL. I will then get this investigated for you on priority.

    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.






  2. 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"


  3. 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.

  • Create New...