Kerio Control Web Filter Is Not Activated Categorization Is Disabled Fixed =link=

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.

If the issue persists, it usually points to a communication problem. Check DNS Forwarding

The filter uses a token that expires every 21 days. If your system time is incorrect or you are using blocked DNS servers, the "Invalid Authorization" error may trigger. Ensure your is synced with an NTP server. Check the Error Log for "Invalid Authorization" messages. Manual Activation

To fix the issue where the Kerio Control web filter is not activated and categorization is disabled: Kerio sends automated check queries to cloud infrastructure

: Use a client like PuTTY to SSH into your Kerio Control appliance. Execute the Fix :

section to ensure your license is valid and that the "Web Filter" module is included. If you have recently renewed, you may need to download the license file and register it again. support.keriocontrol.gfi.com Do you need the specific SSH commands

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. Check DNS Forwarding The filter uses a token

If the above steps fail, you may encounter an expired Zvelo authorization token, which the system cannot renew automatically. This requires manual intervention via the command line.

Add the URL *.zvelo.com and point it to a reliable DNS provider like ( 1.1.1.1 ) or OpenDNS ( 208.67.222.222 ). Reboot the Kerio Control appliance to apply changes. B. Disable Reliability Detection via SSH

By following these steps and ensuring that your Kerio Control software is correctly configured, you should be able to resolve the issue of the web filter not being activated and categorization being disabled. Check the Error Log for "Invalid Authorization" messages

The most effective way to force the filter back into an "Activated" state is through the SSH console. This prevents the system from automatically disabling the filter when it encounters a brief connection hiccup.

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 .

cd /opt/kerio/winroute ./tinydbclient "update SiteFilter set DetectReliability=0" /etc/boxinit.d/60winroute restart Use code with caution. Copied to clipboard

Now that we have explored the causes and symptoms of the issue, let's move on to the step-by-step guide to fix it: