Configuring DPX for Automatic Blocklist Updates

Important. This chapter details changes for the DPX Master Server configuration, not GuardMode. These modifications are essential for enabling the Master Server to download the blocklist from our server.

Follow these instructions to configure automatic blocklist updates for GuardMode in your DPX Master Server.

Prerequisites

Before you begin, ensure you have the following:

• Access to your DPX Master Server via SSH.

• Superuser privileges.

Configuring Automatic Blocklist Updates

1. Log in to your DPX Master Server via SSH, using:

ssh your_username@your_dpx_instance_ip

1. Enable superuser privileges

2. Navigate to the Services Directory, using:

cd /catalogic/services

1. Edit the dpx.yml Docker Compose file to configure automatic blocklist updates.

In the dpx.yml file, locate the section catalog → environment. Add or modify the following environment variables to enable automatic blocklist updates:

• Blocklist Network Fetch Enabled: Determines if the blocklist will be downloaded from the internet. Default: false.

• Blocklist Network URL: The URL for the blocklist download. Default: https://catalogic-mysupport.s3.us-west-002.backblazeb2.com/security-updates/block-list-latest.json.

• Blocklist Network Fetch Interval (milliseconds): The frequency of blocklist updates. Default: 43200000 (12 hours).

Example configuration:

catalog:
  environment:
    BLOCKLIST_NETWORK_FETCH_ENABLED: true
    BLOCKLIST_NETWORK_URL: https://catalogic-mysupport.s3.us-west-002.backblazeb2.com/security-updates/block-list-latest.json
    BLOCKLIST_NETWORK_FETCH_INTERVAL_MILLISECONDS: 10000

Tip. If you encounter any issues while editing the dpx.yml file, ensure that the syntax is correct and all environment variables are properly indented.

1. Save the changes to the dpx.yml file and exit the text editor.

2. Restart the DPX services to apply the new configuration.

systemctl restart dpx-swarm

Attention! Restarting the DPX services will temporarily disrupt any ongoing operations. Plan this change during a maintenance window to avoid impacting users.

1. Once the services are running again (this may take a few minutes), check the Events section in the DPX Master Server web interface to verify that the blocklist has been downloaded.