Using ESET Server Security for Linux

Access the Web interface

If the installation is complete, log in to the Web interface at the URL address the installer displayed, along with the login credentials.

The Web interface is available in the following languages:

English

French

Spanish

Spanish (Latin)

German

Japanese

Polish

SSL Certificate


note

ESET Server Security for Linux Web Interface certificate

ESET Server Security for Linux Web console uses a self-signed certificate. Accessing the Web interface for the first time will result in a certificate issue message unless you add a arrow_down_businesscertificate exception.

To use a custom SSL certificate for the Web interface, generate a certificate and import it to ESET Server Security for Linux.

1.Generate an SSL certificate:

openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout privatekey.pem -out certificate.pem

2.Import the SSL certificate to ESET Server Security for Linux:

sudo /opt/eset/efs/sbin/setgui -c certificate.pem -k privatekey.pem -e

Enable the Web interface remotely

If you complete the installation of ESET Server Security for Linux remotely via ESET PROTECT, the Web interface is not enabled.

If you want to access the Web interface on the particular machine, run the following command from a Terminal window:

sudo /opt/eset/efs/sbin/setgui -gre

The final output will show the URL address of the Web interface and the access credentials.

To make the Web interface available at a custom IP address and port, for example, 10.1.184.230:9999, run the following command from a Terminal window:

sudo /opt/eset/efs/sbin/setgui -i 10.1.184.230:9999

 

To enable the Web interface via ESET PROTECT, use the Run Command task to execute the following command:

/opt/eset/efs/sbin/setgui -re --password=<password>

where <password> represents the desired password defined by you.

arrow_down_businessAvailable options for the setgui command

Product activation and initial scan

If you activated your instance of ESET Server Security for Linux, update the detection modules (click Dashboard > Module update > Check and update) and run an initial scan of your file system.