How to set up a reverse proxy from Vercel/Next.js to PostHog

[@floriankohler9681]

once i have set up the reverse proxy can i still check whether the posthog implementation works when in local development mode?

[@AmitavKhandelwal]

Is there a recommendation about which one we should do though? Or does it not matter, do they effectively end up doing the same under the hood?

[@ianvph]

Hi Amitav, they are effectively the same under the hood.

[@TabuHana]

Could you explain what this is for?

[@PostHog]

Some requests to 3rd parties are blocked by tracking blockers. By using a reverse proxy, you send your request from a 1st party, helping avoid tracking blockers and getting a more accurate picture of usage.

[@gauravr4127]

Thank you, This was a quick solution but it seems I am now stuck with another problem where it says 431 Header too large. Should I use posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY!, { api_host: process.env.NEXT_PUBLIC_POSTHOG_HOST, capture_pageview: false, persistence: 'localStorage+cookie', (local storage + cookie?)

[@PostHog]

Can you try clearing your cookies and see if that fixes it?