Mark923

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

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

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 t

I tried this approach (uninstall/reboot/install and then run the command from the terminal) and I have found that the workaround works. In my case the reboot was the key additional step to get it working.

Sadly this new workaround also doesn't work for me....

The workaround doesn't work for me either.