Hey, guys, I was trying to post in a topic on my forum but got 403 error. I decided to clear cookies and now I can’t even sign in at all. I’ve updated Discourse with gut pull and ./launcher rebuild app and didn’t help at all. Can you help me please? [изображение]

[изображение] Frey: I’ve enabled force https, but got CSRF error when tried to disable it. Just in case anybody got in the same situation: SSH to server cd /var/discourse ./launcher enter app rails c SiteSetting.force_https = false 6, 7, 8. exit

I am seeing this as well. In the logs, I’m seeing: Started GET "/session/csrf?_=1485544587272" for <ip> at 2017-01-27 19:16:45 +0000 Processing by SessionController#csrf as */* Parameters: {"_"=>"1485544587272"} Completed 200 OK in 1ms (Views: 0.2ms | ActiveRecord: 0.0ms) Started POST "/session" …

This is usually because you are doing an internal proxy but not setting the https forwarding headers in your proxy. (If your site is https)

yeah, I also have seen CSRF-related errors in the console.

[изображение] codinghorror: This is usually because you are doing an internal proxy but not setting the https forwarding headers in your proxy. Oh, indeed! This was fixed by adding to my Apache proxy configuration: RequestHeader set X-Forwarded-Proto "https" Thanks a lot for help. Quite int…

[изображение] Maakuth: Quite interesting that this only begun to happen in the 1.7 series. We didn’t had secure cookies before so that wasn’t a problem.

[изображение] Frey: SiteSetting.force_https = false My users just started seeing “403 Unknown Error” when trying to log in. I followed these instructions - but I’m now getting an error in the admin settings: " * Your website is using SSL. But [force_https](https://movermaker.com/admin/site_se…

Not fun, this is still happening to users - getting “Unknown Error” when trying to log in, and 403 Forbidden error when trying to reset password. I’m now on current Discourse.

Yet again, as said upstream ↑ [изображение] codinghorror: This is usually because you are doing an internal proxy but not setting the proper https forwarding headers in your proxy. (If your site is https)

Hm, k. No idea what that means. So Digital Ocean one-click install has this issue… This appears to be the suggested fix: [изображение] Frey: SSH to server cd /var/discourse ./launcher enter app rails c SiteSetting.force_https = false 6, 7, 8. exit I did that, but users kept having the …

Users can't sign in due to 403 error

Поддержка Самостоятельное хостинг

Frey (Frey) 27.Январь.2017 20:35:20 5

I’ve enabled force https, but got CSRF error when tried to disable it.

Тема		Ответов	Просм.
403 Error when changing any settings after enabling force_https with proxy Support	4	999	31.10.2019
Discourse admin login throws 403 ["BAD CSRF"] error Support	4	1730	24.04.2018
Sudden HTTP 403 errors with Discourse Docker ("BAD CSRF") Bug	4	287	25.12.2024
CSRF login error after upgrade to 2.5.0.beta4 Support	12	1658	09.06.2020
Can't login, reset password or create new account due to 403 Forbidden error Self-hosting	10	4669	13.03.2019

Users can't sign in due to 403 error

Связанные темы