Skip to main content

Browser content blockers

A content blocker can prevent regex101 from loading resources. Compare the failing action with extensions disabled.

Investigate an editor problem​

  1. Preserve your unsaved pattern and input.
  2. Open regex101 in a separate browser profile.
  3. Compare the behavior with extensions disabled in that profile.
  4. Inspect blocked requests or errors associated with the failing action.

If the same problem occurs without extensions, continue with application troubleshooting.

The public application displays sponsor placements. Pro removes those placements. Sponsorship documentation describes the available placements.

Per-site exceptions​

The public privacy policy describes the service's data practices. Browser and blocker controls determine which third-party requests your device allows. A per-site exception can permit more requests than the one that caused an error.

Add a per-site exception​

  1. Open the content blocker's control for the current site.
  2. Inspect its explanation of the per-site exception.
  3. If you want to allow the site, enable that exception for regex101.com.
  4. Reload the page.
  5. Verify the result of the action you were investigating.

The exact controls depend on the blocker and its version. For network-wide filtering, ask your administrator to inspect blocked requests.