This error is a critical red flag. It means your content filtering engine is offline. For businesses relying on Kerio Control for productivity, compliance, and security, disabled categorization turns your expensive UTM appliance into a basic NAT router.

Sometimes a simple reboot after changing DNS settings is required to force a new token request. 3. Advanced SSH Fix (Disable Reliability Detection)

Once the underlying network communication pathways are restored, verify your active filtering configuration.

Check → Advanced → Date & Time .

Configure specific to prevent this from happening again. Let me know which step you'd like to try first.

This issue stems from communication failures between your firewall instance and Zvelo , the third-party backend database provider that powers Kerio's cloud-based content categorization engine. Root Causes of the Web Filter Disablement

Kerio Control applies its own rule set to traffic originating from the appliance (e.g., license checks, category updates).

Follow these steps in order to restore functionality.

/etc/init.d/kerio-filtering stop

Walk through if you're unfamiliar with the console. Check your License status within the Kerio interface.

The error typically occurs when the firewall cannot reach the Zvelo categorization servers or when the license token has expired. This is often triggered by DNS failures, where the system marks the filter as "unreliable" after multiple failed connection attempts. Core Troubleshooting Steps 1. Verify DNS and Reachability

Document version: 1.0 – Applicable to Kerio Control 9.x and later.