[GH-ISSUE #44] Extension gets blocked by uBlockOriginLite (not uBlockOrigin) extension #26

New issue

Closed

opened 2026-03-23 20:31:49 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:31:49 +00:00

Owner

Originally created by @ewoks on GitHub (Aug 6, 2024).
Original GitHub issue: https://github.com/tubearchivist/browser-extension/issues/44

Releated to the issue reported here https://github.com/tubearchivist/browser-extension/issues/43, I'm leaving this as a info for others as many might soon switch from uBlock Origin to uBlock Origin Lite have similar problem.

The uBlock Origin Lite 2024.8.5.925 extension (maybe other version too) is currently blocking TubeArchivist extension to connect to the TubeArchivist server. Extension will show error similar to

Pinging manually /api/ping/ endpoint, returns HTTP 200, pong as expected.

There was no issue with uBlock Origin before and this communication error is solely caused by new lite extension.

Adding the server IP to the extension setting as an exception to the "list of hostnames for which no filtering will take place" doesn't resolve the issue.

As a current workaround, I will recomment to stay with uBlockOrigin if you are user of it until Lite takes these cases in consideration, or even until Google Chrome completely enforce the change to manifest v3 for all extensions.

Originally created by @ewoks on GitHub (Aug 6, 2024). Original GitHub issue: https://github.com/tubearchivist/browser-extension/issues/44 Releated to the issue reported here https://github.com/tubearchivist/browser-extension/issues/43, I'm leaving this as a info for others as many might soon switch from `uBlock Origin` to `uBlock Origin Lite` have similar problem. The uBlock Origin Lite 2024.8.5.925 extension (maybe other version too) is currently blocking TubeArchivist extension to connect to the TubeArchivist server. Extension will show error similar to ![image](https://github.com/user-attachments/assets/c563a288-4743-414d-8492-e45395601614) Pinging manually `/api/ping/` endpoint, returns HTTP 200, pong as expected. There was no issue with `uBlock Origin` before and this communication error is solely caused by new lite extension. Adding the server IP to the extension setting as an exception to the _"list of hostnames for which no filtering will take place"_ doesn't resolve the issue. As a current workaround, I will recomment to stay with `uBlockOrigin` if you are user of it until Lite takes these cases in consideration, or even until Google Chrome completely enforce the change to manifest v3 for all extensions.