Standing up a new Discourse forum as a separate docker container on a dedicated physical server that is already running an existing Discourse forum (which is humming along with no errors). Bootstrapping works without errors and the initial “You’ve successfully installed Discourse!” message appears …

It’s likely a problem with whatever is doing https. How’s that configured?

[image] pfaffman: It’s likely a problem with whatever is doing https. How’s that configured? The web server hosts 4 domains and seven separate web sites, so universal SSL termination is done by HAProxy so I can keep the layers separated and provide caching even to SSL content. The stack is H…

Looking through the Discourse production.log and this is what I see: Started POST "/finish-installation/register" for 2601:2c4:c700:745f:216:3eff:0:11 at 2018-09-12 19:21:26 +0000 Processing by FinishInstallationController#register as HTML Parameters: {"utf8"=>"✓", "authenticity_token"=>"[redacte…

This happens when SSL is badly configured. Most of the times a header is missing from the reverse proxy config.

[image] Falco: a header is missing from the reverse proxy config ^ this - the host header has to remain intact throughout, otherwise encryption can’t be established. Is it all IP/port based behind HAProxy? Out of curiosity why are you using HAProxy in front of Varnish and then nginx behind?

Right, and my first guess was to make sure X-Forwarded-Proto was being appended properly by the reverse proxy—and it is. That’s the annoying thing here—the configuration between the working forum and the new one is identical. And when I say “identical” I mean literally using the exact same processe…

[image] Lee_Ars: They’re both on the same server, so other than the nginx configuration file in sites-available they’re even using the exact same set of configuration files. Everything’s the exact same. The nginx config is pretty short—hard for me to screw that up: Is HAProxy using a SAN cer…

[image] Stephen: Out of curiosity why are you using HAProxy in front of Varnish and then nginx behind? The overall config goals were to 1) encrypt everything and 2) cache everything. These are obviously opposing goals, so the way I went about it was to stratify things: SSL termination first, …

[image] Lee_Ars: getting two separate instances of nginx to work properly with Upstart on ubuntu 14.04 proved to be very difficult and required a lot of screwing around Fair enough, they’re just separate sites though in the same instance of NGINX, it’s quite a common setup. Due to the nature …

[image] Lee_Ars: The only differences between it and the config for the working forum is the server_name directive and the port I’m passing to. Did you enable force_https in the second site?

Dépannage de l'erreur "BAD CSRF" lors de la configuration initiale du site

Soutien Installation

Falco (Falco) Septembre 12, 2018, 9:27 13

This should do it:

./launcher enter app
cd /var/www/discourse
rails c
SiteSetting.force_https = true

Unknow error "BAD CSRF"

Sujet		Réponses	Vues
CSRF login error after upgrade to 2.5.0.beta4 Support	12	1560	Juin 9, 2020
Discourse Integration Nextcloud bad csrf Self-hosting	2	1072	Janvier 18, 2022
Avatar, Site Logos, and Cert Errors Self-hosting unsupported-install	61	4057	Mai 25, 2020
Set up Discourse on a server with existing Apache sites Sysadmins how-to	16	22508	Septembre 18, 2020
Solved: Bad CSRF when trying to use HTTPS Self-hosting	1	1231	Mai 22, 2018

Dépannage de l'erreur "BAD CSRF" lors de la configuration initiale du site

Sujets connexes