TinoMontelektro

By the way I think I solved it with reinstalling Eset PROTECT. Some apache http proxy firewall rules did not generate the first time I Installed it.

Thank you for your advices. I will be sure to open a ticket to try and solve this problem.

I am aware of the things you are talking about, but it is not on VA or Linux it is on Windows Server 2019 directly. All-in-one installation.

Apache HTTP proxy is installed and is set as a global proxy to propagate updates and connection to server. Maybe I have wrong configuration or?

So here is the thing. I have Eset Protect (management) through web console on windows server 2019. This ESMC machine is on internet, machines that are connecting to ESET Protect through Agents are not on internet because of security reasons. I am getting "ESET LiveGrid servers can't be reached" and "ESET Push notification servers cannot be reached" warnings for that machines. I presume it is because they are not on internet, even tho I have an http proxy that goes on windows server machine that has internet connection. In linux appliance I can easily remove those two warnings with few commands in terminal (or SSH connection) but when it comes to windows server I am clueless, I tried altering policies, firewall rules and it got me nowhere (maybe I am missing something) . The deal is that this machines will not go on internet so that is not a solution, I tried to disable Eset LiveGrid but that just makes my problem go from warning to security risk. How can I get rid of this two warning and not put my machines directly on internet connection. Advices please.