The appliance must resolve the categorization servers. On the Kerio Control’s diagnostic page (or via SSH/console if enabled), run:
nslookup categorization.gfi.com
Alternatively, use (depending on version):
nslookup mcafee.url.cloud.gfi.com
Correct response: One or more IP addresses.
Failure response: “Server failed” or “NXDOMAIN.”
The Kerio appliance must resolve sessions.gfi.com and licensing.gfi.com. The appliance must resolve the categorization servers
How to test:
Test HTTPS connectivity:
curl -I https://licensing.gfi.com
Use Kerio’s built-in email alerts:
Once you have performed the steps above, verify the system is working:
Introduction: The Frustration of a Broken Filter
For network administrators relying on Kerio Control (now part of GFI Software), few error messages are as confusing and disruptive as seeing your web filter refuse to work. You navigate to the Web Filter section of the admin interface, expecting to see traffic being categorized and blocked according to your policies. Instead, you are greeted by a greyed-out dashboard, inactive rule sets, and the dreaded status indicators: Correct response: One or more IP addresses
This effectively neuters your firewall’s ability to block social media, malware domains, or adult content. Without categorization, your URL rules become useless. This article provides a deep-dive into why this happens and a step-by-step guide to reactivating the filter.
After fixing the issue, back up your configuration immediately: