Deluge Forum

I have a machine running Ubuntu 12.04.2LTS I followed a guide found on the net for the entire server build. There is a section purely on installing Deluge here: http://linuxhomeserverguide.com/mediaserver/deluge.php
Anyway, I ran a sudo apt-get update and apt-upgrade via the CLI this week
Firstly after the update and a subsequent server reboot was that I couldn't connect to the Deluge Daemon from my Mac.
I read somewhere that it could be a version mis-match so I downloaded the latest client version. Still no joy. So I logged into the web interface and saw the daemon was stopped. I started it and that was working again (sorta)
Now my issue is that all my torrents are stuck at download and all say: Tracker Status: "torrent server" Error: Connection Timed out
I have confirmed I am forwarding ports on my router and in Deluge --> Network --> Preferences I have Use Random Ports Checked on incoming na outgoing. I have UPnP, NAT-PMP, Peer Exchange and DHT Selected
Still have no joy with the tracker
So my issues are:
1. I have the daemon auto starting on boot up as per the linuxhomeserverguide but it doesn't actually start after the upgrade anymore
2. none of my torrents are connecting with the tracker

I joined your IRC channel and was being helped by a person on there. This is where we got to which may help:
It is happening for all trackers
Deluge was reading No incoming connections but I did a port test within preferences --> Network Test Active Port, I got a green light and that message disappeared.
I disabled random incoming and outgoing ports and defined the ports in Deluge and on my router
Screenshot attached:

You can see in the image, the ports being forwarded, the ports defined in deluge and the Tracker Status
I can confirm that DNS is working and just to be sure, I changed DNS Servers from opendns to my ISP's own DNS Servers, both appeared fine anyway.
Libtorent version is: 0.15.10.0

Thanks

I have just installed uTorrent on my mac and connected to the same torrent that has stopped in Deluge.

It is downloading perfectly fine, using the same trackers.

This is completely isolated to my Linux Server running Deluge.

So last night I ran:
sudo apt-get remove deluge
sudo apt-get remove deluged
sudo apt-get remove deluge-webui

Rebooted
and ran:
sudo apt-get update && sudo apt-get install deluged deluge-webui

Rebooted and still the same.

Does anybody have any ideas at all???

Hi, I posted to the forums a couple of days ago here: http://forum.deluge-torrent.org/viewtop ... =7&t=42779 I had no reply so I completely reinstalled ubuntu and ran the following commands posted here: http://www.havetheknowhow.com/Install-t ... dless.html If I go to: http://localip:9092 I can't start the daemon. If I SSH in sudo deluge-console and type connect, I get: Failed to connect to 127.0.0.1:58846 with reason: Connection refused Any suggestions?

Thanks to Cas, I now can get into the web by following:
http://dev.deluge-torrent.org/wiki/User ... t%20Job%29

Now my issue is my "thin client" on my mac is not connecting.
I am on my Mac running the Deluge Client. I have setup a new connection: Hostname: IP of my ubuntu machine: Port 58846, Username deluge Password (new password). Pressed add but I have a red light on status.

When I go into deluge-console I get:
[ERROR ] 20:11:34 client:395 RPCError Message Received!
--------------------------------------------------------------------------------
RPCRequest: daemon.login(localclient, 442f280b35276eb6280e476d48df0e86d4bf93ef)
--------------------------------------------------------------------------------
File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 259, in dispatch
ret = component.get("AuthManager").authorize(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 93, in authorize
raise BadLoginError("Password does not match")

BadLoginError: Password does not match

So as a test, I ran: echo "username:password:level" >> ~/.config/deluge/auth with the exact same user as I am logged into and rebooted the server.

It is exactly the same.
For example if I type: connect
I get: >>> connect
Failed to connect to 127.0.0.1:58846 with reason: Password does not match

Cas advised to copy the auth file from the deluge user config to the ssh user config as I am connecting via SSH to get a CLI.

I ran: sudo cp /var/lib/deluge/auth ~/.config/deluge/auth and then sudo reboot

But still no joy when entering deluge-console

So after a huge help from Cas on the IRC Channel, this is what my final problem was:

When running deluge-console I got:
[ERROR ] 22:27:22 client:395 RPCError Message Received!
--------------------------------------------------------------------------------
RPCRequest: daemon.login(localclient, 442f280bdfe36eb6280e47dfe348df0e86d4bf93ef)
--------------------------------------------------------------------------------
File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 259, in dispatch
ret = component.get("AuthManager").authorize(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 93, in authorize raise BadLoginError("Password does not match")
BadLoginError: Password does not match
--------------------------------------------------------------------------------

Running:
ls -lah /var/lib/deluge/core.conf
Returned:
-rw-r--r-- 1 deluge deluge 2.4K Feb 28 22:59 core.conf

The problem is at the time of running this command, that file was modified before I even installed my fresh copy of Ubuntu so that told Cas that the config is not in use.
Cas then went on to say the area of /var/lib/deluge is the home dir
Where I needed to be was:
/var/lib/deluge/.config/deluge which is the config location

Problem is you can't get into: /var/lib/deluge/.config/deluge easily
So firstly I was asked to verify the auth file was actually there:
sudo ls /var/lib/deluge/.config/deluge/auth
It was
Then it was a matter of copying it to my directory:
sudo cp /var/lib/deluge/.config/deluge/auth ~/.config/deluge/auth

Then running:
deluge-console
Gave no error!
I entered the commands:
>>> config -s allow_remote True
Setting allow_remote to True..
Configuration value successfully updated.
>>> config allow_remote
allow_remote: True
C: 91 (200) D: 95.7 KiB (100.0 KiB/s) U: 0.0 KiB (30.0 KiB/s) DHT: 168
exit
As per: http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient

Then final thing to do was set a password inside the hard to get to file:
sudo nano /var/lib/deluge/.config/deluge/auth
I set my U/P as per the above instructions again (user:pass:10)
Ctrl+X > Y

Bam, Deluge thin client (in my case for Mac) was up and running

So happy right now!

So, this helped fix your torrents not connecting to their trackers? I can't seem to get any of my private ones to connect, just wondering if this may help me out at all.
I don't exactly have the sudo ability or access to my server's root directory, though.

Well, I gave up waiting for a reply so I rebuilt my server. HOWEVER. I think you problem will be fixed if you can run the instructions on this page:
http://dev.deluge-torrent.org/wiki/User ... t%20Job%29

Especially this part:

Migration from init.d script

If you followed the old guide to create an init script you need to remove them:

sudo /etc/init.d/deluge-daemon stop
sudo rm /etc/init.d/deluge-daemon
sudo update-rc.d deluge-daemon remove

I was running an older version and after the upgrade it stopped doing exactly what you are experiencing.

However, you will need to run the sudo command to do half of the stuff outlined in that post.