JS Blocker was brilliant, incredibly useful and relatively easy to use. It no longer works with Safari and will not be updated to fit into Apple's requirements. JS Blocker is IMHO the most unfortunate casualty. Unfortunately, not all of Apple's choices in blocked extensions made sense. Apple's goal was to increase Safari security. Safari 12.0 radically changed its extension system. I have sent feedback to the GlimmerBlocker developers.DISCONTINUED. Went from this configuration in GlimmerBlocker (from ): Solution: add exceptions to the PAC for localhost. When using a PAC file proxy bypass exception is, of course, not considered. Long explanation: I use GlimmerBlocker with a PAC as I'm also running LittleSnitch. 1:08:32.336 PM 4-helper: 402002 E findExtensionProcessForPort: | Failed to find extension process for 'safari-extension://4-safari-2bua8c4s2c:52364', my PID: 1687, invalid output: '1687 1:08:32.278 PM 4-helper: 402002 I handleHello: | Welcoming version 4.0.0 of Safari-Extension. Maybe this will help developers, I found it in the system logs: 1:08:32.270 PM 4-helper: 402002 I webSocketForURI: | Extension connected Safari-Extension 'safari-extension://4-safari-2bua8c4s2c / (null)' However, I don't understand why it does not work. So, this shows that GB lets 1Password extension actually establishes a connection to 1Password process. 13:12:12 Sender writes 1029 bytes client->server.
13:12:12 Sender writes 885 bytes client->server. 13:12:12 Sender writes 127 bytes client->server. 13:12:12 Sender writes 277 bytes client->server. 13:12:12 Content-Type: text/plain charset=UTF-8 13:12:12 disables keep-alive: Method = CONNECT 13:12:12 Sender writes 485 bytes client->server. Here is an excerpt from the GlimmerBlocker's log, where Cmd+\ still does not work: 13:12:12 Sender writes 134 bytes client->server. I'm still looking for a way to let 1Password establish a direct connection, but didn't make any progress. I now need to find a way to downgrade to 1Password 3.8.
I can't even explain how much pain this causes me.Īgilebits, please don't ever release something on Thursday or Friday, because you'll leave a lot of your users totally frustrated. Cmd+\ does not work anymore, and logging in is really, really painfull (I need to invoke 1Password through the context menu, anchor it, and copy username/password manually). I must admit, I'm quite disappointed in this release of 1Password, as it completely broke my workflow. Hence, by default 1Password should use the direct connection. T = "function FindProxyForURL(url, host) \n" My pac rule is actually a whitelist for proxy access, like this: gb.ntentType = 'application/x-ns-proxy-autoconfig' However, I don't think there is anything to add in GlimmerBlocker. Thanks, AgileBits, for a great product and great support! :-) Just wanted to share this here so Google can find it, and hopefully help anyone else that's having similar problems. might cause the same problems (and have similar solutions).
Most of the information I found on the web about this problem relates to antivirus/antimalware software causing this problem, and I didn't immediately make the connection that some other network utilities, like Proxifier, Little Snitch, etc. I added a rule to let the 1Password helper process use "No Proxy", and it started working again, just fine.
I checked my logs in Proxifier, and sure enough, it was trying to force the 1Password helper process to go through my corporate proxy (instead of just connecting directly on my local machine, 127.0.0.1). I am behind a corporate firewall/proxy most of the time, and I use a little utility called Proxifier to force some processes that don't obey my system proxy settings to use the proxy (mostly iMessage and some iCloud stuff). I found some threads (including the "Known Issues" thread for 1P4) discussing the fact that Sophos antivirus can cause this issue by blocking network communication between the browser and the 1Password helper process, but I'm not running Sophos or any other antivirus. Neither Cmd+\ nor clicking the icon on the toolbar would fill a saved login or password. I ran into this issue today (and I noticed it in the beta, as well): Once I upgraded my browser extensions to version 4.x (along with 1Password 4 today), they no longer worked.