Session Replay Issues with Proxy Tracking in Kapa.ai

Matthew M. · 2025-11-20T20:36:52.251Z

@kapa.ai are there any known issues with session replay not working correctly when tracking via proxy?

There isn’t a general “known issue” list specific to Session Replay + proxy in the docs, but there is guidance that CORS / proxy misconfiguration can cause Session Replay requests to fail.The debugging guide calls out that when using a proxy you should: - Ensure CORS is configured correctly (e.g., Access-Control-Allow-Origin, Access-Control-Allow-Headers), or requests to the /record endpoint can be blocked. - Make sure your proxy forwards all required headers (including Authorization, Content-Type, Content-Encoding) to the /record endpoint; otherwise you may see errors like 415 Unsupported Media Type, which would prevent Session Replay data from being ingested. - If you run into persistent CORS/proxy issues, trying the default Mixpanel endpoints is suggested as a fallback because they’re preconfigured for CORS. [Debugging CORS]So: yes, when tracking via a proxy, misconfigured CORS or header forwarding can cause Session Replay not to work correctly, but the docs don’t list any inherent product bug with “Session Replay + proxy” beyond those configuration issues.

kapa.ai is still learning and improving, please let me know how I did by reacting below.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

2 comments