Howto: Proxying deluge web client to Apache via mod_proxy

General support for problems installing or using Deluge
k-rog
Member
Member
Posts: 18
Joined: Sat Apr 17, 2010 2:51 pm

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by k-rog »

Do i need to checkout the origin/1.3-prefs-proto branch or origin/master?
johnnyg
Top Bloke
Top Bloke
Posts: 1522
Joined: Sun Oct 28, 2007 4:00 am
Location: Sydney, Australia

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by johnnyg »

origin/master

although we will be branching soon to origin/1.3-stable
k-rog
Member
Member
Posts: 18
Joined: Sat Apr 17, 2010 2:51 pm

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by k-rog »

I have tried to checkout the files in GIt with this manual: http://dev.deluge-torrent.org/wiki/GitRepo. I use this manual for installing: http://dev.deluge-torrent.org/wiki/Installing/Source.

I tried the python setup.py clean -a command. That said i don't have clean system. I ignored that, because i don't know how to clean it. I went on, and it seamed to do allot. Couldn't see any errors.

But when trying to start the webui with the --base parameter, it says it doesnt accept those parameters. What am i doing wrong here?
Cas
Top Bloke
Top Bloke
Posts: 3679
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by Cas »

check the version of deluge-web with --version
k-rog
Member
Member
Posts: 18
Joined: Sat Apr 17, 2010 2:51 pm

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by k-rog »

I ran the --version command. And i still have the 1.2.3 version. So it didn't install.

I saw 1.3-stable is out now, so i'll try to install that. The checkout from git goes just fine.

But when i run the "pyton setup.py clean -a" command it gives me these messages:

Code: Select all

# python setup.py clean -a
running clean
running clean_plugins
Cleaning the plugin folders..
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
running clean
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
'build/lib.linux-i686-2.6' does not exist -- can't clean it
'build/bdist.linux-i686' does not exist -- can't clean it
'build/scripts-2.6' does not exist -- can't clean it
Also checking the version on deluge-web it gives me the following output:

root@XBMCLive:/home/rogier/gitclone/deluge# deluge-web --version
1.3.0-rc1-dev
root@XBMCLive:/home/rogier/gitclone/deluge# /usr/bin/deluge-web --version
1.2.3

the 1.3.0 version is located in /usr/local/bin/deluge-web

Fixed: I changed the path to the deluged and deluge-web files located in /usr/local/bin/. Both started now. :D
cadriel
New User
New User
Posts: 4
Joined: Sat Jun 05, 2010 1:24 am

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by cadriel »

Just a quick note;

This is re: setting up a proxy for Deluge 1.2.3

Deluge web UI proxy works just fine if you only need to proxy the port - not the path.

For example, I run a bunch of virtual hosts on my box, and have a domain mapped to it. This means that I can have "torrent.mydomain.com" proxy to "myipaddress:8112" for example.

Previous examples are fine - just remote the path and have a "/".

--
Craig.
gargouille

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by gargouille »

Hi

I'm running de version 1.3.900-dev of deluge and I have some problem to set the apache proxy.

My configuration of apache is:

Code: Select all

ProxyRequests off

ProxyPass /deluge http://127.0.0.1:8112
ProxyVia On

RequestHeader append X-Deluge-Base "/deluge"
ProxyPassReverse /deluge  http://127.0.0.1:8112
ProxyPassReverseCookieDomain 127.0.0.1 localhost
ProxyPassReverseCookiePath / /deluge
<Proxy *>
  Order deny,allow
  Allow from all
</Proxy>
With this configuration everything work fine except two things. First one, the flag icon for pair (I don't really care for this one).

The other one is that I'm not able to add torrent file. If I add torrent via url is work but I can't upload torrrent file.

Thanks
unaie

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by unaie »

gargouille wrote: The other one is that I'm not able to add torrent file. If I add torrent via url is work but I can't upload torrrent file.

Thanks
Same problem here. But I cannot add torrents via file or via URL.

Error log when I try to upload via webui a torrent file:

Code: Select all

[error] proxy: Error reading from remote server returned by /deluge/json, referer: https://my.website.net:myport/deluge/
[error] client denied by server configuration: proxy:http://127.0.0.1:8112/json, referer: https://my.website.net:myport/deluge/
[error] (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1, referer: https://mydomain:80/deluge
You can see this problem also here by another user:
http://dev.deluge-torrent.org/ticket/1076


Deluge version: 1.3.0-rc1.

Apache2 proxy config:

Code: Select all

ProxyRequests off
        ProxyHTMLExtended on

        ProxyPass /deluge/ http://localhost:8112/
        ProxyHTMLURLMap http://localhost:8112 /deluge
        RewriteEngine on
        RewriteCond %{HTTP_REFERER} http://mydomain:80/deluge/index
        RewriteCond %{REQUEST_URI} ^/torrent/info_inner/.*
        RewriteCond %{REQUEST_URI} !^/deluge/.*
        RewriteRule ^/(.*) /deluge/$1 [PT]
        <Location /deluge/>
           ProxyPassReverse /
           SetOutputFilter proxy-html
           ProxyHTMLURLMap / /deluge/ ec
           ProxyHTMLURLMap /deluge /deluge ec
           ProxyHTMLURLMap ([^*])(\/[^*].*) $1/deluge$2 hRxL
           RequestHeader unset Accept-Encoding
           Order allow,deny
           Allow from all
           ProxyPassReverseCookieDomain 127.0.0.1 localhost
           ProxyPassReverseCookiePath / /deluge/
        </Location>
maxslug
New User
New User
Posts: 3
Joined: Tue Mar 24, 2009 3:03 am

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by maxslug »

Updated simple reverse proxy directions for 1.3 on Page 3, now that deluge-web handles being on a path again. All I had to do was add the Cookie stuff in the reverse proxying et voila. Great job Devs!

http://forum.deluge-torrent.org/viewtop ... 225#p83225

-m
Lexuor76

Re: Howto: Proxying deluge web client to Apache via mod_prox

Post by Lexuor76 »

Hello,
I'm french. I have installed deluged and deluge-web on my ubuntu server. I want to proxying Webui with apache.
I have configured apache with this solution

Code: Select all

ProxyRequests Off

<Location /deluge>
   RequestHeader append X-Deluge-Base "/deluge/"
</Location>

<Proxy *>
   Order deny,allow
   Allow from all
</Proxy>

ProxyPass /deluge http://127.0.0.1:8112
ProxyPassReverse /deluge http://127.0.0.1:8112
ProxyPassReverseCookieDomain 127.0.0.1 localhost
ProxyPassReverseCookiePath / /deluge/
WebUi works on http://www.mydomain.com/deluge but when I try to add torrent the WebUI stay on Torrent Upload.

When I try the same thing on http://www.mydomain.com:8112 it's work correctly.

I have try with "deluge-web -b /deluge" it do the same problem.

Can you help me?
Post Reply