[AYUDA] No se puede iniciar sesión, aparece el error "BAD CSRF"

Soporte
1

Hola a todos,

He instalado Discourse en mi servidor y ha funcionado sin problemas durante mucho tiempo. Sin embargo, tras la última actualización, he descubierto que todas las cuentas de usuario, incluidas las de administrador, no pueden iniciar sesión.

Después de un tiempo, sospeché que podría ser un problema con un complemento, por lo que eliminé todos los complementos y ejecuté ./launcher rebuild app para probar con la versión pura y original, pero sin éxito. En la situación actual, parece que nuestro sitio está en modo solo lectura y no se puede realizar ninguna acción más allá de leer los hilos.

Al enviar cualquier formulario de inicio de sesión, aparece este mensaje y no tenemos idea de qué significa.

985×468 47.2 KB

El sitio está ubicado en https://discuss.stickyricelove.com y somos una organización sin fines de lucro dedicada a educar y promover la educación sexual en Hong Kong, para adolescentes que buscan resolver sus dudas y preguntas.

Esperamos con mucha ansias una respuesta muy pronto.:weary::sob:
Gracias.

2

It looks like one of your plugins is not compatible with the current version of Discourse. I suggest removing all third party (non-official) plugins and rebuilding.

3

It is already a clean build without plugins, only with the docker_manager. Should I remove that too?

4

Hmm, did you try upgrading at the command line?

Please SSH into your server and run:

cd /var/discourse
git pull
./launcher rebuild app
5

I have already tried this many many times, and it still shows the same error.

I’m now removing the docker_manager and rebuilding it.

6

Is this an install that followed our official install guide? Any errors in the rebuild?

7

Yes I have followed the exact steps carefully, and it’s a “no” for the errors. It builds smoothly that I can’t even tell what has gone wrong.

Will extract the backups and rebuild the VPS if nothing works out today. :sob:

8

Do you have this behind cloudflare or anything like that? @sam do you see anything in the pictured JS console errors that would indicate what is the issue?

9

We have consider that issue too, therefore a month ago we completely disabled all Cloudflare features, will also consider moving out Cloudflare since it brings enough troubles for us.

Will there be any override that I can force my current session as an admin? In that way I can get into the backend and see what’s the log telling :worried:

10

Hello,

I manage a small discourse forum for an opensource project and we have something that looks like the same problem. The error is exactly the same with google chrome, but is different with firefox : the login dialog works normally, the page is refreshed but it does not log me in (screenshots bellow).

It’s a dedicated host, and it doesn’t change much if I rebuild with beta, previous beta, or “tests-passed”. We don’t use cloudfare, but it’s behind a nginx reverse proxy (nothing too fancy). The discourse container is http, but nginx serves it in https through the reverse proxy, if that makes any difference.

I would appreciate any idea if there is something I can try.

Regards,

Stephane

image.png1126×740 86.7 KB

image.png979×741 112 KB

11

@codinghorror @sam Will that be an upstream bug?

12

We have no repro of this, so it is likely something about your local setup.

13

Estamos reconstruyendo el VPS e instalando una nueva instancia de Discourse. A continuación se muestra lo que ocurrió y se quedó colgado un momento:

945×186 64.6 KB

14

Is there a solution? We have the same problem…

15

It appears to us an upgrade issue. We have backup away the data, and performed a clean install and backup restoration.

However other than that, I have no idea what caused this issue.

16

Hello. I tried to run it without the nginx reverse proxy and it did not resolve the issue. Will run a reinstall tomorrow except if anyone think about something that could help by that time.

I noticed that by default, the launcher rebuild script was checking out the “tests-passed” version. Is it a bit dangerous ? should it be beta ? When I update from the admin web screen, it update to the most recent beta instead ?

I had to launch a rebuild before the problem appeared because the host ip from inside the container changed. The host is also my mailserver, and the mail config was in app.yml.

Is it possible that with the rebuild, I updated to a version that somehow corrupted the config ? (I launched the rebuild around 11/02/2016 07:00 PM if that’s any help).

Regards,

Stephane

19

In future if you feel your issue was not resolved, flag to reopen topic and DON’T accept an answer on the topic.

20

If you are running a reverse proxy 99.999% the issue is that you are not passing headers right to discourse.