Webfilter categories discrepancies between devices

[IanAce]

Hi,

We have a Fortigate 601E on ver 6.4.13 manged by a FortiManager on ver 7.4.1.

There is a discrepancy between what Webfilter categories are on each device and when I select to block on a category that is not on the Fortigate it gives me the following message:-

post commit check fail: filters - 26 - invalid category id:

Is there any way to manually create this category on the Fortigate? It stops me pushing policy whilst this issue exists.

Thanks.

[abarushka]

Hello,

Could you please clarify whether you are referring to AI and cryptocurrency categories?

https://docs.fortinet.com/document/fortigate/7.4.0/new-features/108890/add-fortiguard-web-filter-cat...

[sarja80]

FortiGate does not have an internal DB, only cache (by default, which lasts for 3600 seconds). The FortiGate queries FortiGuard for every website that is not in its local cache. The only time where FortiGate will differ from FortiGuard is when the FortiGate has made the query and FortiGuard has made a change within the cache timeout period.

[IanAce]

For example, on the Fortigate these are the categories for Potentially Liable:

$ get webfilter categories

g01 Potentially Liable:
1 Drug Abuse
3 Hacking
4 Illegal or Unethical
5 Discrimination
6 Explicit Violence
12 Extremist Groups
59 Proxy Avoidance
62 Plagiarism
83 Child Abuse
g02 Adult/Mature Content:

But on FortiManager we also have:

Crypto Mining
Potentially Unwanted Program
Terrorism

[asrour · Accepted solution]

Hi @IanAce 

FMG 7.4.1 is NOT compatible with FGT 6.4.13 as per the compatibility matrix below

fortimanager-compatibility-5.6.later.pdf (fortinetweb.s3.amazonaws.com)

FMG and FGT should be compatible.

Thank You!

[IanAce]

Thank you for the info asrour. I will arrange for an upgrade of the FGT.