Skip to content
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

Closed
ewoks opened this issue Aug 6, 2024 · 6 comments
Closed

uBlockOriginLite blocks other extension to work properly #169

ewoks opened this issue Aug 6, 2024 · 6 comments

Comments

@ewoks
Copy link

ewoks commented Aug 6, 2024

uBlockOriginLite currently (v2024.8.5.925) blocks the TubeArchivist Chrome extension to connect to the TubeArchivist server as described in tubearchivist/browser-extension#44

Reducing 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 to uBlockOrigin and completely remove uBlockOriginLite.

Any better suggestion is welcome :)

@gorhill
Copy link
Member

gorhill commented Aug 6, 2024

I know nothing about TubeArchivist, TubeArchivist URL or TubeArchivist API Key. What do I need to enter in the fields to reproduce the issue?

@ewoks
Copy link
Author

ewoks commented Aug 6, 2024

Fair enough, let me try to explain better...
I selfhost instance of tubearchivist server in my local network, so the TA get assigned local IP address.
The Chrome TA Companion extension need this IP and API key from the TA server as configuration (similar to the screenshot) to connect to the TA server.
image

Next to the Save button is checkmark if connection can be established, otherwise there is an "Could not connect to server" error:
image

I tried to add locally hosted server IP to the exclusion list in uBOL, it didn't help. If I try to reach the same endpoint outside of Chrome with uBOL, I got valid response from server.
The only way around this issue for me, was to disable uBOL and go back to uBO (which doesn't cause the issue) until there is a better option.

Hope it is more understandable now, but please let me know if I should explain something better. Thanks for considering how to solve this

@gorhill
Copy link
Member

gorhill commented Aug 6, 2024

Which rulesets are enabled in your uBOL?

@ewoks
Copy link
Author

ewoks commented Aug 6, 2024

filter lists:

  • Default (1/1) Ads, trackers, miners, and more
  • Annoyances (5/5) Chat Widgets, Other Annoyances. Social Widgets, Cookie Notices, Overlay Notices
  • Miscellaneous (2/4) AdGuard URL Tracking Protection, Block Outsider Intrusion into LAN

and there is it.. 😅 turning off Block Outsider Intrusion into LAN resolves my issue.
Thanks a ton for the guide and good hint!!! 💪💪💪

Question before we close this: Why mBOL is causing the issue while mBO (not lite) didn't?
I will move to local domain anyway, just curious about the background of this.

Thanks a ton again

@gorhill
Copy link
Member

gorhill commented Aug 6, 2024

turning off Block Outsider Intrusion into LAN resolves my issue

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.

@gorhill gorhill closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
@ewoks
Copy link
Author

ewoks commented Aug 6, 2024

I see.. can confirm my Chrome is on v127.0.6533.88, therefore it makes sense.
Thanks once again and keep rocking 🚀

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

No branches or pull requests

3 participants