CSRF Verification Failed

[francesco-larghi-duferco]

Self-Hosted Version

24.2.0

CPU Architecture

x86_64

Docker Version

25.0.1

Docker Compose Version

2.24.2

Steps to Reproduce

• Created AWS EC2 Ubuntu 22.04 machine
• Install docker and docker compose
• Install self hosted Sentry following the instructions and creating superuser
• Run docker compose up -d
• Open http://my-local-ip:9000 and login with the created user
• CSRF Verification Failed

Expected Result

Logging in the Web interface.

Actual Result

I'm probably missing some key step, not clear which one.

Event ID

No response

[vadim-vin]

Hello, same problem here.

[DaveKeehl]

+1

[vadim-vin]

https://develop.sentry.dev/self-hosted/

Once you have setup a load balancer or reverse proxy to your Sentry instance, you should modify the system.url-prefix in the config.yml file to match your new URL and protocol. You should also update the SSL/TLS section in the sentry/sentry.conf.py script, otherwise you may get CSRF-related errors when performing certain actions such as configuring integrations.

[francesco-larghi-duferco]

https://develop.sentry.dev/self-hosted/

Once you have setup a load balancer or reverse proxy to your Sentry instance, you should modify the system.url-prefix in the config.yml file to match your new URL and protocol. You should also update the SSL/TLS section in the sentry/sentry.conf.py script, otherwise you may get CSRF-related errors when performing certain actions such as configuring integrations.

Thank you for the insight, but i receive the same error even without having reverse proxy in front of Sentry (Nginx or AWS ALB).
My idea is to eventually use them, but also just for testing purposes if I type in the private IP of the machine on port 9000, without having other reverse proxy running on the machine, I still got the same error.

Should I try directly configuring the subdomain, certificates and reverse proxy and changing accordingly the configuration? I was excepting it to work without it for testing.

[vadim-vin]

hi @francesco-larghi-duferco
I set system.url-prefix: to the machine's actual IP address and port (I also don't have any proxy) in sentry/config.yml and it appears to start working.

[francesco-larghi-duferco]

hi @francesco-larghi-duferco I set system.url-prefix: to the machine's actual IP address and port (I also don't have any proxy) in sentry/config.yml and it appears to start working.

Hello again! Yes, you are right.
Nevertheless, it's not clear to me why. Is it a bug maybe? It looks like that field should be assigned only in case of domain changes or reverse proxy indeed.
Anyway thanks for your help on that!

[1021683053]

hi @francesco-larghi-duferco I set system.url-prefix: to the machine's actual IP address and port (I also don't have any proxy) in sentry/config.yml and it appears to start working.

Thank you.You were right.

[hubertdeng123]

Is everyone here using the nightly image of self-hosted Sentry? Meaning 24.2.0.dev?