Deluge Forum

Posted: **Wed Oct 22, 2014 8:16 pm**

Hi, I'm trying to get deluge set up with an nginx reverse proxy, but so far I'm just testing deluge-web on its own without nginx. When I set the --base option to "/deluge" and navigate to /, I get a blank page and when I go to /deluge, which is where I'd expect to see the web ui, I see "No Such Resource.\n No such child resource" without any output from deluge-web (with loglevel of debug). This is my webui config (web.conf)

Code: Select all

{
  "file": 1,
  "format": 1
}{
  "port": 8826,
  "enabled_plugins": [],
  "pwd_sha1": "xxxxxxxx",
  "theme": "gray",
  "show_sidebar": true,
  "sidebar_show_zero": false,
  "pkey": "ssl/daemon.pkey",
  "https": true,
  "sessions": {
    "xxxxxxxx": {
      "login": "xxxxxxxx",
      "expires": xxxxxxxx,
      "level": 10
    }
  },
  "base": "/deluge",
  "pwd_salt": "xxxxxxxx",
  "show_session_speed": false,
  "first_login": false,
  "cert": "ssl/daemon.cert",
  "session_timeout": 3600,
  "default_daemon": "",
  "sidebar_multiple_filters": true
}

After the initialization, I only get this from the log with no indication of what happens to requests regardless of whether I try to access / or /deluge:

Code: Select all

[INFO    ] 15:08:27 server:681 serving on 0.0.0.0:8826 view at https://127.0.0.1:8826
[DEBUG   ] 15:08:31 server:589 Enabling SSL using:
[DEBUG   ] 15:08:31 server:590 Pkey: ssl/daemon.pkey
[DEBUG   ] 15:08:31 server:591 Cert: ssl/daemon.cert
[DEBUG   ] 15:08:43 server:589 Enabling SSL using:
[DEBUG   ] 15:08:43 server:590 Pkey: ssl/daemon.pkey
[DEBUG   ] 15:08:43 server:591 Cert: ssl/daemon.cert
[DEBUG   ] 15:08:43 server:589 Enabling SSL using:
[DEBUG   ] 15:08:43 server:590 Pkey: ssl/daemon.pkey
[DEBUG   ] 15:08:43 server:591 Cert: ssl/daemon.cert
[DEBUG   ] 15:08:43 server:589 Enabling SSL using:
[DEBUG   ] 15:08:43 server:590 Pkey: ssl/daemon.pkey
[DEBUG   ] 15:08:43 server:591 Cert: ssl/daemon.cert
[DEBUG   ] 15:08:43 server:589 Enabling SSL using:
[DEBUG   ] 15:08:43 server:590 Pkey: ssl/daemon.pkey
[DEBUG   ] 15:08:43 server:591 Cert: ssl/daemon.cert
[DEBUG   ] 15:08:43 server:589 Enabling SSL using:
[DEBUG   ] 15:08:43 server:590 Pkey: ssl/daemon.pkey
[DEBUG   ] 15:08:43 server:591 Cert: ssl/daemon.cert

Also, I run deluge like this:

Code: Select all

sudo -u deluge deluge-web -L debug

Posted: **Sat Nov 08, 2014 9:03 am**

Posted: **Sat Nov 08, 2014 2:09 pm**

There is a good guide here based on forum topics: http://allskyee.blogspot.co.uk/2013/12/ ... -plex.html

Posted: **Sun Nov 09, 2014 12:23 am**

Thanks a lot! Is there a reason why --base option is not respected? Am I misinterpreting the purpose of the --base option? I would assume that using the --base option would make reverse proxying quite easy.

I'll see if I can translate the apache config to an nginx equivalent!

Thanks!

Posted: **Sun Nov 09, 2014 3:46 am**

After much wrestling with no result, I filed a bug report: http://dev.deluge-torrent.org/ticket/2677

Posted: **Tue Mar 24, 2015 11:34 pm**

I wanted to make sure that this was out there, because I banged my head against the wall for too long trying to make this work. I also could not for the life of me use the --base option at all. Putting that

Code: Select all

     "base": "/deluge",

(with or without trailing slash) into web.conf gave me a completely blank screen at http://localhost:8112 (even though somehow the page title "Deluge Web UI" came through), and a "No resource // No child resource" error when I navigated to http://localhost:8112/deluge. That was never going to work to set up the reverse proxy because the target URL never worked.

What eventually worked for me was the realization that SLASHES REALLY MATTER... but only for this particular proxy pass. Whereas before I could get away with this:

Code: Select all

        location /sickrage {
                proxy_pass http://localhost:8081;
                include                 proxy-control.conf;
        }

now it requires a couple really crucial slashes:

Code: Select all

        location /deluge {
                proxy_pass              http://localhost:8112/;
                proxy_set_header        X-Deluge-Base "/deluge/";
                include                 proxy-control.conf;
        }

Again, note carefully the trailing slash in proxy_pass and in X-Deluge-Base. The proxy now works great, without the --base option whatsoever.

This is proxy-control.conf, for those who want the whole config I'm using:

Code: Select all

proxy_connect_timeout   59s;
proxy_send_timeout      600;
proxy_read_timeout      36000s;  ## Timeout after 10 hours
proxy_buffer_size       64k;
proxy_buffers           16 32k;
proxy_pass_header       Set-Cookie;
proxy_hide_header       Vary;

proxy_busy_buffers_size         64k;
proxy_temp_file_write_size      64k;

proxy_set_header        Accept-Encoding         '';
proxy_ignore_headers    Cache-Control           Expires;
proxy_set_header        Referer                 $http_referer;
proxy_set_header        Host                    $host;
proxy_set_header        Cookie                  $http_cookie;
proxy_set_header        X-Real-IP               $remote_addr;
proxy_set_header        X-Forwarded-Host        $host;
proxy_set_header        X-Forwarded-Server      $host;
proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
proxy_set_header        X-Forwarded-Port        '443';
proxy_set_header        X-Forwarded-Ssl         on;
proxy_set_header        X-Forwarded-Proto       https;
proxy_set_header        Authorization           '';

proxy_buffering         off;
proxy_redirect          off;

Deluge Forum

[webui] --base option shows blank page or "no response"

[webui] --base option shows blank page or "no response"

Re: [webui] --base option shows blank page or "no response"

Re: [webui] --base option shows blank page or "no response"

Re: [webui] --base option shows blank page or "no response"

Re: [webui] --base option shows blank page or "no response"

Re: [webui] --base option shows blank page or "no response"