Skip to main content
olop
olop
New Member
July 25, 2018
Question

Block Youtube on Google Chrome not work

  • July 25, 2018
  • 3 replies
  • 12419 views
Hi All,   I have a fortigate 800D, firmware v6.0.1. I want to block youtube. I try to block with application control, and QUIC i set "Block". Blocking youtube is working on IE and Firefox. But on Chrome is not working. Can anyone help me for this problem?

3 replies

sdybelgium
sdybelgium
New Member
September 5, 2018

Hi,

 

Did you solve the problem.

we have the same problem here.

It worked for years and now it doesnt.

It even doesnt log the youtube usage.

I added a application block and when im in IE it blocks and logs the attempt.

When im in chrome it just doesnt block and doesnt log the usage.

 

Regards,

 

David

copycon
copycon
New Member
December 20, 2018

I have the same problem, I saw in the log (client access youtube by Ios App and the block_youtube rule catched the flows but the action is allow..... (instead block)?

You should create new service (UDP 443) and put it above block_youtube rules... The problem will be solved.

 

parinshah
parinshah
New Member
March 1, 2019

Yep, I have the same issue.

Nishad
Nishad
New Member
March 5, 2019

This is the issue with the firmware v6.0.0.  I too had faced the same issue, for the workaround, I have created a web filter profile with the website's allowed along with all category in the block state and allow the urls that you want to allow in static url list.

 

This is work for me. I keep this same setting under observation for 24 hours and found that on some systems youtube is opening on crome but the video was not buffered as it was denied by media streaming category(in backend). 

 

 

hmtay_FTNT
Staff
hmtay_FTNT
Staff
March 6, 2019

Hello,

g

Was deep-inspection enabled for the policy? Would you be able to do a packet capture and send it to me? I can take a look at it and see what's wrong? If the signature works for IE and Firefox, it should have worked on Chrome too. If deep-inspection is enabled, it could be TLS 1.3 that causes the missed detection.

 

Homin

Terms & ConditionsAccessibility statement