If you do not see a block page, ensure that the policy with File Inspection enabled is higher in the policy order than other policies the enrolled identities are configured for.

Wait upwards of five minutes before testing again after any policy changes to ensure enough time has passed for the changes to be replicated throughout the Umbrella infrastructure. If problems persist, try clearing the local browser cache on your machine, or even your machine's DNS cache (a reboot will accomplish this).

Beyond that, check to see if you have a local on-prem proxy that is interfering. For more information, see Using Umbrella with an HTTP proxy.

Also, be sure that the Cisco Umbrella root certificate is installed in case of cert errors or files on HTTPS connections not being blocked. For more information, see Manage the Cisco Umbrella Root Certificate.

Contact Support

If you encounter any issues with the File Inspection feature, contact Support.

You may want to include the output of the following commands (these commands should be run from a device enrolled in the policy configured for File Inspection):

dig txt

nslookup -type=txt

You should also include the output of the Umbrella diagnostic to speed up the troubleshooting. See Umbrella Diagnostic Tool.

Test File Inspection < Troubleshooting > File Inspection Reports