-
Notifications
You must be signed in to change notification settings - Fork 80
Troubleshooting
I am going to collect here common usage issues users may face.
The best way to troubleshoot uBlock Origin is with uBlock Origin: the logger will tell you what uBO is doing when you try to load a web page. Using the logger is the first thing you should try when you are trying to find out why a page does not load/display as expected.
You can fix this by following the following steps:
- In the navigation bar (Awesome Bar) enter
about:config
- Click on the
I'll be careful, I promise!
button - Search for
ublock0
- Double click on
extensions.ublock0.forceLegacyToolbarButton
so that the value =true
- Restart Firefox
You can fix this by following the following steps:
- If you use a Linux system go to Edit - Settings - Content and choose a default font other than "serif". "Liberation" and "Clear" are known to work.
- If the icons are still not showing enter
about:config
in the navigation bar and promise to be careful - Search for
fonts
- Check that
gfx.downloadable_fonts.enabled
is set totrue
and see whether the icons appear now. - If it still does not work you might have to set
browser.display.use_document_fonts
to1
but that should not be necessary if you followed step 1.
Because you enabled "Fanboy’s Social Blocking List", or one of the filter lists which includes it, like "Fanboy’s Annoyance List" or "Fanboy+Easylist-Merged Ultimate List".
False positive.
uBO ships with malware filter lists, and this causes false positives in some antiviruses.
Unfortunately, your Chrome browser executable has probably been tampered by malware:
At this point we're pretty sure that this error is primarily caused by malware / unwanted software on your machine actively tampering with the contents of the chrome binary and your user profile directory data
You will need to clean up whatever malware tampered with your Chrome browser installation. Starts here: Malwarebytes Anti-Malware
I've seen this happens on a Chromium-based browser. Upon investigation, even though uBO's icon was on the toolbar, I found that the extension was not actually in memory. I believe this problem coincided with uBO having been updated with a new version from the Chrome store. Forcing a restart of uBO fixed the issue (uncheck then check Enable in the Extensions page).
So it does appear the browser's automated update of an extension can go wrong sometimes. Forcing a restart of the extension fixes the issue.
This has been reported many times. This could be caused a false positive from your anti-virus application.
Specifically, it has been confirmed Avira Anti-virus has been uninstalling uBlock Origin.
- Are you using the no-popups switch?
- Are you using a Chromium-based browser?
If you answer "yes" to both questions above, this is your problem (from link above):
Caveat for Chromium-based browsers: Due to Chromium API limitations, it's not possible for uBlock to determine for sure whether a new tab being opened is that of a popup, or is the result of a legitimate click on a link by the user. So if the no-popups switch is in use, you won't be able to open a link in a new tab through the context menu.
- Wiki home
- About the Wiki documentation
- Permissions
- Privacy policy
- Info:
- The toolbar icon
- The popup user interface
- The context menu
-
Dashboard
- Settings pane
- Filter lists pane
- My filters pane
- My rules pane
- Trusted sites pane
- Keyboard shortcuts
- The logger
- Element picker
- Element zapper
-
Blocking mode
- Very easy mode
- Easy mode (default)
- Medium mode (optimal for advanced users)
- Hard mode
- Nightmare mode
- Strict blocking
- Few words about re-design of uBO's user interface
- Reference answers to various topics seen in the wild
- Overview of uBlock's network filtering engine
- uBlock's blocking and protection effectiveness:
- uBlock's resource usage and efficiency:
- Memory footprint: what happens inside uBlock after installation
- uBlock vs. ABP: efficiency compared
- Counterpoint: Who cares about efficiency, I have 8 GB RAM and|or a quad core CPU
- Debunking "uBlock Origin is less efficient than Adguard" claims
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: uBlock consumes several or several dozen GB of RAM
- Various videos showing side by side comparison of the load speed of complex sites
- Own memory usage: benchmarks over time
- Contributed memory usage: benchmarks over time
- Can uBO crash a browser?
- Tools, tests
- Deploying uBlock Origin
- Proposal for integration/unit testing
- uBlock Origin Core (Node.js):
- Troubleshooting:
- Good external guides:
- Scientific papers