Categorization Is Disabled Fixed: Kerio Control Web Filter Is Not Activated

Restart categorization/update service

Some Kerio versions have a hidden reset:

This error means that Kerio Control cannot connect to the cloud-based URL categorization service, or that the local database is corrupted/present. As a result, your firewall falls back to basic filtering or no filtering at all, rendering your security policies useless.

Kerio Control Web Filter is Not Activated: Categorization is Disabled [Fixed] | FQDN | Port | Purpose | |------|------|---------|

Ensure your Kerio Control is using reliable DNS servers (like 8.8.8.8 or 1.1.1.1) under Configuration > DNS . 3. Clear the Web Filter Cache

Ensure the checkbox is checked.

Last updated: October 2025 – Valid for Kerio Control 9.4.x and GFI Kerio Control 10.x. Key Causes of the Error

| FQDN | Port | Purpose | |------|------|---------| | licensing.gfi.com | 443 | License validation | | brightcloud.kerio.com | 443 | URL categorization updates | | ocsp.digicert.com | 80/443 | Certificate revocation (HTTPS inspection) |

typically due to a loss of reliability in the DNS checks to Kerio's update servers or an authorization token expiration support.keriocontrol.gfi.com Immediate Fixes Disable Reliability Detection (SSH Method):

With these details, I can provide a more targeted configuration fix. Share public link When this happens

: Ensure your Kerio Control Web Filter license hasn't expired, as it will automatically disable after 30 days of trial or upon expiration.

However, many administrators encounter a frustrating scenario: the Web Filter shows as or "categorization is disabled" in the Content Filter settings. When this happens, all web filtering rules based on categories cease to function, leaving your network exposed and policies unenforceable.

Ensure that SSL inspection on a parent device isn't interfering with the Kerio appliance's encrypted handshake with GFI/Kerio servers. 5. Correct System Time and Date

This step is a workaround for cases where DNS timeouts cause the system to falsely mark the web filter as unreliable. Instead of fixing the underlying DNS latency issue, it tells Kerio Control to ignore these timeouts.

This issue is typically caused by between Kerio and its categorization provider, Zvelo. Key Causes of the Error