Deluge Daemon doesn't work
Posted: Tue Jul 10, 2018 3:44 am
Hi all,
I have been using deluge (not the daemon) in classic mode on my Windows 8.1 PC for a while, and I saw a guide to make my Raspberry Pi into a torrent box. After following the steps on HowToGeek's website (google "raspi torrent box") I managed to get the daemon and ThinClient running smoothly, or so I thought. I added a test torrent, being the latest NOOBS version, because I know it has seeders, to make sure it was working.
It turns out it wasn't working. At first I figured it was the PureVPN I was using, but then somewhere along the way I decided to run the deluge daemon on my PC and found it wasn't working either. If I went to preferences and enabled classic mode, it worked like a charm on my PC. Using the non-classic localhost-thinclient method, my torrents had a large initial download speed (around 400 or 500 kb/s) but then almost immediately decreased as if the connection was just dropped. I also went to preferences and tested the ports, and with no VPN on my PC it showed the warning triangle. I changed it back to classic mode, and tested the same port and it gave me a green light almost instantly. The same symptoms occur on the Pi, which led me to conclude that the problem lies within deluged.
I wouldn't consider myself a computer noob but I'm not great, and I'm wondering if this issue I'm having is truly a deluge daemon bug or my inexperience.
Any suggestions would be appreciated, and if this is a bug if someone could explain to me how to submit this to the developers that would be fantastic.
Thanks
I have been using deluge (not the daemon) in classic mode on my Windows 8.1 PC for a while, and I saw a guide to make my Raspberry Pi into a torrent box. After following the steps on HowToGeek's website (google "raspi torrent box") I managed to get the daemon and ThinClient running smoothly, or so I thought. I added a test torrent, being the latest NOOBS version, because I know it has seeders, to make sure it was working.
It turns out it wasn't working. At first I figured it was the PureVPN I was using, but then somewhere along the way I decided to run the deluge daemon on my PC and found it wasn't working either. If I went to preferences and enabled classic mode, it worked like a charm on my PC. Using the non-classic localhost-thinclient method, my torrents had a large initial download speed (around 400 or 500 kb/s) but then almost immediately decreased as if the connection was just dropped. I also went to preferences and tested the ports, and with no VPN on my PC it showed the warning triangle. I changed it back to classic mode, and tested the same port and it gave me a green light almost instantly. The same symptoms occur on the Pi, which led me to conclude that the problem lies within deluged.
I wouldn't consider myself a computer noob but I'm not great, and I'm wondering if this issue I'm having is truly a deluge daemon bug or my inexperience.
Any suggestions would be appreciated, and if this is a bug if someone could explain to me how to submit this to the developers that would be fantastic.
Thanks