Chrome Extension won´t work

Sral

Hi there,

I'm using 1Password 5 Version 5.3.1 (531001). 1Password Mini is running and I installed the 1Password Chrome Extension. I'm running Chrome Version 42.0.2311.135 (64-bit).

When I click on the 1Password extension button in Chrome a new tab opens withe the text "Looking for the 1Password app". After a few seconds 1Password mini opens a small window: "1Password Mini startet" an something about that I have to keep it open in order for the Extension to work.

But then there're two buttons in the Chrome tab: "Try again" and "Get the app!". But Try again isn't working.

Any ideas?

Lars

littlebobbytables

Hi @Sral,

Can I ask, are you running any third party firewalls, anti-virus or parental controls on your computers? The extension talks to 1Password mini via a web socket and if anything blocks this channel then the two can't see each other. Firewalls and anti-virus programs are usually the prime cause but a VPN or proxy server which doesn't ignore 127.0.0.1 AKA localhost can also interfere.

Is it possible you have anything like that? Once we have a better idea we can hopefully supply more specific steps :smile:

Sral

Hey @littlebobbytables,

thank you for your reply.

The problem actually was a proxy server i added lately. But i still wonder why this proxy caused this problem, because I explicitly added "localhost" as an exception.

But anyway, thanks again for your help.

Lars

littlebobbytables

Hi @Sral,

• What kind of proxy was it?
• Could it be worth trying 127.0.0.1 & localhost as entries?

If you're wondering about the first question it's because I remember what a very nice user reported to us and it was in reference to WPAD settings, it turns out that depending on how the proxy is set up the exceptions may need to be added to the proxies configuration server-side rather than client-side.

I don't know if that makes any difference at all.

zwing99

I fought the same thing with a corporate proxy. I had to add exceptions for localhost and 127.0.0.1 on my mac.
But seemed to work after that!

Drew_AG

@zwing99, thanks for confirming that worked for you! Hopefully it all continues to work well for you, but if you run into more problems, just let us know - we're here for you. :)