Alexander Keilhofer 0 Posted February 21 Share Posted February 21 Hi, We are using Endpoint Security with WebControl to block certain pages. When the client is connected directly it works just fine. When the client is using a web-proxy (but is able to resolv DNS etc. directly) blocking a https-site works, but the Browser displays "ERR_TUNNEL_CONNECTION_FAILED" Blocking HTTP-Sites works by displaying the configured site. According to this page we are not alone - yet no fix works. Setting "Use Proxy" in Eset does not help either. TL:DR: Blocking HTTPS sites works, but does not display a nice site. Thanks Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,609 Posted February 21 Administrators Share Posted February 21 Can endpoints communicate with ESET's Web Control servers listed in https://support.eset.com/en/kb332 on UDP port 53535? If only communication via the proxy server is possible, an HTTP tunnel to avcloud.e5.sk:53535 must be allowed. Quote Link to comment Share on other sites More sharing options...
Alexander Keilhofer 0 Posted February 21 Author Share Posted February 21 Hi, the client can communicate without any firewall in between. The „block“ works- but the site is not injected. Instead, the connection is just reset. Quote Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 928 Posted February 22 ESET Moderators Share Posted February 22 Hello @Alexander Keilhofer, this is a know issue, ore better said a missing feature so it will have to be implemented on our side. As of now there is no ETA on it, but is is tracked and planned. Once available, the it will be distributed automatically as a module update. Peter(M_PROTOSCN-255) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.