CHROMIUM: YouTube now showing annoying advertisements...

Dustyn

Dustyn

New Member
Hey yall, how you doing?

To start off I am using Windows 10 Pro 64-bit Version 1607 (OS Build 14393.51) Anniversary Update, Adguard v6.0.226.1108 and the latest snapshot release of Chromium. For some rather strange annoying reason, Adguard doesn't seem to want to filter out YouTube advertisements anymore when using Chromium. I had no issues before, in fact, it worked splendidly. I have disabled "do not block useful adds" and removed that filter altogether. The filters I believe are the default set of filter when installing Aguard for the very first time. I have also added Chromium into the specific list of apps that Adguard automatically populates with apps that are being filtered as Chromium was not listed. I made sure the path to Chromium is correct. I am using the User Filter, English Filter, Spyware Filter, Social Media Filter all up to date.

A few key notes here...
Untitled.jpg Untitled2.jpg
That horrid video advertisement banner on the front of YouTube is successfully filtered and removed if using Internet Explorer 11. I also would like to mention that Adguard filters and removes all advertisements within playing videos along with the YouTube video banner on the front page of YouTube.com. Adguard assistant is also visible and functioning with IE11. While using Chromium, my lovely Adguard Assistant vanishes and I can not use Adguard Assistant on YouTube. I also now have those annoying video advertisements that display within video when the play time lands on a specific time frame in the video that has a yellow block in the seek bar. This was never as issue before and Adguard removed all this stuff. It almost seems as if Adguard just doesn't filter any advertisement when using Chromium now. It did before? Especially since Adguard Assistant just disappears from the bottom right hand corner of my browser window when I go to YouTube.com. It remains on other webpages like Google or DSLreports,com, CNET.com... ect.

I understand things break from time to time. But I would very much appreciate any insight or help into this matter. I've had advertisements sneak past Adguard before on YouTube... RARE... but occasional and then Adguard usually updates itself with a newer updated filter that takes care of the problem. So far, this problem has been going on since the Windows 10 Anniversary Update, and I'm not too sure what to do?

EDIT1: An important update. So, for some bizarre reason, it looks as if Chromium is no longer displaying that video add on the front page of YouTube. However I still have a rather nasty empty area when the add was.
Untitled2.jpg
I don't know if a slight filter tweak was made for it... but fingers crossed? I still can't access Adguard Assistant ONLY when I'm on YouTube.com and ONLY with Chromium.

EDIT2: Why would Chromium be using GeoTrust Global CA Certificate only when on YouTube.com but IE11 uses the Adguard Personal CA Certificate? Why isn't Chromium using the Adguard Personal CA Certificate too? Would that be affecting my add blocking in Chromium?
Untitled.jpgUntitled.jpg
 
Last edited:
Boo Berry

Boo Berry

Moderator + Beta Tester
Moderator
Looks like Adguard's certificate isn't being used in Chromium, hence why ad blocking isn't working on YouTube (since it's a HTTPS site) and why the Assistant isn't appearing. As for why, I'm not sure as it's working for me in Chromium. You can try opening Adguard's settings > General Settings section and pressing the Reinstall Certificate button. If that fails, I'd try manually adding Chromium to the Filtered Apps list (even though by default it should already filter it, assuming the executable is called chrome.exe).
 
Dustyn

Dustyn

New Member
Untitled.png Untitled2.png
So I did just that and re-checked the "chrome" executable location to verify that the location is valid.
Relaunched Chromium and I have the same results with JUST YouTube.com. The Adguard cert is installed and working on any other https:// site, so the Adguard Assistant displays on any other site. YouTube does not use the Adguard Personal CA cert and I see no Adguard Assistant. The Adguard Personal CA cert is being used when I visit YouTube with Internet Explorer 11 though.

To add, here I am using Adguard happily within Chromium displaying the proper Adguard Cert, along with Adguard assistant fully enabled on an HTTPS:// connection to that site.
Untitled.jpg
 
Last edited:
R

Releno

New Member
I'm having the same problem while using Chrome. Ad blocking on all the other browsers work fine, but while using Chrome, both the Google and YouTube domains are showing ads for me. I've checked and on both cases the Adguard Certificate is not being used. Also both YouTube and Google domains are not on the HTTPS exclusion lists. I already tried reinstalling the certificate and doing a clean install of Adguard, but nothing worked.
 
Dustyn

Dustyn

New Member
Sometimes pictures help, I hope these do?
Shows how Adguard Personal CA is being used on some aspects of the site (doubleclick, adds...ect), but Google Internet Authority G2 is the dominant cert being used on YouTube.com. Take a look...
Untitled2.jpg Untitled000.jpg Untitled0000.jpg Untitled0.jpg Untitled00.jpg Untitled.jpg Untitled3.jpg Untitled4.jpg Untitled5.jpg Untitled6.jpg
 
