Bug: ws requests don't come through in apache2 reverse proxies.

[Speiger]

Steps to reproduce the behavior

• 1: Install focal board using git clone and running the docker command.
• 2: setup the apache2 config
• 3: open the board and look at network console and see that the ws/wss connection fails
  

Apache2

<VirtualHost *:80>
	ServerName myURL.com
	Redirect permanent / https://myURL.com/
</VirtualHost>

<VirtualHost *:443>
	ServerName myURL.com
	ProxyPreserveHost On
	
	AllowEncodedSlashes NoDecode
	SSLEngine On
	ProxyPass /ws/ ws://127.0.0.1:8082/
	ProxyPassReverse /ws/ ws://127.0.0.1:8082/
	
	<Location />
		Require all granted
		ProxyPass http://127.0.0.1:8082/
		ProxyPassReverse http://127.0.0.1:8082/
		ProxyPassReverseCookieDomain 127.0.0.1 myURL.com
	</Location>
	
	SSLCertificateFile /etc/letsencrypt/live/myURL.com/cert.pem
	SSLCertificateKeyFile /etc/letsencrypt/live/myURL.com/privkey.pem
	SSLCertificateChainFile /etc/letsencrypt/live/myURL.com/chain.pem
	ProxyPass / http://localhost:8082/ nocanon
	ProxyPassReverse / http://localhost:8082/
</VirtualHost>

Expected behavior

That the focal board setup works with apache2 and is responsive and doesn't require a refresh for any change done.
A best solution would be that a script for apache2 is provided.

Edition and Platform

• todays git patch and ubuntu 22.04

[Roukurai]

Have you been able to get this to work? I constantly get one error or another. At some point I got that I was not using the upgrade to the ws, however, it was setup.

I've attempted several different things but can't get the reverse proxy to work.

[Speiger]

@Roukurai nope planning to switch to NGix because this will not work apache reverse proxy and on top of that it looks like that the apache reverse proxy is so outdated/not supported that it is better to switch to something else.