Support

Use this page when PostHog Debugger does not show the expected PostHog events, network requests, feature flags, or session details.

Install from Firefox Add-ons

1. Open PostHog Debugger (Unofficial) on Firefox Add-ons.
2. Click Add to Firefox.
3. Open the site you want to debug.
4. Open Firefox DevTools and select the PostHog panel.
5. Reload the page so the panel can capture events fired during page load.

Install from the Chrome Web Store

1. Open PostHog Debugger (Unofficial) on the Chrome Web Store.
2. Click Add to Chrome.
3. Open the site you want to debug.
4. Open Chrome DevTools and select the PostHog panel.
5. Reload the page so the panel can capture events fired during page load.

Troubleshooting

No Events Appear Until the Page Reloads

PostHog Debugger captures requests after its page hook is installed. If DevTools or the PostHog panel was opened after the page already loaded, reload the page with DevTools still open.

Also check that recording is not paused and that the Events filters are not hiding the events you expect to see.

Requests Are Blocked by an Ad Blocker

Ad blockers, privacy tools, browser shields, and corporate network filters can block PostHog ingestion requests before they reach PostHog. In that case the Network tab should show blocked or failed PostHog-shaped requests.

To confirm the cause, test in a clean Chrome profile or temporarily disable the blocking tool for your development site.

Self-Hosted or Reverse-Proxied PostHog Endpoints

PostHog Debugger detects self-hosted and reverse-proxied requests by endpoint shape, including /i/v0/e/, /e/, /batch/, /capture/, /decide, /flags, and /s/.

If your proxy rewrites those paths to a custom shape, the extension may not recognize the traffic. Check the Network tab for the actual request URLs and open a support issue with the proxy path pattern if detection needs to be added.

Iframe Limitations

The extension is designed to capture PostHog traffic from frames where Chrome allows the content script to run, including many embedded widget and iframe setups. Chrome can still restrict extension injection in some frames, such as browser-protected pages or frames with restricted schemes. Extension settings pages can still be debugged when DevTools exposes their network requests and a readable inspected page.

If iframe traffic is missing, test whether the same PostHog call appears when loaded in a normal top-level HTTP or HTTPS page, then include the frame URL scheme and setup details in a support issue.

Contact

For bug reports, support questions, or endpoint detection requests, open a GitHub issue:

https://github.com/Gevorg-Glechyan/posthog-debugger/issues

Include the extension version, browser version, the PostHog endpoint shape you expected to capture, and whether the issue happens after reloading the page with DevTools open.