After upgrade to 2.5.0.beta4 I see CSRF errors in the production log: Processing by SessionController#csrf as JSON Completed 200 OK in 1ms (Views: 0.1ms | ActiveRecord: 0.0ms | Allocations: 351) Started POST "/session" for 127.0.0.1 at 2020-05-05 09:25:17 +0000 Processing by SessionController#creat…

Discourse-doctor doesn’t pretend to be able to diagnose a complex setup like yours. It’s comparing only whether local host and the dns return the same value. For your setup it’s expected that they be different. I don’t have any hints on your actual problem, though. Sorry.

Hi, ok, I tested with another account and get the same eror message, seems like logins are blocked totally now and the CSRF error may be the root cause … Any ideas for futher debugging? My app.yml ist pretty standard except that expose: - "127.0.0.1:884:80" # http Incoming requests are forwa…

When registering a new user through oauth2 (Google), I also get a csrf error: Rendered common/_discourse_stylesheet.html.erb (Duration: 0.4ms | Allocations: 206) Rendered application/_header.html.erb (Duration: 0.3ms | Allocations: 142) Completed 200 OK in 23ms (Views: 20.4ms | ActiveRecord: 0.0…

I’ve had exactly the same issue after the upgrade to 2.5.0.beta4 ( Moved site behind proxy, favicon and header not using https anymore - #7 by rossierd ). Were you able to fix the issue? I can imagine that the upgrade came with a new version of nginx (or its config) which leads to this issue (but pur…

Unfortunately the problem is still not solved here. Login fails with “unknown error” and upon each try I see this in the log: root@develd:/var/discourse# tail -f /var/log/discourse-rails/production.log Processing by SessionController#csrf as JSON Completed 200 OK in 1ms (Views: 0.1ms | Allocations:…

Try this : Moved site behind proxy, favicon and header not using https anymore - #12 by rossierd I got successful login with that, but take care where you patch the proxy_pass command. It only works in location @discourse { .. }

ok, just for understanding: we are talking about the nginx inside the “container zoo”, correct? Because, before the update to 2.5.0beta4 there was no requirement for patching this, it just worked smootly.

Yes, if by zoo you mean the container which is running Discourse. You can enter the container with “rails enter app”

We did some further debugging here: the problem starts at the nginx server inside the container. It does not understand the proxy_pass directive and therefore seems to crash, but why: root@develd:/var/discourse# docker ps -a CONTAINER ID IMAGE COMMAND …

I think that you don’t need that proxy_pass right there in your app.yml. My stanza like that looks like this: after_bundle_exec: # This is the magic to get IP numbers transmitted to Discourse # See https://meta.discourse.org/t/last-ip-address-and-action-dispatch-trusted-proxies/50098/3?u=…

CSRF-Login-Fehler nach Upgrade auf 2.5.0.beta4

Unterstützung

Thomas_Rother (Thommie Rother) 7. Juni 2020 um 07:11 6

Leider ist das Problem hier immer noch nicht gelöst. Die Anmeldung schlägt mit „unbekannter Fehler

Thema		Antworten	Aufrufe
Troubleshooting "BAD CSRF" error on initial site setup? Self-hosting	18	6563	30. April 2021
[HELP] Cannot login, error shows "BAD CSRF" Support	28	4391	25. August 2019
Mixed SSL since upgrade Self-hosting	13	876	30. Dezember 2022
403 Forbidden on Logins (started after update to latest version) Support	5	3916	11. November 2016
Discourse admin login throws 403 ["BAD CSRF"] error Support	4	1779	24. April 2018

CSRF-Login-Fehler nach Upgrade auf 2.5.0.beta4

Verwandte Themen