ESET Online Help

Search English
Select the topic

ESET Bridge advanced configuration

ESET Bridge has a default deny policy for the requests passing through, and only ESET hosts are allowed by default.

Allow a custom ESET PROTECT hostname (or any other custom hostname)

1.Open the restrict.conf.template file in a text editor:

Windows: C:\ProgramData\ESET\Bridge\Proxies\Nginx\Conf\restrict.conf.template

Linux: /var/opt/eset/bridge/nginx/conf/restrict.conf.template

2.Add a regular expression defining the custom ESET PROTECT hostname (the code below is an example):

if ($http_host ~* "^.*\.protect01\.company\.net(:[0-9]+)?(/.*)?$")

{

    set $valid_host 1;

}

3.Save the updated restrict.conf.template file.


warning

Ensure to save the configuration file in the UTF-8 encoding. ESET Bridge cannot process files saved in the UTF-8 with BOM encoding.

4.Restart the ESET Bridge service.

Allow a custom ESET PROTECT port (or any other custom port)

1.Open the nginx.conf.http.server.template file in a text editor:

Windows: C:\ProgramData\ESET\Bridge\Proxies\Nginx\Conf\nginx.conf.http.server.template

Linux: /var/opt/eset/bridge/nginx/conf/nginx.conf.http.server.template

2.Add the custom ESET PROTECT port to the following line:

proxy_connect_allow 443 563 2222 2225 ${ANTISPAM_TARGET_HOST_PORT} ${EPNS_TARGET_HOST_PORT};

3.Save the updated nginx.conf.http.server.template file.


warning

Ensure to save the configuration file in the UTF-8 encoding. ESET Bridge cannot process files saved in the UTF-8 with BOM encoding.

4.Restart the ESET Bridge service.

 


note

Add ESET Inspect Connector support

The ESET Bridge default configuration does not support the ESET Inspect Connector network communication. To add support for ESET Inspect Connector, follow these steps:

1.Allow the ESET Inspect Server hostname—See the steps above for allowing a custom hostname.

2.Allow the ESET Inspect port (8093 by default)—See the steps above for allowing a custom port.