-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSRF verification failed. Request aborted. #5936
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
See https://docs.djangoproject.com/en/3.2/ref/csrf/#how-it-works for documentation on CSRF protection. |
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
@gardenappl That is different error, you most likely have disabled sending referrer in Firefox, check https://wiki.mozilla.org/Security/Referrer |
Right, it looks like one of my extensions changed that setting, thanks for pointing that out. Weird that Troubleshooting Mode didn't revert that setting to the default. |
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
I followed the instructions here and am unable to login using my admin credentials. I can see that the login POST request passes the CSRF token. I see the django docs are linked above but I'm not really sure what information I should be using from there? This is weblate 4.14.1. |
@meunierd Most like it's unrelated, unless you get the same error. CSRF token is passed with every POST request. |
I had the same issue. Adding |
Hi, I ran docker-compose with this configuration
But when I try to login or register, I get this error
Is there a problem with the configuration or is the problem somewhere else?
The text was updated successfully, but these errors were encountered: