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? [image]

[image] 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 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" for at 2017-01-27 19:16:46 +0000 Processing by SessionController#create as */* Parameters: {"login"=>"username", "password"=>"[FILTERED]"} Can't verify CSRF token authenticity Rendered text template (0.0ms) Filter chain halted as :verify_authenticity_token rendered or redirected It has been like this for a few days, I think since updating to 1.7.0. I’ve installed the 1.7.1 fix but it didn’t help. Trying now with the 1.7.2, but by the looks of the diff, this issue isn’t fixed there. edit: Yep, no change with 1.7.2.

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.

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

[image] 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 interesting that this only begun to happen in the 1.7 series.

[image] 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.

[image] 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_settings/category/all_results?filter=force_https) is not yet enabled in your site settings." I am using the Digital Ocean app setup with nothing custom, and ‘v2.0.0.beta2 +170’. Is this because I’m using a beta version?

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 ↑ [image] 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: [image] 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 same issue. How do I check if I am ‘doing an internal proxy’? We’re using Cloudflare + Digital Ocean.

Users can't sign in due to 403 error

Product Support Self-hosting

Frey (Frey) January 28, 2017, 6:11am 8

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

Topic		Replies	Views
403 Error when changing any settings after enabling force_https with proxy Product Support	4	1065	October 31, 2019
Discourse admin login throws 403 ["BAD CSRF"] error Product Support	4	1798	April 24, 2018
Sudden HTTP 403 errors with Discourse Docker ("BAD CSRF") Bug	4	413	December 25, 2024
CSRF login error after upgrade to 2.5.0.beta4 Product Support	12	1823	June 9, 2020
Can't login, reset password or create new account due to 403 Forbidden error Self-hosting	10	4898	March 13, 2019

Users can't sign in due to 403 error

Related topics