- by RiCK, a year agoRated 4 out of 5Last update started to request access to IP Address:
See release notes.
uBO requires a new permission, dns, which is required to solve issue 780. This may triggers a new permission warning from Firefox when uBO updates to the latest dev build, specifically "Access IP address and hostname information", even though this was already possible for uBO to access that information.
From now on uBO will CNAME-uncloak network requests. CNAME-uncloaked network requests will appear as blue entries in the popup panel and the logger. The uncloaked entries in the popup panel will also show the related aliases (in smaller characters underneath the canonical names).
Network requests which were blocked, redirected, or excepted by a filter/rule are not uncloaked. Canonical hostnames which are first party to the associated alias hostname are not fed back into uBO's filtering engine.
Warning: CNAME-aliased hostnames exist most likely for content delivery purpose, i.e. legitimate.
- by Firefox user 15235351, a year agoRated 4 out of 5"Important: the statement "IP address" refers to the IP address of the servers to which your browser connects, NOT your specific IP address. uBO has no access to (and no need to know) your specific IP address."
- by Firefox user 13441211, a year agoRated 4 out of 5I'm very satisfied with this extension. Default options right after installation are generally fine. If you want better results, It takes some time to learn about all the available options but the more you learn the more you'll benefit from this fast, light and very customizable extension.
- by Firefox user 15695341, a year agoRated 4 out of 5Greetings. I am using this addon for some time, however since yesterday it has not been blocking ads. Cannot find a solution on the internet. I would be really happy if you could provide me some advice.
Thanks for reply. I also tried another addon, Privacy Badger and it seems that also does not work. Maybe something is wrong with Firefox.
After reinstalling whole firefox with returning to default options and preferences it repaired.
Thanks for your time.
Developer responseposted a year agoThis can happen when the extension storage gets corrupted. First try to reset to default settings (bottom of "Settings" pane in the dashboard), and if this does not work, try removing and reinstalling the extension. You may want to first backup your custom settings in order to be able to restore them afterward.