Diagnose Firefox ETP Blocking Issues

Problem Statement

When you visit a site, you expect Firefox’s Enhanced Tracking Protection (ETP) to block third‑party trackers. If trackers continue to load or the site stops working, something is interfering with ETP. This guide walks you through a diagnostic flow that pinpoints the root cause, verifies the fix, and tells you when to seek further help.

Recognizable Symptoms

• Tracker requests appear in the Network tab even though ETP is enabled.
• The shield icon in the address bar shows a shield but the site still behaves as if trackers were allowed.
• Critical site functions (login, video, maps) fail after enabling ETP.
• ETP appears disabled for a site that should be protected.

Root Causes (Quick Reference)

Cause	Typical Indicator
ETP disabled at site or globally	Shield icon shows a broken shield; no trackers blocked.
Conflict with third‑party blockers (uBlock Origin, NoScript)	False positives; ETP blocks legitimate resources.
Site relies on third‑party scripts that ETP blocks	Missing functionality; broken layout.
Corrupted or outdated profile data	Inconsistent behavior across sessions.
Recent Firefox update bug	Specific tracker categories not blocked until patch.

Diagnostic Flow

1. Confirm ETP Settings

   Open about:preferences#privacy and ensure Enhanced Tracking Protection is set to Strict or Custom. If it’s Off, ETP will not block anything.

   Check the site‑level list: the current URL should not appear in the Block list or Allow list unless you intentionally added it.

2. Inspect the Shield Icon

   Click the shield next to the address bar. It should show a shield with a checkmark if ETP is actively blocking trackers. If the icon is an open shield or broken, ETP is not functioning for that page.

3. Use Developer Tools – Network Tab

   Press Ctrl+Shift+E (or Cmd+Option+E on macOS) to open the Network panel. Reload the page and look for requests that are marked as blocked. If trackers appear as allowed or not found, ETP isn’t filtering them.

4. Check for Third‑Party Blocker Conflicts

   Disable extensions one at a time (especially uBlock Origin, NoScript, Privacy Badger). Reload the page after each disable to see if the issue resolves. If the problem disappears when a blocker is off, a conflict exists.

5. Validate Site‑Level ETP Override

   In the shield panel, click Remove from Allow List or Remove from Block List if the site appears there. Then reload.

6. Profile Integrity Check

   Open about:support and note the Profile Folder location. Close Firefox, copy the folder to a safe place, then create a fresh profile with firefox -P and test the site. If ETP works in the new profile, the original profile is corrupted.

7. Review Update History

   Check about:config for browser.aboutConfig.showWarnings and ensure it’s true. Look at about:preferences#privacy for any release notes about ETP changes. If you recently updated Firefox, consider rolling back to the previous version to see if the issue persists.

Fixes Tied to Findings

• ETP Disabled Globally

  Set Enhanced Tracking Protection to Strict or Custom in about:preferences#privacy. Verify by reloading the page and checking the shield icon.

• Site‑Level Override

  Remove the site from the Allow or Block list in the shield panel. If the site is essential for functionality, add it to the Allow List after confirming that ETP isn’t blocking critical resources.

• Extension Conflict

  Configure the conflicting blocker to respect Firefox’s ETP. For uBlock Origin, enable uBO: Respect Firefox ETP in the settings. If the blocker still interferes, consider disabling it for that site.

• Site Depends on Blocked Scripts

  Use the shield panel’s Show blocked content to identify which scripts are blocked. Add them to the Allow List in about:config with the preference privacy.trackingprotection.trackingContentAllowed set to true for that domain.

• Corrupted Profile

  Create a new profile: firefox -P, test the site, then migrate bookmarks and extensions. If ETP works, keep the new profile.

• Bug in Recent Update

  Check Mozilla’s bug tracker for ETP issues in your Firefox version. If a bug is confirmed, either wait for the next update or temporarily downgrade Firefox.

Verification Checklist

1. Reload the site after applying each fix.
2. Confirm the shield icon shows a shield with a checkmark.
3. Open the Network tab and ensure previously blocked requests no longer appear as allowed or not found.
4. Test site functionality (login, video, maps) to verify no breakage.

Escalation Criteria

• If ETP remains disabled after confirming settings and no extensions are interfering.
• If site breakage persists after adding critical scripts to the allow list.
• When the issue appears consistently across multiple profiles and machines.
• When a known Firefox bug is suspected but no fix is available.

Practical Tips

• Always perform troubleshooting in a private browsing window to avoid affecting your regular profile.
• Keep a backup of your profile before making significant changes.
• Document the steps you take and the results; this helps when reporting bugs.

By following this diagnostic flow, you can quickly determine why Firefox’s ETP isn’t blocking trackers or is causing site breakage, apply the right fix, and verify that the problem is resolved. If the issue remains after all steps, consider filing a detailed bug report with Mozilla, including the Firefox version, operating system, and the exact symptoms observed.