Hello all, I have installed Discourse on my server, and it has ran a long good time, without any troubles. However after the latest update, I have found that all of the user accounts are failed to login, including admin ones. After awhile I was suspecting it is a plugin issue, therefore I removed…

If you are running a reverse proxy 99.999% the issue is that you are not passing headers right to discourse. [image] Error 403 when trying to add articles or change any options Support Holy moly, finally! I need to add a simple line to my nginx config: …

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.

Hmm, did you try upgrading at the command line? Please SSH into your server and run: cd /var/discourse git pull ./launcher rebuild app

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.

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

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:

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?

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 …

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 b…

@codinghorror @sam Will that be an upstream bug?

[AIDE] Impossible de se connecter, erreur « BAD CSRF » affichée

Soutien

lifehome Novembre 4, 2016, 4:02 3

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

Sujet		Réponses	Vues
Can't Login to Discourse - CSRF Token Authenticity Support	0	3498	Décembre 11, 2016
CSRF login error after upgrade to 2.5.0.beta4 Support	12	1777	Juin 9, 2020
Discourse admin login throws 403 ["BAD CSRF"] error Support	4	1780	Avril 24, 2018
Sudden HTTP 403 errors with Discourse Docker ("BAD CSRF") Bug	4	378	Décembre 25, 2024
Authentication not working after a recent update Support	2	1979	Octobre 26, 2016

[AIDE] Impossible de se connecter, erreur « BAD CSRF » affichée

Sujets connexes