I have been a Eset subscriber since 1.0. My current license has about a year to go and, I am fairly computer literate. I am one of the users who has issues with the HTTP proxy for our and inbound traffic. I have read all the threads and regardless of the recommended configurations to solve the problem. 3.0's Http proxy sidestepping my firewall, Jetico. Yes, I know there are ways to block the outbound port, but it isn't worth the hassle with FF. That is the operative word for me; Hassle. So, I have gone back to 2.7. It looks like eset is going the way of other who did one things well until they tried to do many things well. It doesn't work. Not if you want total control of your internet access. Yes the learning curves for firewalls such as Jetico is steep but well worth it. especially if you are doing any business access over a vpn or financial transactions. May I am getting old, and paranoid but I don't see security reasons Eset running outbound HTTP and HTTPS traffic through Nod32. Inbound maybe for a poorly configured router, firewall and browser. But outbound My router, firewall, and hips have that locked down solid. If I am venturing into areas that may pose a threat on the web. I can turn sandboxie on. Regrettably, Eset seems to feel they have a better way, and a well configured firewall and browser are superfluous with Nod32 3.0 watching over the web traffic. What I would like to see is the ability to simply turn the http proxy off and hand control back to the firewall.