Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

davidc's Achievements


Rookie (2/14)

  • First Post
  • Collaborator Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. Yes this is happening repeatedly now. Latest Enpass for Windows 6.8.5. Latest Enpass for iOS 6.8.6.
  2. It seems the file was corrupted somehow, possibly by the iOS client where I just changed a password for the first time in years. occ files:scan rebuilds the index and makes the curl error go away Sync then results in: "It seems that password of data on NextCloud has been changed lately. Please enter the new password to continue sync." Entering my master password does not work, so I guess the file has been corrupted. I am not given the option to push the latest version from my laptop to Nextcloud, what is the safest way to do this without losing any data? I know the vault on my laptop is currently good. I see the file on my laptop is named Vaults\primary\vault.enpassdb whereas the vault on Nextcloud is named Enpass/vault.enpassdbsync i.e. has a different file extension. Can I overwrite the .enpassdbsync with the .enpassdb from my laptop or is it in a different format? Or should I copy this file instead from my laptop: Enpass\.sync\primary\Nextcloud.enpassdbsync ?
  3. "Something went wrong while syncing with NextCloud. Error code: 1307018" Could that be a less helpful error message? Where is the logfile so I can see what actually went wrong? The Nextcloud instance is running fine and all desktop and mobile Nextcloud clients are syncing just fine.
  4. What server? There is no server involved, Enpass runs on my computer. To this day, Enpass continues to save the new password to a completely random different entry if you allow it to "update" when you change your password on a site. As a result I continue to maintain a text file duplicating all my passwords so I don't get screwed over when Enpass overwrites another crucial password. Absolutely ridiculous.
  5. This bug still exists. Enpass saves the details to the WRONG site record, completely obliterating the actual password that already existed for that completely different and unrelated site. Since I have no way of knowing whether a site's password is going to get lost until I try to access it, possibly months later when I no longer have the password in my head, I have now taken to writing down every single password in a text file, COMPLETELY OBVIATING THE POINT OF A PASSWORD MANAGER. How does Enpass continue to get something so completely fundamental wrong?
  6. Since this is now happening *every single time* I save an updated password, feel free to contact me to arrange a screen share to demonstrate the problem.
  7. Enpass is now, on every single device, saving updated passwords to the wrong vault entry. Every. Single. Time.
  8. These basic failures to (a) migrate data from 1password (b) synchronise data between machines (or even tell me when it fails to sync) and (c) frequently failing to actually save the right password or to the right place, make Enpass appear a complete joke, and result in us duplicating all passwords into text files anyway, making a farce of the concept of a password manager. I appreciate that you do a better job than 1password at autocompleting web forms, but why can't you get the fundamentals right? Really regretting moving everyone to Enpass and wasting all that money now. -davidc
  9. I was on site X earlier and entered a new password. The Chrome extension prompted me to save the updated password, which I did. I am now on site Y, which shares absolutely nothing in common with site X, and it is entering the wrong username and password. Looking at site Y in Enpass to find out why, I see it is showing URL for site Y, but the username, password, and webform details from site X! Looking at site X in Enpass, I see it hasn't saved the updated password either. It's only saved it to (overwritten) site Y. How on earth does this even happen? This is obviously a MAJOR security flaw as it is sending a password for one site to a completely different site that may be malicious. Enpass 6.1.1 (451) -davidc
  10. I don't know about that, I bought it on all the platforms, but it is clear there is a bug that is affecting more than one person i.e. is not user error. Enpass do you have a plan to fix this? Is there any debugging/logging anywhere at all that we can use to assist you? As I have mentioned, syncing to the same WebDAV server with the same credentials on another Windows 10 computer works fine. And on my laptop consistently fails with cryptic error 904035 (why not even bother to display a real error message?). -davidc
  11. One thing that is troubling me is that Enpass is making no efforts to inform me of a sync problem. I have to notice that something seems out of date and then I have to go all the way into the main app, menu, vault, to see that an error occurs. In the meantime I am creating sync conflicts. Enpass needs to be more bold about informing the user about sync problems - either repeatedly, or with a persistent dialogue that needs to be explicitly acknowledged before it goes away. It's not acceptable for things to be getting weeks out of sync without me knowing. -davidc P.S. I am back to getting 904035 consistently on my laptop. But I didn't notice until today because of the above problem.
  12. Hi, I can confirm that no proxy is in place at either end. If I have my desktop and my laptop on the same home network (both Windows 10), my desktop can sync fine with the WebDAV server but my laptop cannot (error 904035). Both are running Enpass 6.1.0 (407). I could not find any Enpass logfile. The server is Nextcloud on Linux with a Let's Encrypt certificate. The certificate is accepted automatically in both Internet Explorer and Edge. It is signed by Let's Encrypt Authority X3 which is signed by the trusted CA DST Root CA X3. I have also verified that the server is sending the chain certificate from the command line. But today it is working. Nothing has changed, I have not upgraded Enpass and the certificate on the server has not rolled over. There haven't been any Windows Updates either (I run OOSU to prevent them). Edit: it worked once, now it is giving Webdav error code 909975 -davidc
  13. Is there any update to this? I am also getting 904035 on sync on one Windows 10 computer but another Windows 10 computer works fine. Viewing the server logs I can see the one with the error isn't making any requests at all. I also use Let's Encrypt certificates. I'm not going to bypass certificate verification for obvious reasons! -davidc
  • Create New...