Cant Block Site

firdhyprayogo Lv1Posted Jun-12-2025 12:17

Hi,
I'm currently dealing with an issue related to blocking specific websites and applications—especially gambling-related content. The blocking works as expected when using Firefox; however, when users access the same content through Chrome, it opens successfully and is categorized under a different protocol like Quic .

I'm using the following methods for access control:
- Keyword filter
- Content filter
- Application and web filter

Is there any way to ensure consistent blocking across all browsers, particularly Chrome?

Thank you in advance.

AimanHakim has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Last edited by AimanHakim Jun-13-2025 04:00.

How about trying to create a new policy dedicated for blocking QUIC? Sometimes when creating 1 policy with multiple protocols to block may have an issue. Try create a policy only with blocking QUIC. At the same time, during the test for surfing the web try empty the cache or using incognito. Cuz maybe previous sessions have not been cut off completely.
If it still doesn't work, u may need to contact sangfor support on this as the QUIC is quite tricky to block in some situations.
Is this answer helpful?
Syed ShahMir Lv1Posted Jun-13-2025 15:05
  
Sure, here's a bit more detail, still brief:

1. **Block QUIC (UDP/443):**
   Chrome uses QUIC (UDP-based) which bypasses normal web filters. Blocking it forces Chrome to use HTTPS over TCP, which your filters can inspect.

2. **Enable SSL Inspection:**
   This allows Sangfor to inspect encrypted HTTPS traffic, ensuring keyword/content filters work properly across all browsers.

With these two steps, website and app blocking will be consistent across Chrome, Firefox, and others.
firdhyprayogo Lv1Posted Jun-12-2025 13:23
  
hi Aiman

I already tried to block the quic protocol on acces control rule to deny all desired connection, but still, it open only on chrome, but when i use edge and firefox it blocked

Screen Shot 2025-06-12 at 12.22.04 PM.png (286.76 KB, Downloads: 74033)

Screen Shot 2025-06-12 at 12.22.04 PM.png
firdhyprayogo Lv1Posted Jun-12-2025 13:16
  
hi Aiman, thanks for the suggest i will try to block Quic protocol
AimanHakim Lv2Posted Jun-12-2025 13:08
  
Hi there, in that case u should apply the QUIC protocol as well for blocking. When blocked, it will fall back using https for web serfing.

I Can Help:

Change

Moderator on This Board

909
182
94

Started Topics

Followers

Follow

Board Leaders