Mark923 Posted June 26, 2019 Report Posted June 26, 2019 Hi, I am trying to get Enpass working on a clean install Windows 10 laptop. I'm using the Enpass install from the Windows store and the Chrome extension from the Chrome store. When I click on the extension icon in Chrome, it displays the "looking for Enpass" page and if Enpass isn't it then launches it. But then it errors with "Enpass Assistant is unable to connect with the Enpass app." I initially suspected that the Sophos antivirus on the laptop was interfering with the comms to 127.0.0.1 - BUT, Enpass works just fine in MS Edge (using the Edge extension) and also Vivaldi (using the Chrome extension from the Chrome store!!!!). I really don't understand what's causing Chrome to fail, especially as Vivaldi works... Enpass version is 6.1.0 (408) and Chrome extension is 6.0.2 - If it helps, Firefox behaves exactly like Chrome. Thanks.
Mark923 Posted June 26, 2019 Author Report Posted June 26, 2019 I've had to split my message as the message checker doesn't like me and/or code boxes ... If I enable logs in the extension I get: 26/06/2019, 13:31:01 : Connecting using websocket 26/06/2019, 13:31:01 : Opening connection on ws://127.0.0.1:10391 26/06/2019, 13:31:01 : Connection opened 26/06/2019, 13:31:01 : Connection established on port 10391 26/06/2019, 13:31:02 : Message parsed successfully 26/06/2019, 13:31:02 : Greetings from Enpass 26/06/2019, 13:31:02 : Self Initiating srp. 26/06/2019, 13:31:02 : Authentication required 26/06/2019, 13:31:02 : Termnating srp initialization process. 26/06/2019, 13:31:27 : Message parsed successfully 26/06/2019, 13:31:27 : App Different user. 26/06/2019, 13:31:27 : Closing connection 26/06/2019, 13:31:27 : Disconnecting Manually. 26/06/2019, 13:31:27 : Bug with 10391 26/06/2019, 13:31:27 : Connecting using websocket 26/06/2019, 13:31:27 : Opening connection on ws://127.0.0.1:10392 26/06/2019, 13:31:28 : Opening connection on ws://127.0.0.1:10393 26/06/2019, 13:31:29 : Error with connection after other user reported. 26/06/2019, 13:31:29 : Got Error 26/06/2019, 13:31:29 : Opening connection on ws://127.0.0.1:10394 26/06/2019, 13:31:30 : Opening connection on ws://127.0.0.1:10395 Enpass is definitely listening on port 10391: C:\Users\uizmw>netstat -ano | findstr 10391 TCP 127.0.0.1:10391 0.0.0.0:0 LISTENING 12008 C:\Users\uizmw>echo off & (for /f "tokens=5" %a in ('netstat -aon ^| findstr 10391') do tasklist /NH /FI "PID eq %a") & echo on Enpass.exe 12008 Console 1 87,848K
Anshu kumar Posted June 27, 2019 Report Posted June 27, 2019 Hi @Mark923, Sorry for the trouble you are going through. I would like to share that Enpass app communicate with the other browsers (Chromium or Firefox based browser) via localhost address (127.0.0.1). Although Enpass extension for Edge browser communicate with the main app via NMHost that's why Edge browser extension is working fine and other browser is throwing Enpass connection error. So please bypass the localhost(127.0.0.1) connection from Sophos Antivrus and let me know if the problem persists. Hope this helps!
Mark923 Posted July 1, 2019 Author Report Posted July 1, 2019 Thanks for giving an insight why MS Edge works - I wondered if it used a different mechanism. The Sophos on this PC is managed centrally, so I can see if I can get the IP/port opened. *but*... what completely confuses me is that Chrome does not work whereas Vivaldi (which is based on Chromium and actually uses the extension from the Chrome store) *does* work. If the IP/port was being blocked by Sophos, then Vivaldi ought not to work, as it's using the same approach as Chrome. But it does...
atygert Posted September 20, 2019 Report Posted September 20, 2019 I encountered this, again, for no apparent reason. Enpass was working fine one day. The next, I started getting this message in a tab in Chrome every time I opened a new browser. Looking in the Browser section of Enpass, where I expected to see Chrome, it's path and an "authorized" icon, I saw nothing. There appears to be no rhyme or reason to why this happens. My frustration with having to wait two business days, minimum, to get a response forced me to uninstall the app and the Chrome extension. Once that was done, I rebooted and reinstalled both. The sync to my vault happened and I authorized the browser. All is working now. Even though I have it fixed, this seems like a prevalent enough problems that there should be more attention given to it. Uninstall/reinstall is not an exceptable long term resolution. This has been happening for a while and Enpass should get to the bottom of why the extension disappears and the connection fails.
atygert Posted October 13, 2019 Report Posted October 13, 2019 It happened again. I've been seeing this problem every few weeks for a while. Very frustrating. I opened a case and was asked to grab a bunch of different log files, which I can't recall. I got the thing working by deleting everything and reinstalling, but my patience is wearing thin. May be time to start looking for another product. Rebuilding every week or two is untenable. Windows 10 1809 Chrome Version 77.0.3865.120 (Official Build) (64-bit) Enpass Password Manager extension for Chrome Version 6.0.2 Enpass 6.2.0 (542)
leftliber Posted January 14, 2020 Report Posted January 14, 2020 On 6/27/2019 at 3:47 PM, Anshu kumar said: Hi @Mark923, Sorry for the trouble you are going through. I would like to share that Enpass app communicate with the other browsers (Chromium or Firefox based browser) via localhost address (127.0.0.1). Although Enpass extension for Edge browser communicate with the main app via NMHost that's why Edge browser extension is working fine and other browser is throwing Enpass connection error. So please bypass the localhost(127.0.0.1) connection from Sophos Antivrus and let me know if the problem persists. Hope this helps! Could you please let me know how to bypass the localhost, when in a managed sophos environment? In my sophos endpoint there's no "protection" tab to make the exception.
Kilian Schwarz Posted January 29, 2020 Report Posted January 29, 2020 Hi, I have the same problem. And have a solution programmed. This program closes the swi_fc.exe temporarily and the extension can connect / audify again with Enpass. https://github.com/Kilian-Schwarz/EnPass-swi_fc/releases For me it works very good. Sincerely yours Kilian Schwarz
FirecrackerBE Posted April 9, 2020 Report Posted April 9, 2020 I'm having the same problem. Even after excluding the localhost address as instructed. @Anshu kumar, the problem persists. Can you please further investigate and give us a working solution for this annoying problem?
Garima Singh Posted April 9, 2020 Report Posted April 9, 2020 Hey @FirecrackerBE Welcome to the forum! Please revert to us with the answer to the following queries and we will get it sorted out for you: On which device (along with OS version) are you using Enpass? Which Enpass and Enpass extension version are you using? Which Chrome version are you using? Are you facing the same problem with other browsers too? Are you using any Antivirus or third-party security-related extension? Also, let us know the error you getting? Thanks.
FirecrackerBE Posted April 29, 2020 Report Posted April 29, 2020 (edited) On which device (along with OS version) are you using Enpass? WINDOWS 10 PC, version 1903 Which Enpass and Enpass extension version are you using? Enpass version 6.4.1 (642), browser extension for chrome version 6.4.0 Which Chrome version are you using? Chrome Version 81.0.4044.129 Are you facing the same problem with other browsers too? No, Edge, Vivaldi, Opera work fine. Are you using any Antivirus or third-party security-related extension? Sophos free antivirus Also, let us know the error you getting? Well, I use it in Dutch version, so the exact error is "Verbindingsfout! swi_fc.exe voorkomt dat de Enpass-extensie verbinding maakt met de Enpass-app.", roughly translated to: Connection error! swi_fc.exe is preventing the Enpass extension to connect to the Enpass app. I already tried the solution described at "https://www.enpass.io/support/kb/security/enpass-browser-extension-is-not-working-due-to-sophos-antivirus/". The local adress is excluded in any possible way, but I still get the error. Furthermore, this doesn't make sense, as other browsers (Opera, Vivaldi) have no problem. I understand Edge works differently, but Opera and Vivaldi work the same as Chrome I believe? Please advise @Garima Singh . Edited April 29, 2020 by FirecrackerBE
Pratyush Sharma Posted April 30, 2020 Report Posted April 30, 2020 Hi @FirecrackerBE, Thanks for sharing the details. Could you please try disabling "Authorize Browsers with Verified Code Signatures Only" in Enpass Browser settings? Let us know what are the results.
FirecrackerBE Posted May 5, 2020 Report Posted May 5, 2020 @Pratyush Sharma I disabled the option. I closed Chrome. Opened again. Still the same problem. Then I later rebooted the PC and tried again. Same problem. Other suggestions?
Garima Singh Posted May 5, 2020 Report Posted May 5, 2020 Hey, @FirecrackerBE Thanks for writing back. Please reinstall the extension and check. If issue persists, please try re-installing Chrome and share the findings with us. Thanks.
FirecrackerBE Posted May 12, 2020 Report Posted May 12, 2020 I reinstalled the extention, to no avail. Reinstalling Chrome will have to wait. I have some things stored and configured that I don't want to lose right now. I'll try it as soon as I can.
Pratyush Sharma Posted May 13, 2020 Report Posted May 13, 2020 Hi @FirecrackerBE, Thanks for writing back in. Please share your finding with us after reinstalling the Chrome browser.
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