Openload Anti Abuse Mechanism

Openload Anti Abuse Mechanism




🛑 ALL INFORMATION CLICK HERE 👈🏻👈🏻👈🏻

































Openload Anti Abuse Mechanism
Everything about using Adblock Plus on Google Chrome
Embed blocked!
This error was triggered from Openload's anti abuse mechanism


As you can see here I added the following codes (I did not know if I should add it as one single line so I rather added each line of code at a time. eg. ||openload.co/*license then pressed enter)

The problem still persists. Should I disable easylist or keep it on?

Edit: I also added the other domains' version of the above given request to add the lines of code. eg. ||openload.co/*license ||openload.cc/*license ||openload.io/*license (.co | .cc | .io)
what other extensions are you using in chrome ?
Other extensions are tampermonkey (only active on primeseries with a skip buttons script which is nt on at openload) then I have Poper Blocker (For Popups) then Stylish (visuals of sites)
try (for test) keeping enabled only ABP, test again
I disabled every other extension and it still shows Embed Blocked
save your current custom filters and keep only the filters above. Test again.

Removed everything except those filters and the same issue persists, I also did another test by disabling all other extensions again (even the google docs ones) and the issue still persists.
nope: see "Show .." (left at the top). You have to select "blocked items" not ALL.
and be sure you are already in that panel and after that refresh the page (press F5). Then post here the screenshot (more screenshots if there are more pages) with the blocked items.
ah wait, if you click on this link: http://openload.io/f/fBC9VSLbmWU while having the dev tool open then it quickly refers it to https://openload.co/embedblocked?referer=

so I will have to take a video and then find the frame which it shows the first link's site


Display: All posts 1 day 7 days 2 weeks 1 month 3 months 6 months 1 year
Sort by: Author Post time Subject
Direction: Ascending Descending






Post

by Arion » Thu Feb 23, 2017 10:55 pm



Post

by mapx » Thu Feb 23, 2017 11:20 pm



Post

by Arion » Fri Feb 24, 2017 12:42 am



Post

by mapx » Fri Feb 24, 2017 8:48 am



Post

by Arion » Fri Feb 24, 2017 9:10 am



Post

by mapx » Fri Feb 24, 2017 10:30 am



Post

by Arion » Fri Feb 24, 2017 11:38 am



Post

by mapx » Fri Feb 24, 2017 1:31 pm



Post

by Arion » Fri Feb 24, 2017 2:17 pm



Post

by mapx » Fri Feb 24, 2017 2:36 pm



Post

by Arion » Fri Feb 24, 2017 5:48 pm



Post

by mapx » Fri Feb 24, 2017 5:50 pm



Post

by mapx » Fri Feb 24, 2017 5:51 pm



Post

by Arion » Fri Feb 24, 2017 6:15 pm



Post

by Arion » Fri Feb 24, 2017 6:18 pm


Powered by phpBB ® Forum Software © phpBB Limited






Features




Mobile




Actions




Codespaces




Copilot




Packages




Security




Code review




Issues





Integrations




GitHub Sponsors




Customer stories








Explore GitHub


Learn and contribute



Topics




Collections




Trending




Skills




GitHub Sponsors




Open source guides


Connect with others



The ReadME Project




Events




Community forum




GitHub Education




GitHub Stars program








Plans




Compare plans




Contact Sales




Education






In this repository


All GitHub





In this repository


All GitHub





In this organization


All GitHub





In this repository


All GitHub








uBlockOrigin

/

uAssets


Public






Code



Issues



Pull requests



Discussions



Actions



Projects



Security



Insights





qwer1304 opened this issue
Feb 15, 2018
· 8 comments







qwer1304 opened this issue
Feb 15, 2018
· 8 comments











mapx-




closed this as completed


Feb 15, 2018







mapx-




added
the

invalid

label


Feb 15, 2018




update fix https://forums.lanik.us/viewtopic.php?p=127624#p127624 and #…










Sign up for free
to join this conversation on GitHub .
Already have an account?
Sign in to comment













You can’t perform that action at this time.





You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.


Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement . We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Replace the bracketed [...] placeholders with your own information.
After forwarding to openload, I'm getting:
Embed blocked
This error was triggered from Openload's anti abuse mechanism
[Screenshot(s) for difficult to describe visual issues are mandatory ]
Have Nano Defender 13.32 installed
Disabling uBlock Original on the page does NOT resolve the issue
[Add here the result of whatever investigation work you have done: please investigate the issues you report -- this prevents burdening other volunteers. This is especially true for issues arising from settings which are very different from default ones.]




The text was updated successfully, but these errors were encountered:

However, when you get again that error, try disabling not uBo but nano defender.
Update the link.
Disabling Nano Defender doesn't help
I fixed cutw.me anti adb, cannot reproduce your openload issue
Thx.
Try this link http://linkshrink.net/7bMao1 to see the problem with openload
(This is the link cutw.me forwards to)
As I said, cannot reproduce the issue (meaning I arrived on that page but no error for me, the torrent file is downloaded for me)
yes, you should try chrome stable or beta.


Context Navigation

← Previous Ticket Next Ticket →





Oldest first

Newest first


Threaded


This ticket has been modified since you started editing. You should review the
other modifications which have been appended above,
and any conflicts shown in the preview below.
You can nevertheless proceed and submit your changes if you wish so.


leave
as closed
.



reopen
The resolution will be deleted. Next status will be 'reopened'.



reassign
to
The owner will be changed from kzar.

Note: See
TracTickets for help on using
tickets.

Download in other formats:


Comma-delimited Text

Tab-delimited Text

RSS Feed



Opened on 03/03/2017 at 05:39:31 PM
Closed on 03/22/2017 at 06:51:50 AM
Last modified on 04/18/2019 at 08:36:20 AM

w10, 1.12.4.1739, chrome Version 57.0.2987.88 beta (64-bit)


An error occurs: "Embed blocked! This error was triggered from Openload's anti abuse mechanism"


This happens since we've injected a CSP for the page, which prevents Object elements having a non HTTP/S URL. See ​ Issue 4643 - Prevent WebSocket circumvention via object elements .


To avoid this we need to ensure the page isn't whitelisted before injecting our CSP.


This is not a regression since the last release IMO, we already were injecting a CSP in this situation it's just that it didn't happen to trigger openload.io's (current) detection logic.


IIRC Sebastian and I decided this situation didn't matter too much, but perhaps it does. I've opened a review, but even if it gets pushed it will be after the release.


the whitelisting issue is secondary.


The main issue is that error you get in the dev build but not in the stable build .


tested also in uBo ==> no such error (even disabling their special filters from ublock filters or disabling uBo extra)


Done. Possible to whitelist/unwhitelist filters that inject a CSP.


ABP 1.13.2.1785
Chrome 49 / 59 / Windows 7
Opera 36 / 45 / Windows 7

Visit the Trac open source project at http://trac.edgewall.org/



Adblock-Plus-1.13.3-for-Chrome-Opera

Adblock-Browser-for-iOS-2.1.0 Adblock-Browser-for-Android-1.5.0 Adblock-Browser-for-Android-1.4.1

Adblock-Plus-for-Chrome-Opera-Firefox-next Adblock-Plus-for-Internet-Explorer-Next Adblock-Plus-for-Samsung-Browser-next Adblock-Plus-for-iOS-next Customizations-for-Adblock-Plus-next Diagnostics-for-Adblock-Plus-next Element-Hiding-Helper-next URL-Fixer-next Websites code sharing Websites continuous integration Websites editing service acceptableads.com/committee cleanup help.eyeo.com 1.0.0 help.eyeo.com 1.1.0





Adblock-Browser-for-Android Adblock-Browser-for-iOS Adblock-Plus-for-Android Adblock-Plus-for-Chromium Adblock-Plus-for-Internet-Explorer Adblock-Plus-for-Samsung-Browser Adblock-Plus-for-iOS/macOS Asus Browser Automation Core Infrastructure Libadblockplus Libadblockplus-Android Maxthon Office-IT Platform Sitescripts URL-Fixer Unknown User-Interface Websites




Unknown / Cross platform Adblock Browser for Android Adblock Browser for iOS Android Asus Browser Chrome Firefox Firefox Mobile Edge Internet Explorer iOS Maxthon Opera Safari Samsung Browser SeaMonkey Thunderbird Yandex.Browser




Context Navigation

← Previous Ticket Next Ticket →





Oldest first

Newest first


Threaded


This ticket has been modified since you started editing. You should review the
other modifications which have been appended above,
and any conflicts shown in the preview below.
You can nevertheless proceed and submit your changes if you wish so.


leave
as closed
.



reopen
The resolution will be deleted. Next status will be 'reopened'.



reassign
to
The owner will be changed from kzar.

Note: See
TracTickets for help on using
tickets.

Download in other formats:


Comma-delimited Text

Tab-delimited Text

RSS Feed



Opened on 03/03/2017 at 05:39:31 PM
Closed on 03/22/2017 at 06:51:50 AM
Last modified on 04/18/2019 at 08:36:20 AM

w10, 1.12.4.1739, chrome Version 57.0.2987.88 beta (64-bit)


An error occurs: "Embed blocked! This error was triggered from Openload's anti abuse mechanism"


This happens since we've injected a CSP for the page, which prevents Object elements having a non HTTP/S URL. See ​ Issue 4643 - Prevent WebSocket circumvention via object elements .


To avoid this we need to ensure the page isn't whitelisted before injecting our CSP.


This is not a regression since the last release IMO, we already were injecting a CSP in this situation it's just that it didn't happen to trigger openload.io's (current) detection logic.


IIRC Sebastian and I decided this situation didn't matter too much, but perhaps it does. I've opened a review, but even if it gets pushed it will be after the release.


the whitelisting issue is secondary.


The main issue is that error you get in the dev build but not in the stable build .


tested also in uBo ==> no such error (even disabling their special filters from ublock filters or disabling uBo extra)


Done. Possible to whitelist/unwhitelist filters that inject a CSP.


ABP 1.13.2.1785
Chrome 49 / 59 / Windows 7
Opera 36 / 45 / Windows 7

Visit the Trac open source project at http://trac.edgewall.org/



Adblock-Plus-1.13.3-for-Chrome-Opera

Adblock-Browser-for-iOS-2.1.0 Adblock-Browser-for-Android-1.5.0 Adblock-Browser-for-Android-1.4.1

Adblock-Plus-for-Chrome-Opera-Firefox-next Adblock-Plus-for-Internet-Explorer-Next Adblock-Plus-for-Samsung-Browser-next Adblock-Plus-for-iOS-next Customizations-for-Adblock-Plus-next Diagnostics-for-Adblock-Plus-next Element-Hiding-Helper-next URL-Fixer-next Websites code sharing Websites continuous integration Websites editing service acceptableads.com/committee cleanup help.eyeo.com 1.0.0 help.eyeo.com 1.1.0





Adblock-Browser-for-Android Adblock-Browser-for-iOS Adblock-Plus-for-Android Adblock-Plus-for-Chromium Adblock-Plus-for-Internet-Explorer Adblock-Plus-for-Samsung-Browser Adblock-Plus-for-iOS/macOS Asus Browser Automation Core Infrastructure Libadblockplus Libadblockplus-Android Maxthon Office-IT Platform Sitescripts URL-Fixer Unknown User-Interface Websites




Unknown / Cross platform Adblock Browser for Android Adblock Browser for iOS Android Asus Browser Chrome Firefox Firefox Mobile Edge Internet Explorer iOS Maxthon Opera Safari Samsung Browser SeaMonkey Thunderbird Yandex.Browser



Sharon Lee Realitykings
Riley Steele Tinkerbell
College Girl Fingering Herself

Report Page