Hi,
Running Deluge 1.3.11 Web UI on headless Ubuntu x64 14.04.2.
Everything works well except for the Proxy (BTGuard) which utilises Socksv5 with auth.
The tracker (regardless of which one) is in error state and the torrent of course will not start no are there any seeders/peers etc.
As soon as I disable the proxy and restart Deluged & Deluge-web I get normal behaviour.
A look at the web.log (/var/logs/deluge) reveals the following:
[WARNING ] 20:29:03 config:361 Unable to open config file /var/lib/deluge/.config/deluge/hostlist.conf.1.2: [Errno 2] No such file or directory: '/var/lib/deluge/.config/deluge/hostlist.conf..............
I have searched the entire server for hostlist.conf (find / -type f -name "hostlist.conf*") but am unable to locate this apparently necessary file. Thinking it maybe a permissions error on /var/lib/deluge/.config/deluge/ , I chmod -R 777 this location and rebooted hoping that Deluge would then be able to create the file.
I also creates an empty hostlist.conf & hostlist.conf.1.2 with the correct permissions to enable Deluge to perhaps write to the file.
Deluge was installed using this guide (http://dev.deluge-torrent.org/wiki/User ... ce/Upstart).
Any help is welcomed.
Deluge:Web UI 1.3.11 - Proxy Socksv5 with Auth
Re: Deluge:Web UI 1.3.11 - Proxy Socksv5 with Auth
Ok,
So I obviously didn't search hard enough and did find a template for a hostslist.conf.1.2.
Can somebody shed some light on this:
Do I edit <deamon-port> to "58846" and is the "cb612435a69cc86f21dd8a4299f81a16c73f9916" the same as pwd_sha1 or pwd_salt in web.conf or is this completely new ID?
So I obviously didn't search hard enough and did find a template for a hostslist.conf.1.2.
Can somebody shed some light on this:
Code: Select all
{
"file": 1,
"format": 1
}{
"hosts": [
[
"cb612435a69cc86f21dd8a4299f81a16c73f9916",
"127.0.0.1",
<deamon-port>,
"",
""
]
]
}
Re: Deluge:Web UI 1.3.11 - Proxy Socksv5 with Auth
[SOLVED] Deluge:Web UI 1.3.11 - Proxy Socksv5 with Auth
I changed proxy service providers. Everything is running as it should. BTGuard didn't offer much support.
I changed proxy service providers. Everything is running as it should. BTGuard didn't offer much support.