Fix a problem
Check why Shield appears inactive
Check the current page, global and site protection, browser access, and visible warnings.
Quick answer
Start with the website and protection status shown in Shield’s popup. A missing count is not evidence that blocking is off. Production Chrome and Edge do not provide Shield’s blocking counts; Firefox’s counts are aggregate and do not describe only the current website.
Check a normal website you can reload. Browser settings pages, extension pages, and other restricted pages are not suitable places to confirm page protection.
Where to find it
Open Shield AdBlock from the browser toolbar or extensions menu. Use Settings for the global protection switch and warnings. Use your browser’s extension manager to check whether Shield itself is enabled and has website access.
What to do
- Open a normal HTTP or HTTPS website.
- Reload it if it was open before installing or updating Shield.
- Open Shield and check the named website.
- If it says No active site, return to the website tab and reopen the popup.
- If blocking is off everywhere, turn on Protection everywhere in Settings.
- If this website is paused, use its resume action.
- Reload the website and check the popup again.
If a pause remains, review Settings → Websites → Paused Protection. A parent hostname can still cover the current page after a more specific entry is removed. Check Ad Hiding Paused separately if request blocking seems active but page elements remain visible.
If an access warning appears, review Shield’s website permissions in the browser extension manager. Restricted access can remove page-feature coverage and affect Firefox request blocking. Follow browser access and permissions for the browser-specific limits.
What should happen
The popup should show a known protection state for the website once its settings load. A saved enabled setting does not prove every source or page feature loaded successfully. Read any warning under Settings, including warnings about unavailable sources, ad hiding, or inactive request-blocking rules.
If Shield says it could not finish an internal update and will retry shortly, allow the retry to finish. If it says settings could not be read or are read-only, record that warning before changing more controls; do not assume displayed fallback values are your saved choices.
Undo and check
Resume temporary pauses after testing. Restore other switches you changed only for diagnosis. If browser access was intentionally restricted, review the effect before expanding it. You can choose where you want Shield to operate.
If that does not work
If Shield will not open at all, check its enabled state in the browser’s extension manager. You can reload the extension there if your browser offers that action, then reload the website. Preserve a backup before considering removal; read backup guidance. Share the exact warning and browser and Shield versions with support before resetting your setup.
Related help
Contact support and share a report if the problem continues. You can also find the support contact details.