Jump to content

HQJaTu

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About HQJaTu

  • Rank
    Newbie
  1. New 6.20 dropped password copying while editing. I observed same change in macOS and Windows 10 store versions. Maybe this affects also iOS and Android versions. A typical workflow for changing an existing password is: Copy old password using Copy-button, old password is usually required during change Edit the entry Generate new password Click Show to reveal the newly generated password Copy the provisional new password from edit field Sometimes generated password isn't valid and manual editing is required. Reasons for this could be too long password containing invalid characters, etc. At this point old password is not yet lost. It is possible to cancel the change. On successful password change, Save the updated entry IMHO returning the previous functionality enabling editing and copying the password is absolutely necessary.
  2. With 6.20 update the problem seems to be gone. I'm not getting a flood of sync errors anymore.
  3. Ok. Windows 10 and macOS are free-of-charge. I happily paid for my iOS Enpass. So far customer support is simply managing expectations while giving polite "we will fix this soon". Other than that, past two months have been rather unfruitful. Like David, also I'm ready to help any way I can. This ridiculous bug is getting very annoying. If the sync fails, Enpass keeps retrying in a forever-loop spewing the 904035 love. It's like playing whack-a-mole. You dismiss the sync-error and quite soon it will pop out again.
  4. Yeah. The price of the product is right (doesn't cost a thing), but getting support for it can take quite a long time. Probably most users are going for commercial clouds and fixing WebDAV isn't a priority to Enpass devs.
  5. Thanks for that. I'll be looking forward for any new software versions which might address this issue. Meanwhile, I managed to replicate the problem on a laptop waking from sleep. There is no proxy configured, but this specific sync error will occur towards my WebDAV server. When that happens, sync attempt will continue forever without timing out. Since there is no Cancel Sync -button available to manually abort the forever failing sync, my fix is to quit Enpass and restart. Then the problem will be fixed. However, this does not happen every time after sleep wake. It happens often enough so, that I can confirm the failure.
  6. Ok. Then its not the same case I have. That's what I experience. All browsers trust the certificate chain ok, but Enpass doesn't. It seems to have a certificate vault of its own.
  7. I have exchanged couple emails with support and clarified my case to them, but haven't heard from them since. The current theory is, that any HTTP-proxy, transparent or regular will cause Enpass to interpret things incorrectly. Can you confirm: Storage backend. In my case its my own Linux box with the LE-cert using WebDAV. If you're getting this on a cloud provider, then it might be a different case. I know, most likely you wouldn't use LE-cert on those, but still ... covering all the bases. The target URL works ok and has valid cert on your browser. In Windows 10 check also Edge as is it will use system settings just like Chrome. Firefox won't use system settings. Is there is a proxy in use. A transparent proxy might generate a HTTPS-cert on the fly causing the issue. Your browser might accept the certificate root ok, but Enpass doesn't use your Windows 10 certificate storage at all. It would help this case if you can share the above details on your setup.
  8. Thanks for your response. I'll move this discussion to PM with details.
  9. Initial vault setup from own server goes ok. Something changed in version 6.0.5 (or 6.0.6) and now my Let's Encrypt certificate spits error on every sync. This is not happening on my Mac nor iPhone. Only on Windows 10 store version does that. Fix is to disconnect. At reconnect select "Bypass SSL certificate verification". After that, everything works ok. This is not a blocker, more like a nuisance. Early 6.x versions worked ok, but latest 6.1.0 does not. The obvious weird thing is, that the certificate IS valid and other platforms work ok.
×
×
  • Create New...