aprilnea/sentry-tunnel

Sentry Tunnel is a tool that helps your app keep reporting errors to Sentry even when users have ad-blockers or privacy extensions installed. Many ad-blockers block requests to Sentry's servers by default, which means you lose visibility into crashes and bugs that real users are experiencing. This project solves that by routing those error reports through your own domain instead, so they look like normal traffic to your site. When a user's browser would normally send an error report directly to Sentry, the tunnel intercepts it and forwards it along on your behalf. You configure it with your Sentry host and a list of allowed project IDs, and it handles the rest. On the client side, you just add one line to your Sentry configuration telling it to use a tunnel path on your domain. The tunnel checks that incoming requests are legitimate by validating the hostname and project IDs, so nobody can abuse your server to proxy traffic to random destinations. This is useful for teams running web apps who rely on Sentry for error monitoring but know their users have ad-blockers. For example, if you run a SaaS dashboard and a chunk of your users have privacy extensions installed, those users' errors may never reach Sentry without a tunnel like this. Product managers and developers who notice gaps in their error data often trace the problem back to content blockers, and this is a straightforward fix. The project is built in Rust and designed to integrate with Axum, a web framework, but it also offers a framework-agnostic core handler if you use something else. It is modular by design, so you can enable only the pieces you need. The security model is deliberate: by restricting which project IDs and hostnames are allowed, it prevents your server from becoming an open proxy that bad actors could exploit.