brosenz Posted January 9, 2018 Report Share Posted January 9, 2018 For unknown reasons I get this error sometimes asking me to start the desktop app, and the desktop app is already running, look at the photo attached, If I try a second time it will be fine 3 Link to comment Share on other sites More sharing options...
Anshu kumar Posted January 10, 2018 Report Share Posted January 10, 2018 Hi @brosenz Sorry for the trouble you are going through. We have fixed some issues in a recent update 5.6.6 so please update the app and share your findings. Cheers! Link to comment Share on other sites More sharing options...
brosenz Posted January 10, 2018 Author Report Share Posted January 10, 2018 5 hours ago, Anshu kumar said: Hi @brosenz Sorry for the trouble you are going through. We have fixed some issues in a recent update 5.6.6 so please update the app and share your findings. Cheers! I had already installed the latest version 5.6.6 when I got the error. That's the reason I posted, because this used to be an error on earlier versions and I thought It would have been fixed in the last one, unfortunately it did not get fixed. Link to comment Share on other sites More sharing options...
brosenz Posted January 10, 2018 Author Report Share Posted January 10, 2018 6 hours ago, Anshu kumar said: Hi @brosenz Sorry for the trouble you are going through. We have fixed some issues in a recent update 5.6.6 so please update the app and share your findings. Cheers! Based on experience the last 15 hours I see the connection error more frequent now than with previous versions Link to comment Share on other sites More sharing options...
brosenz Posted January 11, 2018 Author Report Share Posted January 11, 2018 On 1/10/2018 at 2:24 AM, Anshu kumar said: Hi @brosenz Sorry for the trouble you are going through. We have fixed some issues in a recent update 5.6.6 so please update the app and share your findings. Cheers! Over the last 24 hours I have had more connection errors than ever, I would say 3 to 6 times more than with previous versions, clearly something is wrong Link to comment Share on other sites More sharing options...
brosenz Posted January 11, 2018 Author Report Share Posted January 11, 2018 (edited) On 1/10/2018 at 2:24 AM, Anshu kumar said: Hi @brosenz Sorry for the trouble you are going through. We have fixed some issues in a recent update 5.6.6 so please update the app and share your findings. Cheers! I would say connection error happens almost 100% of time when I do not use Enpass for one to two hours, and I guarantee that it is not the lock timeout because I have it set to 24 hours, and I do not get any request for credentials Edited January 11, 2018 by brosenz Link to comment Share on other sites More sharing options...
MarcS Posted March 23, 2018 Report Share Posted March 23, 2018 On 1/10/2018 at 2:24 AM, Anshu kumar said: Hi @brosenz Sorry for the trouble you are going through. We have fixed some issues in a recent update 5.6.6 so please update the app and share your findings. Cheers! Hi @Anshu kumar I am having the same problem after migrating to a new Mac, on Safari only (Chrome is working). macOS 10.13.3 / Safari 11.0.3 / Enpass 5.6.3 (139) (latest available in app store) / Enpass Safari Extension 5.5.2. Oddly, the same configuration has worked and still works fine on the old Mac. Any suggestions? Link to comment Share on other sites More sharing options...
Anthony Posted May 6, 2018 Report Share Posted May 6, 2018 I have also just encountered this issue. Windows 10 Pro x64 1803, Edge Browser, Enable browser extensions was already enabled. Enpass Extension for Edge Browser v5.5.2 Enpass Desktop (Windows Store bridged) v5.6.6 I generally see these issues when the Windows Desktop app is locked, and I then click on the Enpass browser extension button to invoke Enpass. It is as though it is not always cleanly handling communication to the locked desktop app. 1 Link to comment Share on other sites More sharing options...
Rainer101 Posted July 17, 2018 Report Share Posted July 17, 2018 Same here, on macOS 10.13.6 and Enpass v 5.6.9 with Safari extension v5.5.2 on a MacBook Pro Mid 2017. No autofill too. Works on Mac Pro, same software versions, all updated too. Link to comment Share on other sites More sharing options...
4oo4 Posted July 24, 2018 Report Share Posted July 24, 2018 I've been having this happen too the past couple months, but for me it works on Windows 10 but not on Ubuntu 16.04 (both using Firefox 61.0.1, Enpass 5.6.9). So far I've been fixing by disabling and re-enabling the addon. I don't have this issue with Chromum. Cheers Link to comment Share on other sites More sharing options...
vburdyko Posted July 31, 2018 Report Share Posted July 31, 2018 Just installed 5 beta of MacOS Mojave 10.14 (18A347E) and have this issue on both Chrome and Safari. Disabling, re-enabling, re-installing — there's no effect at all. Enpass 5.6.9(151) MacBook Pro Mid 2014 Link to comment Share on other sites More sharing options...
Anshu kumar Posted August 3, 2018 Report Share Posted August 3, 2018 Hi @vburdyko Sorry for the trouble you're going through. I've forwarded this issue to the dev team to look into it and I'll get back to you once I hear from them. Till then please co-operate with us. Link to comment Share on other sites More sharing options...
fmfm Posted August 7, 2018 Report Share Posted August 7, 2018 The new version of August 7 (5.6.11 - 155) does not help. In the lack of support, I eventually found this go-around: in Enpass preferences, tab "Browser", uncheck "Verify browsers" (I translate from my langage, no idea it is exactly in English but something like that). Hope this helps Francesco- Link to comment Share on other sites More sharing options...
fmfm Posted August 7, 2018 Report Share Posted August 7, 2018 Now Enpass extensions connects to the main Enpass App and autofills within browsers: it works fine back again, like some months ago. Clearly, the current versions of Enpass do not recognize mainstream browsers like firefox, chromium.... (ouch) Francesco- MacOS 10.12.6/MacbookPro 15" Enpass 5.6.11 (155) (latest) Safari 11.1.2 (latest) Chromium 68.0.3440.84 (latest) Firefox 61.0.1 (latest) Link to comment Share on other sites More sharing options...
kwieto Posted September 6, 2018 Report Share Posted September 6, 2018 Same here, the "Enpass connection error" makes is useless for Edge. Sometimes it works, most of the time not. Application and extension in their latest available versions. I see this happens at least for some users for months, so it is nothing new, but still not corrected. Currently I'm testing another software and it is working fine, so it can be done properly. Link to comment Share on other sites More sharing options...
Anthony Posted September 7, 2018 Report Share Posted September 7, 2018 I'm seeing this issue more and more often now across multiple PCs. All running: Windows 10 1803 (17134.254) Microsoft Edge 42.17134.1.0 Enpass 5.6.19 (5548) (Desktop App through Microsoft Store) Enpass Edge Extension 5.5.2 If I go into the Enpass App -> Tools -> Settings -> Browser and Toggle 'Enable Browser Extensions' OFF and then back ON, then the Enpass extension works immediately. Link to comment Share on other sites More sharing options...
spot1701 Posted November 13, 2018 Report Share Posted November 13, 2018 On 9/7/2018 at 3:09 AM, Anthony said: I'm seeing this issue more and more often now across multiple PCs. All running: Windows 10 1803 (17134.254) Microsoft Edge 42.17134.1.0 Enpass 5.6.19 (5548) (Desktop App through Microsoft Store) Enpass Edge Extension 5.5.2 If I go into the Enpass App -> Tools -> Settings -> Browser and Toggle 'Enable Browser Extensions' OFF and then back ON, then the Enpass extension works immediately. +1 Same issue here. Link to comment Share on other sites More sharing options...
MarcS Posted November 27, 2018 Report Share Posted November 27, 2018 It's BACK ! Problem has returned after many problem-free months. Now, getting the error all the time. Everything is up-to-date: macOS Mojave 10.14.1 ; Safari 12.0.1 ; Enpass Safari extension 5.5.2 ; Enpass for Mac 5.6.11 Is there a solution? Link to comment Share on other sites More sharing options...
mschindl Posted December 14, 2018 Report Share Posted December 14, 2018 It's still a nightmare with Safari and there is no permanent workaround available :/ Same issue at my system with the version shown in the last post. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now