Today I tried adding a second server to host one of our discourse instances. The container is configured to use an external redis, postgres, and storage servers - its web-app only. Thus far we’ve been running the single server sites behind HAProxy without issues. When running with 2 servers behind H…

Thanks to the hint from @Falco I tried adding the following to my container config and now things are working as expected: - volume: host: {{ discourse_nas_path }}/assets guest: /var/www/discourse/public/assets

@Falco Hi thanks for the reply. The two servers use shared storage over NFS. In my container config I have this volumes: - volume: host: {{ discourse_nas_path }}/data guest: /shared - volume: host: {{ discourse_nas_path }}/logs guest: /var/log Each container stores its …

[immagine] foozmeat: When running with 2 servers behind HAProxy we see quite a few 404s from nginx for JS files. Besides adding and removing backends in Haproxy what have you done to test it? Does your Haproxy config do random backends or affinity? Is the 404 logged by Haproxy? Is the 404 lo…

Esecuzione di 2 host dietro haproxy fallisce con 404 casuali

Supporto Installazione

Falco (Falco) 6 Maggio 2020, 11:42pm 3

If you are running more than one web container you need something to ensure both have access to the static files.

The easiest path is Using Object Storage for Uploads (S3 Clones)

4 Mi Piace

Argomento		Risposte	Visualizzazioni
Use HAProxy and Varnish with Discourse Sysadmins how-to	3	5171	Aprile 21, 2015
Sorry for another Haproxy/Apache port 80 post but Self-hosting	5	1527	Giugno 8, 2024
Sharing shared volumes Support	11	1021	Novembre 9, 2020
Troubleshooting "BAD CSRF" error on initial site setup? Self-hosting	19	6329	Luglio 18, 2024
App.yml shared volumes for a two website setup Self-hosting	5	1245	Luglio 3, 2019

Esecuzione di 2 host dietro haproxy fallisce con 404 casuali

Argomenti correlati