avatar

avatar

Administrator
Staff member
Administrator
@Dustyn thank you for the screenshots! Now it is clear why YT ads are there. The question is how is that possible:)

I see two possible reasons for it:
1. Chrome could switch to QUIC protocol (which we block by default, but who knows maybe it has happened?).
2. Chrome could use TCP FastOpen feature which is pretty buggy now. Although this is highly unlikely, as I know TCP FastOpen is not available on Windows.

So, here is what you can do:
1. Go to "chrome://flags".
2. Find "Experimental QUIC protocol" there and set it to "Disabled".
3. Find "TCP Fast Open" and also disable it.
4. Relaunch Chromium and check YT
 
Dustyn

Dustyn

New Member
avatar said:
@Dustyn thank you for the screenshots! Now it is clear why YT ads are there. The question is how is that possible:)

I see two possible reasons for it:
1. Chrome could switch to QUIC protocol (which we block by default, but who knows maybe it has happened?).
2. Chrome could use TCP FastOpen feature which is pretty buggy now. Although this is highly unlikely, as I know TCP FastOpen is not available on Windows.

So, here is what you can do:
1. Go to "chrome://flags".
2. Find "Experimental QUIC protocol" there and set it to "Disabled".
3. Find "TCP Fast Open" and also disable it.
4. Relaunch Chromium and check YT
Click to expand...
So I followed you directions and the only thing I could disable was the "Experimental QUIC protocol".
"TCP Fast Open" experiment is not available to me as you indicated as I'm using Windows.

All I can say is a great big THANK YOU to you Andrey! After relaunching Chromium, YouTube is now using the Adguard Personal CA cert and is once again BLOCKING all advertisements in YouTube just like IE11. Looks so much better now! I'm thinking this will also help with other sites I may not have noticed working correctly too. I am very very happy this did the trick as I can now start using Chromium more often now. Very interesting to hear that this appears to be a major issue too! :eek: Hopefully this can be resolved with perhaps a new Adguard program release/update in future. Thank you kindly! :D
Untitled.jpg
 
Boo Berry

Boo Berry

Moderator + Beta Tester
Moderator
Eventually, hopefully, Adguard will support QUIC and HTTPS/2.

Also if anyone is using Chrome, Vivaldi or Opera, you can put in chrome://flags and disable QUIC there too.
 
avatar

avatar

Administrator
Staff member
Administrator
Boo Berry said:
Eventually, hopefully, Adguard will support QUIC and HTTPS/2.
Click to expand...
HTTP/2 for sure, but I don't think we will mess with QUIC. It is a bit too experimental.

Also the issue is sorted out in the latest RC.
 
Dustyn

Dustyn

New Member
avatar said:
HTTP/2 for sure, but I don't think we will mess with QUIC. It is a bit too experimental.

Also the issue is sorted out in the latest RC.
Click to expand...
Good to hear!

Also, why wouldn't developers of Adguard want to work with QUIC?
From what I can see although experimental, has some benefits?

Key features of QUIC over existing TCP+TLS+HTTP2 include
  • Dramatically reduced connection establishment time
  • Improved congestion control
  • Multiplexing without head of line blocking
  • Forward error correction
  • Connection migration
Just curious is all. :)
 
avatar

avatar

Administrator
Staff member
Administrator
Dustyn said:
From what I can see although experimental, has some benefits?
Click to expand...
There is a number of reasons:
1. No good documentation on how this protocol works.
2. Developed and used by Google only.
3. It often changes so it'd be hard to support it.
 
Dustyn

Dustyn

New Member
Just wanted to report some findings...
After installing Adguard v6.1.258.1302 it appears that "Experimental QUIC protocol" in Chromium now works with Adguard when this experimental feature is turned back on.

Did something change with this recent release of Adguard and how does Adgaurd now address QUIC when enabled?
Not saying I will keep QUIC enabled, but I'm wondering as to why it now functions correctly with this latest release of Adguard but failed before?
 
Boo Berry

Boo Berry

Moderator + Beta Tester
Moderator
Dustyn said:
Did something change with this recent release of Adguard and how does Adgaurd now address QUIC when enabled?
Not saying I will keep QUIC enabled, but I'm wondering as to why it now functions correctly with this latest release of Adguard but failed before?
Click to expand...
They fixed QUIC connections slipping through in the pre-final 6.1 build. QUIC connections, as far as I know, are prevented when Adguard for Windows is enabled.
 
You must log in or register to reply here.
Top