Technical Tip: The webfilter is not blocking any websites despite having the webfilter licensing with FortiGuard servers connected on FortiGate

[KumarV]

Description	This article describes a given scenario, where the Admin is not able to block any website using Webfilter profile. FortiGate has a reliable connection with FortiGuard servers with full licensing as well. Admin also has Custom-deep-inspection enabled. Under the default profile, the admin has Streaming Media and Download Category disabled, and a URL filter for youtube.com has also been created. Note: In this scenario, no website is getting blocked. YouTube is chosen as an example to give an idea. The picture below shows that Youtube.com is still accessible even after blocking it in the Webfilter security profile. The Screenshot below shows the root cause of the problem. Admin has Custom-deep-Inspection enabled on the policy but HTTPS inspection is disabled. Webfilter security profile checks the URL of the website and takes the appropriate action. Whereas in this scenario HTTPS inspection is disabled so Webfilter does not inspect any website.
Scope	FortiGate.
Solution	After enabling the HTTPS inspection port under the Custom-deep-Inspection profile as shown above, the Webfilter would start inspecting the traffic and hence it is possible to see the block page below. Related Articles : Troubleshooting Tip: Unable to connect to FortiGuard servers Troubleshooting Tip: The webfilter is unable to block an established web connection when switching f...