Howto: Proxying deluge web client to Apache via mod_proxy

[mvoncken]

- the extra parameter for proxying is only available in svn (1.1).
- svn (1.1) does have a built-in option to use https .

[nxmehta]

Also wanted to chime in and say that proxying is working perfectly with the svn version. Thanks for adding this feature!

[lenwar]

(using latest SVN 4247)
Works like a charm except for the status icons... They lack the /deluge/-part in the URL's and give broken image-links.
https://<domain>/pixmaps/all rather than https://<domain>/deluge/pixmaps/all

Thanks for the report, i'll fix that.

Any news on this one?
My webserve's logging is getting big!!

[StelardActek]

I can't seem to get this to work with the ajax template. It just sits there at the loading screen. I figure probably the .js files are referring to the wrong URL.

I tried editing Rpc.js so that on construction it prepended the URL with '/deluge', but while that got me past the loading screen, there were no images, missing CSS, et cetera.

I'm using 1.1.0

[greddyboost]

Hi mvoncken, I believe your new code for easier proxying may have broken deluge's mod_wsgi compatability. I am using the same code from your post http://forum.deluge-torrent.org/viewtop ... sgi#p18985 announcing initial 1.0 webui, which has worked for me as recently as the 1.0.7 release. However, with 1.1.0 installed, going to localhost/deluge/ will now auto-redirect to localhost/deluge/deluge/login, which states "not found." Modifying the webui argument as in

Code: Select all

deluge -u web / &

will give me localhost:8112//deluge and will not solve the mod_wsgi issue. Modifying to

Code: Select all

deluge -u web  &

will still result in the double deluge problem. Let me know what other information you may need. Thank you.

[lozbrown]

Hi

This doesnt work for me, I'm testing this at work where only port 80 is allowed through. i've got the deluge web deamon running

Code: Select all

loz@gravity:~$ ps -ef | grep deluge
loz       1270  1178  1 09:27 pts/0    00:00:01 /usr/bin/python2.5 /usr/bin/deluge -u web /deluge
loz       5386     1  0 Jan21 ?        00:01:38 /usr/bin/python2.5 /usr/bin/deluged -d

and have followed mvoncken's guide to setting up apache. I'm using deluge 1.1 on ubuntu. I'm also using the ajax template.

unfortunatly when i try and load up the web page i get the following java errors.

java-errors.JPG (77.06 KiB) Viewed 12145 times

and then a page that simply says:
Loading...

but nothing else happens
Any ideas how to fix this?

[johnnyg]

Hi

This doesnt work for me, I'm testing this at work where only port 80 is allowed through. i've got the deluge web deamon running

Code: Select all

loz@gravity:~$ ps -ef | grep deluge
loz       1270  1178  1 09:27 pts/0    00:00:01 /usr/bin/python2.5 /usr/bin/deluge -u web /deluge
loz       5386     1  0 Jan21 ?        00:01:38 /usr/bin/python2.5 /usr/bin/deluged -d

and have followed mvoncken's guide to setting up apache. I'm using deluge 1.1 on ubuntu. I'm also using the ajax template.

unfortunatly when i try and load up the web page i get the following java errors.

java-errors.JPG

and then a page that simply says:
Loading...

but nothing else happens
Any ideas how to fix this?

those are javascript errors (java != javascript).
I'd say that the ajax template isn't working in IE.
try using the classic or white template.

[Tenkian]

Can someone explain the new proxying feature? I'm trying to get proxying working using the examples in the first page of this thread and having no luck I edited the httpd.conf file and added the entries, restarted apache but when I browse to the http://homeserver/deluge/ page it changes the url to the internal one http://192.168.0.8:8008

This works internally, but at work it does not as we only allow port 80 through the firewall.

I'm pretty new to all this and am running Ubuntu Server 8.10 with LAMP.all the mod_proxy modules described in the previous posts. I am running deluge as a daemon using the instructions found on these forums with the -u web option.

Thanks.

[draggy]

I would also be interested in the learning how the proxy feature works

[porszem]

Hi mvoncken, I believe your new code for easier proxying may have broken deluge's mod_wsgi compatability. I am using the same code from your post http://forum.deluge-torrent.org/viewtop ... sgi#p18985 announcing initial 1.0 webui, which has worked for me as recently as the 1.0.7 release. However, with 1.1.0 installed, going to localhost/deluge/ will now auto-redirect to localhost/deluge/deluge/login, which states "not found." Modifying the webui argument as in

Code: Select all

deluge -u web / &

will give me localhost:8112//deluge and will not solve the mod_wsgi issue. Modifying to

Code: Select all

deluge -u web  &

will still result in the double deluge problem. Let me know what other information you may need. Thank you.

Any solution for that "Double-Deluge" problem ? (maybe a py script error)
if I use different folder it it dosent work,it is worse