ESET Online Help

Search English
Select the category
Select the topic

Offline Repository—Linux

You can use the Mirror Tool to create an offline repository on Linux (Are you a Windows user?) when using closed computer networks or networks with limited internet access. You can use the Mirror Tool to create a clone of the ESET repository in a local folder. This cloned repository can be moved (for example, onto an external disk) to a location in the closed network. You can copy the repository to a secure location in the local network and make it available via an HTTP server (for example, ESET Bridge).

To update the offline repository, run the same command with the same parameters as used for offline repository creation. Previous data in the intermediary folder will be used, and only outdated files will be downloaded.


Be aware that the size of the repository is growing, and the intermediary directory will be the same size. Ensure you have at least 1.2 TB of free space before starting this procedure.

Best practices

See also the ESET Knowledgebase article Best practices for using the ESET PROTECT On-Prem in an offline environment.

Example scenario for Linux

I. Create repository clone

1.Download the Mirror Tool.

2.Extract the Mirror Tool from the downloaded .zip file.

3.Prepare (create) folders for:

intermediary files

final repository

4.Open the Terminal in the folder with the MirrorTool file and make the file executable:

chmod +x MirrorTool

5.Run the following command (change the intermediary and output repository directories to the folders from step 3):

./MirrorTool --repositoryServer AUTOSELECT ^
--intermediateRepositoryDirectory ~/Documents/Intermediary ^
--outputRepositoryDirectory ~/Documents/Repository

6.After the repository is copied to the outputRepositoryDirectory folder, move the folder and its contents to another machine where your closed network is accessible.

II. Set up the HTTP server

1.You need an HTTP server running on the machine in the closed network. You can use:

ESET Bridge proxy from the ESET download site (this scenario)

a different HTTP server

2.Install ESET Bridge proxy.

III. Run the offline repository

1.Navigate to /opt/eset/bridge/etc and open the pkgid file using a simple text editor. Change the http_proxy_settings_static_content_enabled setting to true to activate the offline repository server. Save the changes and close the pkgid file.

2.Copy the downloaded repository from step 6 (section I. above) to the offline repository server directory:

The default offline repository server directory is /var/opt/eset/bridge/OfflineRepository with proper access rights.

To use a custom directory, create a new folder for the offline repository (for example, /var/opt/CustomOfflineRepository). In the pkgid file, replace the line "http_proxy_settings_offline_repository_dirPath": "%DATADIR%\\OfflineRepository" with "http_proxy_settings_offline_repository_dirPath": "/var/opt/CustomOfflineRepository".

oThe eset-bridge user needs full access rights to the directory. Use this Terminal command to grant the access rights: sudo chown -R eset-bridge:eset-bridge /var/opt/CustomOfflineRepository

oCopy the downloaded repository into /var/opt/CustomOfflineRepository.

3.Restart the ESET Bridge service using the Terminal command: sudo systemctl restart EsetBridge.service. You must restart the service only after changing the pkgid file—the service restart is unnecessary when the repository data is changed, deleted, or added.

4.The offline repository runs on the address http://YourIPaddress:4449 (for example,

5.Set the new repository address using the ESET PROTECT Web Console:

a.ESET PROTECT Server—Click More > Settings > Advanced Settings > Repository and type the offline repository address into the Server field.

b.ESET Management Agents—Click Policies, click the Agent policy > Edit > Settings > Advanced Settings > Repository > type the offline repository address into the Server field.

c.ESET endpoint products (for Windows)—Click Policies, click the ESET Endpoint for Windows policy > Edit > Settings > Update > Profiles > Updates > Product Updates > type the offline repository address into the Custom server field.