Kerio Control Web Filter Is Not Activated Categorization Is Disabled Fixed Direct
Even with a license, the service may be stopped or hung.
By following these tips and the steps outlined in this article, administrators can ensure that the Kerio Control web filter is working correctly and providing comprehensive protection for their network.
When the Kerio Control Web Filter shows as "not activated" or "categorization is disabled," it is
🚨 Common mistake: Web filter is off in the rule that matches user traffic.
The Kerio Control Web Filter is a premium add-on service powered by Cyren (or GFI, depending on your version). It requires a valid, active subscription. Go to Status > License Details . Even with a license, the service may be stopped or hung
Tip: Try testing the DNS resolution by going to in Kerio Control and pinging ://kerio.com . If it fails, your DNS is the issue. 4. Review Content Filter Rules Ensure the filter is actually enabled in your ruleset. Go to Content Filter .
No categorization data appears in traffic logs.
If the license is active but shows an error, click to force a sync with the GFI/Kerio activation servers. Step 2: Fix DNS and Connectivity Issues
Kerio sends automated check queries to cloud infrastructure. If a response is dropped 10 consecutive times within 1 minute, the firewall marks the backend engine as unreliable and completely disables categorization. The Kerio Control Web Filter is a premium
If Kerio Control detects multiple DNS timeouts (10 failures within 1 minute), it may automatically disable the Web Filter as "unreliable". You can manually disable this safety check via SSH: Log in to the console. Navigate to /opt/kerio/winroute ./tinydbclient "update SiteFilter set DetectReliability=0" Restart the service using /etc/boxinit.d/60winroute restart 3. Verify License and Module Activation
Click the button. This refreshes the relationship with the GFI services. 3. Check DNS Settings (Crucial) Kerio Control requires accurate DNS to reach ://kerio.com . Go to Configuration > Interfaces .
To prevent the Kerio Control web filter not activated issue from occurring in the future, here are some additional tips and best practices:
In the Web Administration interface, go to > License . Tip: Try testing the DNS resolution by going
[Kerio Control Firewall] --(DNS Queries Overload/Blocked)--> [ISP DNS Server] | (Dropped Request) | [Cloud Database (Zvelo)]
Execute the following command to disable detection: ./tinydbclient "update SiteFilter set DetectReliability=0" Restart the service: /etc/boxinit.d/60winroute restart .
If the issue persists, it usually points to a communication problem. Check DNS Forwarding