Safari browser extension stopped working

[Ben]

Hi all,

For about a week now, the Safari browser extension stopped working, displaying only a ‘Enpass Connection Error’.

It works fine with the Chrome extension and the taskbar helper.

When doing a tcpdump (sudo tcpdump -i lo0 portrange 10391-10395 -nnn) on the loopback interface I can see traffic from the taskbar helper or the Chrome extension to Enpass. However, I don't even see a connection attempt from the Safari extension.

Here are the relevant open sockets (I am using Dropbox sync, hence the first connection):

% sudo lsof -i -n -P|grep Enpass
Enpass     949        bcollet   29u  IPv6 0x227f399a5755c0cf      0t0  TCP [MY IPV6 GOES THERE]:49721->[2620:100:6022:7::a27d:4207]:443 (ESTABLISHED)
Enpass     949        bcollet   34u  IPv4 0x227f399a5dc33e77      0t0  TCP 127.0.0.1:10391 (LISTEN)
Enpass     949        bcollet   40u  IPv4 0x227f399a5dc32bb7      0t0  TCP 127.0.0.1:10391->127.0.0.1:49484 (ESTABLISHED)
EnpassHel  954        bcollet   11u  IPv4 0x227f399a68114bb7      0t0  TCP 127.0.0.1:49484->127.0.0.1:10391 (ESTABLISHED)

I tried to reinstall the browser extension and Enpass. I restarted (and updated) my Mac. I still have the issue.

In the extension's source code I saw that it's using ‘localhost’ to contact Enpass, and as Enpass is only listening in IPv4 I tried to comment the IPv6 localhost entry in my ‘/etc/hosts’ file, to no avail (it should fall back to IPv4 anyway, but I am starting to consider sacrificing chickens and drawing pentacles on the floor).

Here are the versions I am using:

•   Safari Version 11.0.3 (13604.5.6), then updated to 11.1 (13605.1.33.1.2)
•   Browser Extension 5.5.2
•   Enpass 5.6.3 (138)
•   macOS High Sierra 10.13.3 (17D102), then updated to 10.13.4 (17E199)

Any help is appreciated,

Cheers!

Edited April 2, 2018 by Ben

[Anshu kumar]

Hi @Ben 

Sorry for the trouble you are going through. Please try clearing the cache and cookies from Safari browser, if you haven't tried that yet. If the problem still persists please drop us an email support@enpass.io mentioning this link so that we can share a debug tool and investigate where the problem could be.

Thanks for your co-operation.

[OliG]

On 3/31/2018 at 1:13 PM, Ben said:

Hi all,

For about a week now, the Safari browser extension stopped working, displaying only a ‘Enpass Connection Error’.

It works fine with the Chrome extension and the taskbar helper.

When doing a tcpdump (sudo tcpdump -i lo0 portrange 10391-10395 -nnn) on the loopback interface I can see traffic from the taskbar helper or the Chrome extension to Enpass. However, I don't even see a connection attempt from the Safari extension.

Here are the relevant open sockets (I am using Dropbox sync, hence the first connection):

% sudo lsof -i -n -P|grep Enpass
Enpass     949        bcollet   29u  IPv6 0x227f399a5755c0cf      0t0  TCP [MY IPV6 GOES THERE]:49721->[2620:100:6022:7::a27d:4207]:443 (ESTABLISHED)
Enpass     949        bcollet   34u  IPv4 0x227f399a5dc33e77      0t0  TCP 127.0.0.1:10391 (LISTEN)
Enpass     949        bcollet   40u  IPv4 0x227f399a5dc32bb7      0t0  TCP 127.0.0.1:10391->127.0.0.1:49484 (ESTABLISHED)
EnpassHel  954        bcollet   11u  IPv4 0x227f399a68114bb7      0t0  TCP 127.0.0.1:49484->127.0.0.1:10391 (ESTABLISHED)

I tried to reinstall the browser extension and Enpass. I restarted (and updated) my Mac. I still have the issue.

In the extension's source code I saw that it's using ‘localhost’ to contact Enpass, and as Enpass is only listening in IPv4 I tried to comment the IPv6 localhost entry in my ‘/etc/hosts’ file, to no avail (it should fall back to IPv4 anyway, but I am starting to consider sacrificing chickens and drawing pentacles on the floor).

 Here are the versions I am using:

•   Safari Version 11.0.3 (13604.5.6), then updated to 11.1 (13605.1.33.1.2)
•   Browser Extension 5.5.2
•   Enpass 5.6.3 (138)
•   macOS High Sierra 10.13.3 (17D102), then updated to 10.13.4 (17E199)

Any help is appreciated,

Cheers!

Hey Ben! 
I have experienced the same issue and actually, I was just able to solve it...

My situation: Enpass Safari Extension Connection Error

• I had a 2015 MacBook Pro running with macOS High Sierra. Enpass used to work fine with all browsers (Safari, Firefox, Chrome)
• A couple of weeks ago I switched to a 2017 MacBook Pro via Migration Assistant. On my new MBP, Enpass still worked with Firefox and Chrome, but did not work with Safari!
  Always displayed this dumb connection error...

Now here's what I did:

• Uninstall and re-install Enpass for macOS (tried both the App-Store and the Enpass-Website versions)
• Uninstall and re-install Enpass Safari Extension (tried both the Safari Extensions Gallery and the Enpass Website versions)
• Install Enpass for macOS and Enpass Safari Extension DEBUG versions sent to me from Enpass support

And all of this didn't change a thing!

Here's what solved my issue:

After reinstalling Enpass and the respective safari extension about a million times, I decided to re-install macOS without erasing my data.
A reinstallation of macOS is the only way to re-install Safari.

How I did this:

• Make a Time Machine backup to an external HDD or NAS. 
• Go to Mac App Store, search for High Sierra and download it (around 5 GB)
• When the download is finished, the High Sierra Installer pops up
• Simply re-install macOS this way (this does not affect your data!) 
  -> and then be happy things are working well again!

And - voilà - this solved the problem for me.

Now everything is working well!

Good luck,
Oliver

 

[Ben]

Hi all,

Sorry for the late reply. I was able to solve my problem.

The issue was caused by HSTS. I sometimes use ssh tunnels to connect to management interfaces of devices behind a bastion host. One of theses devices is using HSTS and from that point every connexion to localhost required an HTTPS certificate.

Safari extensions connecting to localhost honour HSTS policies, so the connection to Enpass from the browser extension was not possible anymore.

To solve it, I had to completely close Safari (and kill all process related to Safari in the Activity Monitor) and delete the following file: ~/Library/Cookies/HSTS.plist.

Cheers,

Benjamin