Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Web Interface Behind Proxies #29

mnaberez opened this Issue Jul 15, 2011 · 6 comments


None yet
5 participants

mnaberez commented Jul 15, 2011

There should be some way to configure a URL prefix for when the web interface is behind a proxy. This has been requested several times on the mailing list.

Related to issue #28

@mnaberez mnaberez closed this in 6ed7a0d Jan 13, 2012

mmoya commented Nov 12, 2013

Hello @mnaberez , is there any update on this?


mnaberez commented Nov 13, 2013

@mmoya Looks like it is still on the TODO.txt list. The web interface in general could use some work. Patches would be welcome.


mnaberez commented Feb 17, 2015

Reopening since this has come up again. Related: #495

@mnaberez mnaberez reopened this Feb 17, 2015

calvin commented Mar 7, 2015

I'm updating the code to support this. I know that there are other implementations (#495 and #28) but what I'm proposing is similar to #372. Once I'm done, I'll create a PR.

yarikdot commented Nov 1, 2015

btw: This nginx configuration worsk for me fine:

location /supervisor {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    # hack the host https://github.com/Supervisor/supervisor/issues/251
    proxy_set_header Host $http_host/supervisor/index.html;
    proxy_redirect off;
    rewrite ^/supervisor(.*)$ /$1 break;

@yarikdot This isn't working for me, at least on v3.3.3, because it's trying to load http://MY_HOST/stylesheets/supervisor.css which is a 404. But even http://MY_HOST/supervisor/stylesheets/supervisor.css is a 404 too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment