| Preventive Measure | Why | |--------------------|-----| | Set up monitoring alerts | Receive email notification if categorization stops. | | Regularly check license expiry | Add a calendar reminder 30 days before renewal. | | Use redundant DNS servers | Prevents single-point-of-failure resolution issues. | | Document upstream proxy changes | Any proxy change requires updating Kerio. | | Test after updates | Category servers change IPs; test every quarter. | Q1: Can I use Kerio Control without cloud categorization? Yes, but only with static URL lists, IP-based rules, or by disabling web filtering entirely. Dynamic filtering will not work.
This article explains why this message appears, the seven most common causes, and step-by-step solutions to restore full web filtering functionality. To understand the error, you must first know how Kerio Control’s web filter works. | Preventive Measure | Why | |--------------------|-----| |
Indirectly. HTTPS filtering (SSL inspection) is separate. However, if categorization is disabled, you cannot block HTTPS sites based on category, even if SSL inspection is on. | | Document upstream proxy changes | Any
Remember: Cloud categorization requires the firewall itself to act as a client. Treat it like any other workstation that needs DNS, NTP, and outbound HTTPS access. With proper monitoring and preventative maintenance, you can ensure that “categorization disabled” becomes a rare event rather than a recurring headache. Visit the official Kerio Control Knowledge Base or the GFI Community Forums. Always include your debug logs (Diagnostics → Generate Support Info) when seeking vendor support. Last updated: 2025 Revision: 4.0 Yes, but only with static URL lists, IP-based
No. The free version (limited to 5 users) does not include cloud categorization. Web filtering will always show as disabled. Conclusion The message “Kerio Control web filter is not activated – categorization is disabled” is not a minor glitch—it signals that category-based content filtering is completely offline. Most often, the culprit is an expired license, DNS failure, or an outbound firewall rule blocking the appliance’s own traffic.
Usually 1–5 minutes. Restart the firewall engine for immediate effect.
Go to or Web Filter → Upstream Proxy (version dependent).