Apache HTTP Proxy

[Ali Akbar 0]

Hi,

Currently we are doing ESET POC for one of our client. The ERA server is connected to proxy for access to the internet. After configuring the proxy details in  Servers Setting in ESET Remote Administrator, the ESET Repository able to work and create the all in one installer. We also had set the HTTP Proxy Policy for both product and Agent to the endpoint (ERA IP). Currently the endpoint is not receiving the update from the ERA Server. When we check in Apache HTTP Proxy folder for Cache, it was empty, didn’t store any cache for ESET Update file. My assumption here is the apache is listening to its own IP where by right its must  be configured to client’s own proxy to connect to internet and download the update file. Is there any work around for this problem 

 

ERA Version 6.5
Endpoint : Version 6.6
Windows Server 2012

 

Edited November 3, 2017 by Ali Akbar
additional info

[janoo 11]

Hi, what IP address can you see in the Proxy settings of the Endpoint? (on the client machine)

 

[Ali Akbar 0]

ERA IP address

[Mitsuyuki 0]

A few things you could try is to confirm that the Client machine is able to access the ERA server through the port for the Apache HTTP Proxy (default port 3128), possible confirm using telnet or the following url for your ERA Server hxxp://{eraserverIPaddress or hostname}:3128/index.html . It should display a message stating "it works!".

You may also confirm that the Apache HTTP proxy service is running on the ERA server and confirm server has access to the IP addresses listed in the following article;

hxxps://support.eset.com/kb332/#downloadupdates

Edited November 8, 2017 by Mitsuyuki
Removal of active links

[Ali Akbar 0]

Connection all ok include port 2222,2223 and 3128,Client are connected to the ERA servers

[janoo 11]

Maybe just for the check, do you have any other machine with ESET Endpoint installed in that network which has not proxy policy applied? Does this machine receive updates?