-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
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
uBlockOriginLite blocks other extension to work properly #169
Comments
I know nothing about TubeArchivist, TubeArchivist URL or TubeArchivist API Key. What do I need to enter in the fields to reproduce the issue? |
Fair enough, let me try to explain better... Next to the I tried to add locally hosted server IP to the exclusion list in Hope it is more understandable now, but please let me know if I should explain something better. Thanks for considering how to solve this |
Which rulesets are enabled in your uBOL? |
filter lists:
and there is it.. 😅 turning off Question before we close this: Why Thanks a ton again |
It's a browser issue, one extension is not supposed to interfere with the network requests of other extensions, see w3c/webextensions#369. As per latest comment in the thread, this is reportedly fixed in Chromium 128. |
I see.. can confirm my Chrome is on v127.0.6533.88, therefore it makes sense. |
uBlockOriginLite
currently (v2024.8.5.925) blocks theTubeArchivist
Chrome extension to connect to the TubeArchivist server as described in tubearchivist/browser-extension#44Reducing blocking to the "Basic" or adding exception with the TubeArchivist server IP doesn't help, extension just can't connect to the server (via http if it matters).
The only workaround I came up until now so the
TubeArchivist
can connect, is to go back touBlockOrigin
and completely removeuBlockOriginLite
.Any better suggestion is welcome :)
The text was updated successfully, but these errors were encountered: