UTM SG210 Web Filtering not Working with Chrome

Hi,
Chrome browsers are also filtered in my environments like other browsers.
But Google implements some "privacy optimizations". (like Apple his privacy proxy)
Here the DNS requests or the complete web requests use a tunnel (VPN) .
So your firewall can't see anything.
Here, the “quick protocol” is usually used.
You can try blocking  “quick protocol” within your rules.
.... but maybe there is something new ... from the "security sheriff google"

Thanks for your help. I blocked QUCIK by blocking UDP 443 and 80 via firewall rule. But the problem still exists.

So sadly this wasn't (the only) solution.

Hello Erik,

did you try to set the client's proxy settings manually? Just for testing purposes...

Hello Philipp, thanks for your answer. Yes i already tried that. Is there any possibility to check whether chrome is indeed using the proxy? The "Web Filtering" live log doesn't show any traffic caused by chrome.

Hello Erik,

what's the mode you are using with your webfilter?

There are three modes available: standard, transparent and full-transparent. The latter is only usable in bridged mode and I assume that you don't use a bridge, do you?

So the only relevant modes are standard and transparent.

It is standard mode.

Did you change the standard proxy port?

Proxy port is 8080.

Hallo Erik,

Show us a screencap of 'Misc Settings' on the 'Misc' tab of 'Filtering Options'.  Note #2 in Rulz.

Cheers - Bob

Hello Bob, thanks for your answer.

Here is the screenshot.

Regarding to Rule #2 i can't see how the traffic of the chrome browser could be allowed by one of the points before 7. But i will have a closer look, thanks for the hint.

Erik, two days ago, you said, "I blocked QUCIK by blocking UDP 443 and 80 via firewall rule. But the problem still exists."

If one of your 'Allowed Target Services' is UDP 443, then Web Filtering allows that traffic before it can be blocked by a firewall rule.

Cheers - Bob

Erik, two days ago, you said, "I blocked QUCIK by blocking UDP 443 and 80 via firewall rule. But the problem still exists."

If one of your 'Allowed Target Services' is UDP 443, then Web Filtering allows that traffic before it can be blocked by a firewall rule.

Cheers - Bob

I removed the 443 and 80 Services from "Allowed Target Services" temporarily. But Chrome can't still be blocked. I added a Screenshot of the firewall rule. I only use three workstations for testing.

Erik, please insert a picture of the Edit of the 'QUICK 443' Service definition.

Cheers - Bob

I think about switching from standard to transparent mode.

Could this circumvent the problem?

Yes, but this indicates that 'QUICK 443' hasn't been removed from 'Allowed Target Services'.  See #2 in Rulz.

Cheers - Bob