There are three primary reasons why this status appears:
The error "Kerio Control web filter is not activated – categorization is disabled" is almost never a hardware failure. In 99% of cases, it is a licensing, DNS, or system clock issue.
Quick Recap Checklist:
By following this guide, you should see the Web Filter dashboard return to life, categories populating, and your URL rules enforcing correctly. If the problem persists, contact GFI Support with the log file located at /var/log/kerio/web-filter/error.log – it will contain specific HTTP error codes explaining why the cloud categorization handshake is failing.
Remember: A web filter without categorization is like a guard dog without teeth. Fix it immediately to maintain your network’s security and productivity policy. There are three primary reasons why this status appears:
SSL/TLS certificates secure the categorization API. If the firewall’s system time is off by more than a few minutes, certificate validation fails, and categorization is automatically disabled.
By [Your Name/Tech Team]
One of the most powerful features of Kerio Control is its ability to filter web content, blocking malicious sites and restricting categories like gambling, adult content, or social media. However, administrators occasionally encounter a frustrating scenario: the Web Filter status displays "Not Activated" or warns that "Categorization is Disabled."
When this happens, your firewall rules relying on URL categories cease to function, leaving the network vulnerable or unfiltered. The error "Kerio Control web filter is not
This article explores the root causes of this error and provides a step-by-step guide to getting your web categorization back online.