Do you see any specific errors in the or Warning Log modules?
The categorization token expires every . If Kerio cannot reach internal update servers to refresh it, authorization fails.
Understanding the root cause helps you select the correct troubleshooting path. This issue typically stems from four specific areas:
In the world of network management, few things are as frustrating as seeing a "Not Activated" status on a tool you rely on. Here is the story of how the Kerio Control Web Filter's categorization issue—a common headache for admins—is typically diagnosed and fixed. The Situation Everything seems fine until the administrator logs into the Kerio Control Webadmin and sees a warning: Do you see any specific errors in the or Warning Log modules
Kerio downloads a local copy of the categorization database. If that database is outdated or corrupt, forcing a fresh download helps.
The Kerio Control Web Filter is an essential component for network security, providing dynamic, real-time URL categorization and classification. It ensures that users cannot access dangerous, inappropriate, or unproductive content by blocking traffic based on web page classification. However, a common issue reported by administrators is the error or "Categorization is disabled," resulting in open internet access and potential security vulnerabilities .
This comprehensive guide explains why this error occurs and provides step-by-step solutions to fix it and restore your web filtering capabilities. Understanding the Error Understanding the root cause helps you select the
This issue is typically caused by between Kerio and its categorization provider, Zvelo. Key Causes of the Error
The rule should look like: Source: Firewall -> Destination: Internet -> Service: Any (or HTTP/HTTPS/DNS) -> Action: Allow .
Click or Update License Info to force the firewall to re-authenticate with the parent servers. Step 2: Check Kerio Control's System DNS Settings The Situation Everything seems fine until the administrator
A disabled Kerio Control Web Filter can lead to significant network security risks. In most scenarios, the "not activated" error is caused by DNS resolution failures or transient connectivity issues with the Zvelo classification database. By verifying your license, updating your DNS servers, and potentially disabling the DetectReliability feature, you can restore full web filtering functionality.
Run this to see if categorization is alive:
If the error persists even after all eight fixes, contact GFI Support and attach the file from /var/log/kerio/control/ or categorization folder. Provide them with:
Without categorization, the firewall was blind. Employees could wander into the darkest corners of the internet, and Mark’s beautifully crafted security policies were nothing more than suggestions. The Investigation
Connect to your firewall appliance using an SSH client (like PuTTY).