Page 1 of 1

Bind deluge webui port 80 - Blank page

Posted: Thu Nov 25, 2010 2:43 pm
by dudumomo
Hi there,
I'm trying to blind deluge to port 80 but as I'm running already a server on this port, I've decided to use the ProxyPass option in a vhost.
As I prefer running through HTTPS, I've used my vhost 443 that I already use for bind AjaxTerm (SSH with a web interface)

But whereas AjaxTerm works, Deluge doesn't...I only get a black page but the tab name is correct (ie, Deluge: Web UI 1.3.1)

Here is my vhost

Code: Select all

<VirtualHost *:443>
        SSLEngine On
        SSLCertificateFile /etc/ssl/private/localhost.pem

     ProxyRequests Off
        <Proxy *>
                AuthUserFile /srv/ajaxterm/.htpasswd
                AuthName EnterPassword
                AuthType Basic
                require valid-user

                Order Deny,allow
                Allow from all
        </Proxy>
        ProxyPass /ssh/ http://localhost:8022/
        ProxyPassReverse /ssh/ http://localhost:8022/
        ProxyPass /deluge/ http://localhost:8112/
        ProxyPassReverse /deluge/ http://localhost:8112/
</VirtualHost>
But if I set ProxyPass for deluge to the root folder ie:

Code: Select all

ProxyPass / http://localhost:8112/
ProxyPassReverse / http://localhost:8112/
It works...but obviously I'm not able to use any other 443 services.

Any idea why ?

Thank you !

Re: Bind deluge webui port 80 - Blank page

Posted: Mon Nov 29, 2010 4:10 pm
by dudumomo
I still haven't figured out why it doesn't work....
Any highlight ?

Re: Bind deluge webui port 80 - Blank page

Posted: Mon Nov 29, 2010 5:40 pm
by Cas
I am not sure if this is relevant but did you read this: http://dev.deluge-torrent.org/wiki/Faq# ... :80inLinux

Re: Bind deluge webui port 80 - Blank page

Posted: Tue Nov 30, 2010 2:22 pm
by dudumomo
Well I already have a server on the port 80 so I prefer using the port 443 with a redirection like www.mydomain.ltd/deluge

I don't understand why it doesn't work...

Re: Bind deluge webui port 80 - Blank page

Posted: Fri Dec 10, 2010 3:52 pm
by olesk
Just a quick check: you realize you need a trailing slash after that address right?

I.e when doing reverse proxying the two addresses www.mydomain.ltd/deluge and www.mydomain.ltd/deluge/ point to two completely different places (one being proxied, the other most likely to /var/www/deluge on an Ubuntu/Debian installation).