Troubleshooting Tip: Video Filter Debugging Commands

[Renante_Era]

Description	This article describes how to debug the Video Filter when a YouTube filter is not working correctly.
Scope	FortiProxy, FortiGate, v7.0.x and v7.2+.
Solution	Double-check the Technical Tip: Blocking internet traffic but allowing access to specific YouTube Channel through Vid.... Ensure that traffic matched the expected firewall policy. diagnose sys session filter cl diagnose sys session filter src <IP address> diagnose sys session list | grep policy_id Make sure that the API key is configured correctly. show full | grep -f <API key> Double-check the channel ID as well. show full | grep -f <channel_ID> Clear the browser cache and reload the video.  Confirm block/allow YouTube videos/channels using web filter event logs (FortiGate GUI -> Log & Report -> Security Events -> Web Filter Events). The following images represent an allowed and blocked video web filter log, respectively:      7. Additional debug commands can be collected using the following FortiGate CLI commands: Before starting, make sure that the WAD filter is not configured with other parameters:  diagnose wad filter list  drop unknown sessions: disabled  diagnose debug console timestamp enable   diagnose wad filter src x.x.x.x               <----- Source IP of the client. diagnose wad debug enable level verbose diagnose wad debug enable category video diagnose wad filter list  diagnose wad debug show  diagnose debug enable Stop the debugging after generating traffic to YouTube: diagnose debug disable  diagnose debug reset