Add Sentry tunnel to bypass ad-blocker on test environment

Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 15:40:14 +02:00
parent b7617d968d
commit f650c01c3e
4 changed files with 38 additions and 0 deletions
@@ -35,6 +35,24 @@ server {
        root /var/www/certbot;
    }

+    # Sentry "tunnel" endpoint (see src/main.tsx's Sentry.init tunnel option).
+    # Browser ad-blockers/privacy extensions commonly block requests that go
+    # straight to *.ingest.<region>.sentry.io (ERR_BLOCKED_BY_CLIENT), since
+    # that looks like third-party tracking. By forwarding this path server-side
+    # to Sentry instead, the browser only ever talks to our own domain
+    # (test.slpsoftware.nl), so it is no longer recognized/blocked as
+    # third-party tracking.
+    #
+    # LET OP: de org-/project-id in de proxy_pass hieronder MOET overeenkomen
+    # met de VITE_SENTRY_DSN die voor DEZE omgeving is ingesteld (de
+    # `VITE_SENTRY_DSN` Gitea repository variable voor de testomgeving). Pas
+    # dit aan als je ooit van Sentry-project/DSN wisselt.
+    location /sentry-tunnel {
+        proxy_pass https://o4511795618185216.ingest.de.sentry.io/api/4511795622838352/envelope/;
+        proxy_set_header Host o4511795618185216.ingest.de.sentry.io;
+        proxy_ssl_server_name on;
+    }
+
    location / {
        proxy_pass http://192.168.1.103:80;
        proxy_set_header Host $host;