For further assistance with specific error codes, you can visit the GFI Support Portal Using Kerio Control Web Filter
Go to to check the status of the "Web Filter" module.
If temporary network drops frequently trigger this issue, you can configure Kerio Control via the Secure Shell (SSH) to stop disabling the filter when queries time out. Step 1: Enable SSH on Kerio Control
This error often occurs because the Zvelo key token, which expires every 21 days, has failed to renew. Check DNS Forwarders: For further assistance with specific error codes, you
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
The Kerio Control Web Filter relies on a third-party categorization database, typically from , to analyze and classify web content. For the filter to work, your Kerio Control server must maintain a valid license and be able to reach the licensing and categorization servers. When it fails, the system disables the filter, often logging the messages you see. The error can arise from several common issues:
After completing the steps:
user wants a long article about fixing the "Kerio Control web filter is not activated, categorization is disabled" error. I need to provide a comprehensive troubleshooting guide. I'll follow the search plan provided. search results from the initial plan have provided several promising leads. Result 0 appears to be a support article about resolving web filter categorization issues, result 1 discusses invalid authorization, result 2 covers license activation failures, and result 3 provides information on web filter licensing. I should open these to gather detailed information for the article. article "Resolving Web Filter Invalid authorization failures" provides a clear solution related to DNS settings and Zvelo tokens. "Warning Logs in Kerio Control" shows examples of the error messages. The license activation article explains connectivity and storage issues. The "Kerio Control Licensing Process" outlines optional components like the Web Filter. These are all relevant to the user's query. I should also search for information on how to enable the web filter and possibly about reliability detection. 0 seems to be about disabling reliability detection. This might be part of a workaround. I should open it. article provides a specific fix via SSH commands to disable reliability detection. Now I have a good set of sources covering the error's causes and solutions. I'll structure the article with the following sections: introduction, understanding the error and the importance of licensing, configuring DNS forwarding correctly, setting correct system time and connectivity, addressing token expiration with SSH modifications, disabling reliability detection as a temporary workaround, final checklist for verification, and a conclusion. I will cite the relevant sources throughout. message "Kerio Control web filter is not activated, categorization is disabled" in your logs indicates a breakdown in the web filtering service. This often appears alongside entries like DNS response 'FAILURE: Invalid authorization' to query... . This guide provides a structured, step-by-step approach to diagnosing and resolving the root cause, covering essential areas from basic licensing to advanced command-line fixes.
If Kerio Control is behind another upstream firewall, create an explicit allow rule to those destinations.
Go to Status > System Health and use the Debug or Ping tool (or SSH into the box). Try to ping google.com or ://kerio.com . Check DNS Forwarders: If the license is active
Use a reliable, universal NTP server pool such as pool.ntp.org or ://google.com .
Large time drifts can cause certificate and token failures. Ensure the system time is synchronized. Verify Admin Settings: Navigate to Content Filter Applications and Web Categories
