feat: configure PostHog reverse proxy to bypass ad blockers

- Updated PostHog initialization to use a reverse proxy for API requests.
- Added rewrites in Next.js configuration to route requests through the domain.
- Set ui_host for proper toolbar functionality and ensured correct pageview tracking.

surfsense_web/instrumentation-client.ts

@@ -2,7 +2,10 @@ import posthog from "posthog-js";
 
 if (process.env.NEXT_PUBLIC_POSTHOG_KEY) {
 	posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY, {
-		api_host: process.env.NEXT_PUBLIC_POSTHOG_HOST,
+		// Use reverse proxy to bypass ad blockers
+		api_host: "/ingest",
+		// Required for toolbar and other UI features to work correctly
+		ui_host: "https://us.posthog.com",
 		defaults: "2025-11-30",
 		// Disable automatic pageview capture, as we capture manually with PostHogProvider
 		// This ensures proper pageview tracking with Next.js client-side navigation

surfsense_web/next.config.ts

@@ -31,6 +31,27 @@ const nextConfig: NextConfig = {
 		}
 		return config;
 	},
+
+	// PostHog reverse proxy configuration
+	// This helps bypass ad blockers by routing requests through your domain
+	async rewrites() {
+		return [
+			{
+				source: "/ingest/static/:path*",
+				destination: "https://us-assets.i.posthog.com/static/:path*",
+			},
+			{
+				source: "/ingest/:path*",
+				destination: "https://us.i.posthog.com/:path*",
+			},
+			{
+				source: "/ingest/decide",
+				destination: "https://us.i.posthog.com/decide",
+			},
+		];
+	},
+	// Required for PostHog reverse proxy to work correctly
+	skipTrailingSlashRedirect: true,
 };
 
 // Wrap the config with MDX and next-intl plugins