You can clearly see in the example configuration I posted, we did not use wss
wss !== apache2 reverse proxy (it’s only one way to do it, and we don’t use wss)
In fact, we only use ngnix and apache2 reverse proxy configurations using unix domain sockets because:
- I am lazy and like simple, easy to debug configurations.
unix domain socketsare simple and easy to debug- In
nginx, we can switch between the reverse proxy and any container with a symbol link apache2(reverse proxy to container) does not work with a symbolic link so a web server restart is required
However, @Grunskin asked about something which we have not configured yet; doing the reverse proxy on one host and running the container on another host.
When I have time, I’ll test this for both nginx and apache2 in the same data center and see if I can get this to work mounting the remote file system and using a unix socket.
Until then…
Note: IMO, this issue is not germane to either nginx or apache2 which only acts as reverse proxies (but as mentioned, have not yet tested the remote access config, so cannot comment further.).