Ive also seen it have issues with Websockets (HTTPS feature). It takes the proxy config from Cisco ASA and then applies it EVERYWHERE which is not correct and causes issues with Safari and Chrome.
To summarize for all who encounter this issue, it is indeed caused by TunnelBear and I am confident that this was not malicious and my computer was not compromised. Ive noticed when using Anyconnect on Mac OS (latest is Sierra 10.12), that Anyconnect sets the proxy configuration wrong.
I read this link from apple Server Admin 10.6 Help: Configuring Web Service Proxy Settings i understand that to set this up i must enable it on my Mac Server and also on.
To save on bandwidth i would like to setup a Mac OS X Snow leopard server with a web caching proxy, forward proxy. You are correct, there was a glitch somehow that left the proxy enabled on my computer, but turning TunnelBear on/off could have fixed it. My office is a Mac environment with a couple of windows pcs. I elevated my support ticket and TunnelBear did confirm that Vigilant mode does setup this proxy to redirect traffic until your connection is secure. I cleared my computer and methodically installed software, and I did confirm that it was TunnelBear! They initially said that is was not TunnelBear.
I originally contacted TunnelBear support suspecting the same thing. I do this by entering the commandexport httpproxy'username:passwordip address:port number'Is there a way to m. This property is the real name of the wireless network that devices connect to. This value is the name that users see when they browse the list of available connections on their device. Given that you also use Tunnelbear and we had similar experiences, I'm satisfied that it is the culprit. For every new session in OS X terminal, I have to make my proxy settings again. Network name: Enter a name for this Wi-Fi connection. And probably a bug with TunnelBear means it didn't get turned off properly at some point. I'm not exactly how either one works, but a local proxy would make sense. thought, "Is my Mac compromised?" My gut told me the culprit was Tunnelbear: either the "TCP override" or "GhostBear" options.
Applications I have used today are Chrome, TunnelBear (which was off at the time) and Parallels to run Windows 7 I stumbled on your post after going through the same process: Had internet connectivity issues, saw my Web Proxy was enabled.