-
Notifications
You must be signed in to change notification settings - Fork 28
[Anti-adblock] hulu.com #97
Comments
This did come up during testing; the discussion took place in a confidential issue so it's normal that you couldn't find it. This is really rare so we couldn't investigate the cause. How often do this happen to you? |
Understandable. Shortly after writing my post it happened three more times on one video. It's quite common on my end, each time the console showed the same text. Maybe it's based on location and difficult to reproduce without a proxy? I'm not much of an expert on how ads are pulled, but it's an idea. |
Got another report from the US:
|
On Reddit, by
|
Can someone try these?
|
Preroll is fixed but Hulu has a new timer so the 1 sec blank video no longer works. Instead I am still getting the "Sorry, we're unable to load a message" message for full 120 seconds. |
This has GeoLock and requires account. It is horrifyingly hard to test. |
@killer23d |
@jspenguin2017 when Hulu detects ad block, it will show a full 2 min of error message. Otherwise the ad duration is random from 1 min to 4 min. I can get you VPN or DNS bypass and account access if you need to troubleshoot. |
Can you reproduce ads/anti-adblock on uBO default? |
Finally got time to try, with default and updated all the default filters. The ads are still on, even pre-roll are showing. The issue with Hulu is that when it detects a ad block and the error message will be shown at full length. The length is random. I've attached the console log. |
@okiehsch Can you test? |
No. |
URLs where this issue occurs (Required)
https://www.hulu.com/watch/102162#i0,p12,s8,d0
Screenshots (Required)
https://i.imgur.com/Uzr1FxK.png
Screenshot of console (Required, press
F12
to open the console)https://i.imgur.com/4eJbzCV.png
Describe the issue (Optional if obvious)
While the filters generally work as expected, it occasionally breaks, a blue screen flashes for a second and I'm left with the screen above, the player is unresponsive until I refresh. It happens at complete random during the blank ad timeouts.
Apologies if this is a known issue, I couldn't find anything related.
Reproduction Steps (Optional if trivial)
It seems to be a guessing game when it will happen. Going through the process of "ads" will eventually turn up this anomaly.
Environment (Required)
Your filter lists (Required)
https://i.imgur.com/v4elArj.png
The text was updated successfully, but these errors were encountered: