## Context
With an adblocker enabled, `posthog.init` succeeds but loading assets (e.g. from `eu-assets.i.posthog.com`) fails with `ERR_BLOCKED_BY_CLIENT`, and PostHog keeps throwing/retrying errors.
## Verified resolution
Maintainer marandaneto closed it stating the only reliable solution is the reverse proxy (https://posthog.com/docs/advanced/proxy), which hides the PostHog domains so adblockers can't match them. Maintainer ioannisj added: bundle the SDK extensions into your own app (`npm install posthog-js` instead of the CDN snippet) so `/static/*.js` requests never happen, or use the `prepare_external_dependency_script` init hook to rewrite asset paths through your proxy.