Closed voidsp-rick closed 1 week ago
Same thing for me after a fresh installation. Do you find a solution?
When I made requests using the Sentry java client, I found out, that sentry relay doesn't log any requests.
I don't know why Traefik doesn't route traffic to sentry-relay, I will debugging this issue further.
A simple workarround I found was to issue a new Subdomain (for example sentry2.sentry.local) and configure it as the sentry dsn in your clients. You'd have to write your own ingress and add this domain to the CSRF Trusted Origin setting.
This is the ingressroute that works for me
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
name: sentry-ingressroute
namespace: sentry
annotations:
kubernetes.io/ingress.class: traefik
spec:
entryPoints:
- websecure
routes:
- kind: Rule
match: Host(`sentry2.redacted.tld`)
services:
- kind: Service
name: sentry-relay
port: 3000
namespace: sentry
tls: {}
One cause of this is that Traefik v3 by default does not respect regular expressions in k8s Ingress objects. I was able to fix this by setting --core.defaultRuleSyntax=v2
in Traefik and then things started working as expected.
The traefik.ingress.kubernetes.io/router.pathmatcher
and traefik.ingress.kubernetes.io/router.rulesyntax
(the latter not yet shipped) ingress annotations may also help here. I intend to investigate these once the next version of Traefik is released.
@zvickery thanks a lot --core.defaultRuleSyntax=v2
fix same problem
@zvickery - Thanks a lot for sharing the workaround! I had the exact same issue after upgrading to Traefik v3, and switching to the v2 rule syntax helped fix it! 🙏🏻
With Traefik v3.1.3 I have confirmed that the below Ingress annotation also works. This allows setting v2 style path matching only for this Ingress and not globally:
annotations:
traefik.ingress.kubernetes.io/router.rulesyntax: v2
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Description
I'm encountering a persistent issue with CSRF verification in my Sentry deployment using the Helm chart. Despite configuring
CSRF_TRUSTED_ORIGINS
and other relevant settings, I continue to receive CSRF verification errors.Environment
Configuration Details
Argo CD Application YAML
Ingress Configuration
Issue Details
CSRF_TRUSTED_ORIGINS
and related configurations, I am consistently receiving CSRF verification errors.403 Forbidden (Referer checking failed - no Referer.)
Steps Taken
Configuration Verification:
Ingress Configuration:
Pod Restarts:
Error Logs
Sentry Web Log:
Sentry Worker Log:
My domain is served behind cloud flare with proxy full mode. UI is accessible but with the same error.
Response: