How to enable Apache HTTP Proxy on my ERA Virtual Appliance after initial configuration

Open terminal and according to your OS version run the following commands as root to enable Apache HTTP Proxy:


The location of apachectl and htcacheclean will vary based on your system, check it before running the script.

The parameter /var/cache/apache2 determines the location of the caching folder, this location is set in /etc/httpd/conf.d/proxy.conf under CacheRoot.

Apache HTTP Proxy replaces the Mirror Tool functionality from ESET Remote Administrator 5.x. It is primary used for caching detection engine update files and caching information from ESET Live Grid®.

For CentOS 6

1. echo /opt/apache/bin/apachectl start >> /root/

2. echo /opt/apache/bin/htcacheclean -d60 -i -p/var/cache/apache2 -l10000000000 >> /root/

3. iptables -A INPUT -p tcp --dport 3128 –j ACCEPT

4. ip6tables -A INPUT -p tcp --dport 3128 –j ACCEPT

5. service iptables save

6. service ip6tables save

7. chmod +x /root/

8. /root/

For CentOS 7

1.systemctl enable httpd

2.sudo mkdir -p /etc/systemd/system/httpd.service.requires

3.sudo ln -s /usr/lib/systemd/system/htcacheclean.service /etc/systemd/system/httpd.service.requires

4.systemctl start httpd

5.htcacheclean -d60 -t -i -p/var/cache/apache2 -l5000M


You can adjust parameters for Apache HTTP Proxy cache cleaning: -d defines cleaning interval in minutes, -p specifies path as the root directory of the disk cache, -t deletes all empty directories, -i intelligently deletes cache only when there was a modification of the disk cache, -l defines total disk cache size limit.

6.iptables -A INPUT -p tcp --dport 3128 -j ACCEPT

7.ip6tables -A INPUT -p tcp --dport 3128 -j ACCEPT

8.service iptables save 

9.service ip6tables save

This will start Apache HTTP Proxy and enable port 3128 in an firewall. You will need to create policies for all ESET products / ERA components to communicate via Apache HTTP Proxy and allow the caching of installation files / update files for ESET products. For more information see our Knowledgebase article part II. Configure policy settings for client computers.