document running app behind reverse proxy

[rade]

A user on the community slack was struggling to access the scope app when it was running behind a reverse proxy, the main challenge being getting websocket traffic through. Eventually they came up with the following working nginx config:

server {
                listen   443;

                ssl     on;
                ssl_certificate   /xxxx;
                ssl_certificate_key  /xxxx;

                location /weavescope/ {
                    proxy_pass http://scope.weave.local:4040/;
                    proxy_http_version 1.1;
                    proxy_set_header Upgrade $http_upgrade;
                    proxy_set_header Connection "upgrade";
                    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                    proxy_set_header Host scope.weave.local;
                }

We should put this in our docs, perhaps as a new section in the installation docs.

Looking at the above config, I believe the scope.weave.local implies that nginx is running inside a container on the Weave Network, but I could be wrong about that. @ekimekim any idea? cc @abuehrle

[tvvignesh]

Hi guys. First of all amazing work with Weave. Any documentation on how to run behind a reverse proxy? While the UI runs, it is not able to load all topologies when running behind nginx as the reverse proxy.

[chandu412]

@tvvignesh does your issue fixed ? I am also trying to put weave behind nginx on kubernetes cluster but its not working.

[tvvignesh]

@chandu412 Not sure if they have the feature now, but I ended up getting a separate subdomain for weavescope for now

[chandu412]

@tvvignesh can you please send me the working configuration that you are using on sub domain