Jump to content
Enpass Discussion Forum

Mark923

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Mark923

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

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

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

     

  4. 22 hours ago, TechMac said:

    My workaround: uninstall the app entirely, reboot the system and download from store again. Run

    
    QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

    in the terminal and open Enpass. Reconfigure cloud-access and apply known master-password. Soon the cloud stored date will be loaded. 

    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.

×
×
  • Create New...