Closed agateblue closed 5 years ago
I may have an idea for this but I won't be able to test for a few days (or if it will even work).
Worst case scenario: we have an env variable set like USE_REVERSE_PROXY=true
which will use a separate funkwhale_proxy.conf
The current
funkwhale_proxy.conf
is:It means it will consider Funkwhale as served behind the server and protocol used to contact the proxy. This works well when the container is exposed directly to the internet.
However, in a
client -> reverse proxy -> funkwhale container
scenario, this breaks, because if you haveproxy_pass http://localhost:5000
in your proxy conf, the values ofX-Forwarded-Proto $scheme;
andproxy_set_header X-Forwarded-Host $http_host;
will respectively behttp
andlocalhost
, regardless on how the proxy itself is accessed over the internet.One workaround is to replace this funkwhale_proxy.conf when running the container behind a proxy:
websocket support
proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade;