Join our Telegram channel for updates, announcements, and community support:

Kerio Updates Mirror is a solution for local caching and mirroring of updates for Kerio Control and Kerio Connect products, which allows you to:

• Reduce internet traffic and speed up the update process
• Provide updates for isolated networks or systems with limited internet access
• Automatically download and update antivirus databases, IPS/IDS Snort databases, and other security components

• Docker and Docker Compose (installation guide)

Please note: the Docker image version may differ from the mirror version - this is normal. The image is only updated when necessary (for example, when dependencies change) and is not synchronised with each version of a mirror.
If you install a mirror in any other way, the version of Docker's image will be the same as the current one.

1. Download Docker images
2. Load images from archives:

   sudo docker load -i tor_v1.1.2.tar
   sudo docker load -i mirror_v2.1.0.tar

3. Download or clone the repository:

   git clone https://github.com/cnekTep/kerio-updates-mirror.git
   cd kerio-updates-mirror

4. Make necessary configurations
5. Start the containers:

   sudo docker-compose up -d

1. Download or clone the repository:

   git clone https://github.com/cnekTep/kerio-updates-mirror.git
   cd kerio-updates-mirror

2. Make necessary configurations
3. Start building and deploying containers:

   sudo docker-compose up -d

This option provides a fully configured out-of-the-box solution, ideal for quick deployment.

1. Download the Virtual Machine
2. Import the image into your virtualization system (Hyper-V, VMWare - OVF Template)
3. Start the virtual machine

If you don't want to use Docker, you can run Kerio Updates Mirror without it. To do this, you will need to manually install all the dependencies and configure the system. However, it can be more difficult and take more time. It is recommended to use Docker to simplify the installation and management process.

1. There is no built-in TOR support
2. There is no built-in proxy server
3. Difficulties with activating Kerio Connect antispam (for more information, see Configuring Kerio Connect antispam)

cd "path_to_nssm_folder"
nssm install kerio-updates-mirror

net start kerio-updates-mirror

nssm remove kerio-updates-mirror confirm

To configure updates through the local mirror in Kerio Connect, you need to specify an HTTP proxy server in the settings:

To configure updates through the local mirror in Kerio Control, you need to add DNS records:

n the non-Docker version, for Kerio Control and Kerio Connect updates to work correctly, you must manually specify the local mirror address for the respective hosts (see the table above).

• For Kerio Connect, you can configure the DNS server so that it resolves the specified domains via Kerio Control. This can be done by specifying the IP address of the server with the mirror in the DNS settings.
• Alternatively, you can add the necessary domain matches and mirror IP addresses to the hosts file on the server with Kerio Connect.

This will ensure that update requests are redirected to your local mirror.

There are two options for configuring antispam:

1. Via VPN (recommended):

   • Direct traffic to the following hosts via VPN:

     upgrade-please-change-me.cdn.bitdefender.net
     patches-please-change-me.cdn.bitdefender.net
     nimbus.bitdefender.net

   • In this case, both antivirus and antispam will work.

2. Through an external proxy:

   • Temporarily configure Kerio Connect to work via an external proxy server
   • Wait for antispam activation
   • Disable the proxy
   • After that, both components will work: antivirus and antispam

Note: When using a proxy, the antivirus will temporarily stop working, but it will recover after disabling the proxy.
Antispam will work until the server is restarted.

• For Kerio Connect:

  • Automatic downloading of antivirus databases when accessing the mirror
  • Support for anti-spam functionality

• For Kerio Control:

  • Automatic downloading of antivirus databases when accessing the mirror
  • Scheduled updates for:
    • IPS/IDS Snort databases
    • GeoIP databases
    • Lists of compromised addresses
  • Ability to retrieve GeoIP databases from external sources on the GitHub platform

TOR bridges are used to ensure reliable access to updates even in case of access restrictions:

• TOR bridges configuration file: _tor/config/bridges.config
• When the USE_CHECK_TOR=true parameter is enabled in docker-compose.yml, the system automatically checks internet accessibility through TOR and updates bridges if necessary
• New bridges can be obtained from the official website or via Telegram bot

The default time zone is UTC

• The time zone can be changed in the .env file
• After changing the time zone, you need to rebuild the container using the docker compose up -d command

• Access to the web management interface, depending on the settings in docker-compose.yml:
  • Only port 9980 is published and only Kerio Connect is updated: http://SERVER_IP:9980
  • Ports 80, 443 are published and Kerio Control is updated: http://SERVER_IP:80