Firefox Extension cannot connect to Helper due to FoxyProxy - whitelist rule solution

nomad55

I've been using 1Password for quite a while now. But my Firefox refuses to connect to 1Password Helper. I've found out it has something to do with FoxyProxy, which prevented the Extension from working. After some digging in this forum I came across serveral ports which are used by 1Password to communicate. I cannot change the Proxy Configuration .pac file directly, but I've found a possible solution to make it work, which I like to share with you.

I've created a new proxy configuration in FoxyProxy which I've called "No proxy for 1Password" there I've created a Whitelist rule with following regular expression pattern in the URL-pattern tab:

^(https?|ws)://(?:[^:@/]+(?::[^@/]+)?@)?(?:localhost|127\.\d+\.\d+\.\d+)\:(?:6258|6263|10191|10196|14821|14826|24861|24866|25007|25012|38151|38156|46360|46365|49801|49806|55730|55735|59483|59488)(?:/.*)?$

This configuration has direct connection to Internet seleted in the proxy detail tab. This rule is now on top of my configuration. Now it works like a charm!

LauraR

@nomad55 - Thanks so much for posting this solution here. I have edited the title of this post so people know that the solution has been posted.

MikeT

We'll also add this helpful tip to our existing KB article on this. Thank you again.

nomad55

Just found some further ports of the v4 browser extension from: https://guides.agilebits.com/1password-windows-kb/4/en/topic/troubleshooting-extensions-win which I should consider and therefore added to my whitelist rule:

^(https?|ws)://(?:[^:@/]+(?::[^@/]+)?@)?(?:localhost|127\.\d+\.\d+\.\d+)\:(?:6258|6263|10191|10196|14821|14826|24861|24866|25007|25012|38151|38156|46360|46365|49801|49806|55730|55735|59483|59488)(?:/.*)?$

seems 1Password sometimes uses a non http schema connecting to the helper. In FoxyProxy-logging I've found a ws:// scheme connecting to the helper... so respected that in the upper rule as well

Hope I've found all ports used ;-) you may update my first post with the new expression above and delete this one, thanks!

MikeT

Hi @nomad55,

We actually use ws:// (websocket) protocol to communicate but https:// is used for the initial handshake process before it switches to the websocket protocol.

I've updated your original post but I'll leave the above post to make sense of this post. :smile:

Thanks again for your help!

koffie

Thanks! Was trying to figure out a regex to match all ports etc, but also missed the "ws://" protocol part... Works like a charm.

LauraR

@koffie - we're so glad this worked for you. Thanks for letting us know.