# \[AYUDA\] No se puede iniciar sesión, aparece el error "BAD CSRF"
**URL:** https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424
**Category:** Support
**Created:** [3 Noviembre, 2016 09:08 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424 "2016-11-03T09:08:33Z")
**Posts on this page:** 12
**Page:** 2
### Author:  [@stephane](https://meta.discourse.org/u/stephane)
#### Post date: [7 Noviembre, 2016 15:35 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/21 "2016-11-07T15:35:12Z")
Hello,
Thank you @sam, the reverse proxy change you suggested worked. I don’t know why my test without it did not reveal it was a proxy problem, or what caused it to appear, but the change worked !
Regards,
Stephane
---
### Author:  [@Firei](https://meta.discourse.org/u/Firei)
#### Post date: [9 Noviembre, 2016 18:45 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/22 "2016-11-09T18:45:34Z")
When we have reinstalled discourse it worked for two days and now we have same problem. It happens with a proxy and without the proxy. User cannot login/post/like/register or anything.
We have updated and rebuild discourse many times and will not work. pls help
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [9 Noviembre, 2016 20:40 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/23 "2016-11-09T20:40:37Z")
As stated above, it’s almost certainly the wrong proxy header, if you are on HTTPS. You could try turning off HTTPS.
---
### Author:  [@Firei](https://meta.discourse.org/u/Firei)
#### Post date: [9 Noviembre, 2016 21:50 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/24 "2016-11-09T21:50:13Z")
@codinghorror we haven’t HTTPS enabled
---
### Author:  [@daxen](https://meta.discourse.org/u/daxen)
#### Post date: [24 Noviembre, 2016 10:48 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/25 "2016-11-24T10:48:09Z")
same here:
updated discourse+plugins yesterday.
today users reported login to discourse not possible - already logged in sessions are working fine.
showing login error: “unbekannter fehler / unknown error”
browser console: “BAD CSRF” and some javascript
fix:
add this to nginx config:
> proxy\_set\_header X-Forwarded-Proto https;
best regards,
daniel
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [24 Noviembre, 2016 11:51 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/26 "2016-11-24T11:51:13Z")
If you have http and the site setting force\_https, expect a bad time
---
### Author:  [@daxen](https://meta.discourse.org/u/daxen)
#### Post date: [24 Noviembre, 2016 13:29 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/27 "2016-11-24T13:29:53Z")
No, we only use https.
it’s all back working again.
---
### Author:  [@csirac2](https://meta.discourse.org/u/csirac2)
#### Post date: [8 Diciembre, 2016 12:02 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/28 "2016-12-08T12:02:17Z")
For what it’s worth, the recent upgrade broke things for us also, in exactly the same way. We have a strictly https-only set of subdomains, and an apache reverse-proxy.
The configuration directive in apache equivalent to the nginx advice above is:
```
RequestHeader set X-Forwarded-Proto "https"
```
Cheers
---
### Author:  [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [25 Agosto, 2019 13:47 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/29 "2019-08-25T13:47:18Z")
A mí también me ocurre lo mismo después de una instalación limpia Y de una restauración (exitosa) desde una copia de seguridad antigua: CSRF incorrecto.
No estoy usando ningún proxy. Sin embargo, accedo al sitio web utilizando una entrada local en mi `/etc/hosts`.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [25 Agosto, 2019 14:07 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/30 "2019-08-25T14:07:14Z")
¿Y el problema desaparece si el servidor se referencia correctamente en el DNS público?
---
### Author:  [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [25 Agosto, 2019 14:34 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/31 "2019-08-25T14:34:09Z")
No lo sé: restauré temporalmente un formulario antiguo en un VPS para extraer cierta información.
Si la falta de registros DNS públicos es la causa, ¿hay alguna solución alternativa?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [3 Julio, 2024 18:03 UTC](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424/32 "2024-07-03T18:03:26Z")
[Previous page](https://meta.discourse.org/t/help-cannot-login-error-shows-bad-csrf/52424.md?page=1)