Bob, I did as you suggested and found that the Web Filtering Live Log seems to "quit" after a short period of time. Filtering does not work at all for some reason. I can type the URL into the Filter box, but the log seems to be outputting whatever it likes in there. Can't see the URL I'm trying to filter in the log's output. Is anyone else having this issue?
If you don't see it in the Web Filtering log at all, it's not being handled by Web Protection. What do you learn from doing #1 in Rulz?
Cheers - Bob
iZamir.Com is my dream project to provide valuable information to the reader in Pakistan like our recent guide about Best Solar AC in Pakistan .
Hi and welcome to the UTM Community!
If you are using Web Filtering in the Transparent mode, it's possible that Chrome and Android phones are accessing the server using UDP 443 instead of TCP 443. You could create a firewall rule like 'Any -> {UDP 443} -> Internet : Drop' to force Chrome to use TCP.
If you are using the Proxy in Standard mode (explicit proxy), you can add UDP 443 to 'Allowed Target Services' on the 'Misc' tab of 'Filtering Options'.
In either case, you must not select 'Do not proxy HTTPS traffic in transparent mode' on the 'HTTPS' tab of the filtering Profile.
You should now be able to block that URL effectively.
Cheers - Bob
Please see the three options listed earlier in this thread.