With the /tunnel
endpoint set up, Sentry doesn't appear to be able to save replays. Using compression on the replay payload
does not appear to make a difference.
Check it out:
- Create
.env
filecp .env.example .env
- Edit the newly created
.env
with values for a Sentry project under your control. npm run dev
- Navigate browser to
http://localhost:5173/sentry-example-page
- Click the "Throw error!" button.
- Open your Sentry dashboard and observe: error logged, no replay.