Use Kerio’s built-in email alerts:
When Kerio Control reports that the Web Filter is not activated and categorization is disabled, the culprit is almost always a licensing gap or a connectivity error preventing the device from reaching the cloud database.
By verifying your license status, ensuring your DNS and WAN connections are stable, and checking the Advanced Options to ensure the service is enabled, you can quickly restore security and filtering to your network environment.
Leo stared at the blinking green cursor on his terminal, the words "Kerio Control: Web Filter not activated. Categorization is disabled." burning like a warning flare.
He was the sysadmin at a small, progressive high school, "The Horizon Academy." The school board had just approved a "responsible digital citizenship" curriculum, which meant Leo was supposed to disable the old, draconian web filter. Their theory: teach kids to self-regulate, not just block them. Leo’s job was to make the network functional but unfiltered.
But the Kerio Control box was ancient, a cranky little server that had been patched, rebooted, and cursed at for five years. When Leo clicked "Save" on the new, filter-less policy, the system didn't just turn off protection—it threw an error. Specifically:
"Kerio Control: Web Filter not activated. Categorization is disabled."
Leo shrugged. That was the goal, right?
He was wrong.
Monday, 8:15 AM
The first wave was innocent. A freshman in Ms. Albright’s history class searched for "Roman Empire engineering." Without categorization, the filter didn't know if this was "Education" or "Weapons." The system defaulted to a limbo state—it let everything through, but it also forgot how to cache or prioritize.
The student’s query hit the main server, then bounced to an ad network, then to a CDN in Moldova, then back. The round trip took 14 seconds. Ms. Albright’s smartboard froze, displaying a spinning wheel of death over a pixelated image of a Roman aqueduct.
Tuesday, 10:20 AM
Mr. Henderson in the library noticed it next. Students researching "endangered species" were being served ads for exotic leather boots. Without content categorization, the traffic shaper had no idea what was payload and what was noise. The school’s 500 Mbps pipe was suddenly acting like DSL.
"Why is YouTube buffering?" a student whined.
"It's not YouTube," Leo muttered, pulling up Kerio’s raw logs. The logs were a screaming kaleidoscope of IP addresses: 45% legitimate school traffic, 55% botnets, cryptominers, and zombie click-farms that had slipped in because no filter was there to blacklist known malicious domains.
Kerio wasn't just a wall; it was a traffic cop. And the cop had gone home. Use Kerio’s built-in email alerts: When Kerio Control
Wednesday, 1:00 PM – The Boiling Point
The new AI-powered grading platform, "GradeSwift," went down. Every teacher in the building lost their progress reports. The cause? Without bandwidth categorization, a single student’s background torrent client (which he thought he’d closed) opened 8,000 concurrent connections to a seedbox in Luxembourg. Kerio, confused, treated the torrent packets with the same priority as the principal’s Zoom call with the district superintendent.
The call dropped. The superintendent was mid-sentence.
Then came the other problem. Since categorization was disabled, the "safe search" enforcement was also off. A seventh-grader innocently searching for "swim team" was shown results that would make a sailor blush. The filter wasn't blocking bad things; it also wasn't blocking inappropriate things that looked like innocent things.
The principal, Dr. Evans, stormed into Leo's office. "Leo. A parent just called. Their child searched for 'how to build a birdhouse' and got a pop-up for… well, for things you build with birdseed, but not that kind."
Leo stared at the Kerio dashboard. The message was still there, mocking him:
"Web Filter not activated. Categorization is disabled."
He finally understood. "Disabled" didn't mean "open and free." It meant "chaotic and blind." The filter’s absence hadn't created a utopia of self-regulation; it had created a digital jungle where nothing worked right, everything was slow, and the worst stuff rose to the top because there was nothing to push it down. Leo stared at the blinking green cursor on
The Fix
That night, Leo didn't turn the filter back on. Instead, he wrote a 17-line script. It didn't enable categorization. It did something smarter. He set Kerio to a "Log-Only" mode with a custom rule: If categorization is disabled, then throttle all un-categorized traffic to 1kbps and route it to a local cache that updates every 10 seconds.
It was a hack, a Frankenstein solution. But when he hit "Apply," the terminal blinked once.
Status: Web Filter – Custom Policy. Categorization – Bypassed. Work – Resume.
The spinning wheels stopped. The principal’s Zoom reconnected. The torrent client was reduced to a sad, slow trickle. And the seventh-grader’s search for "swim team" now just showed photos of a local pool's schedule.
Leo leaned back. The Kerio box hummed quietly. It wasn't fixed. It was working—despite being broken. And sometimes, that’s the best a sysadmin can hope for.
He printed the error message from Monday and taped it to his monitor. It became his motto: "Not activated. Disabled. But it works."
Because in the end, a good admin doesn't need the filter. He just needs the feeling of the filter—and a really clever script. Monday, 8:15 AM The first wave was innocent
SSL/TLS certificates secure the categorization API. If the firewall’s system time is off by more than a few minutes, certificate validation fails, and categorization is automatically disabled.