Skip to main content
DeepakTiwari
New Member
April 14, 2024
Question

Unable to Block Artificial Intelligence Category

  • April 14, 2024
  • 4 replies
  • 2800 views

Hi Team,

 

We are wanting to Block Artificial Intelligence Category in our Webfilters but every time we mark this Category as blocked and save webfilter and again open this so that category always mark as Allow, This is a some king of bug in Webfilter.

Product :- FortiGate 60F

Version :- v7.2.8 Build 1639(Mature).

 

Pls help us to get rid of this bug.

4 replies

AEK
SuperUser
SuperUser
April 14, 2024

Hi @DeepakTiwari 

Does it work with CLI?

config webfilter profile     edit "webfilter"         config ftgd-wf             config filters                 edit 100                     set category 100                     set action block                     next             end         end     next end

 

AEK
shivashankar2k9
New Member
August 13, 2024

Tried the cli command and it worked. 
add correct web filter profile here or else it will create new web filter profile with that name 

config webfilter profile     edit "webfilter" --> update these with exact web filter profile name         config ftgd-wf             config filters                 edit 100                     set category 100                     set action block                     next             end         end     next end

 

hbac
Staff
Staff
April 15, 2024

Hi @DeepakTiwari,

 

I'm not able to replicate the issue in my lab. There might be some other trigger conditions in your configuration. I suggesting opening a ticket with Fortinet TAC and share your configuration in the ticket. 

 

Regards, 

mpatel
Staff
Staff
April 15, 2024

@DeepakTiwari 

 

Try running the CLI debugs as mentioned in the below KB article and then attempt to make the change in the webfilter. Upload the cli debugs logs to further look into what could potentially be causing this issues.

 

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Verify-configuration-in-CLI/ta-p/196389

 

shivashankar2k9
New Member
July 16, 2024

Facing similar issue on same fortigate version.
@DeepakTiwari is the issue resolved for you and what is the solution