NGDM

Have you ever found a reason/solution to this? I'm encountering this issue also.

Just curious if this issue was already resolved in some way?

I'm running your latest docker image on my Synology D916+ and am now receiving following error message in the supervisord.log: FATAL: kernel too old I'm not using Wireguard or anything. Possible something you added in this latest one isn't compatible with our older kernel? Edit: returned to 2.0.4.dev38_g23a48dd01-3-01 and all is good again. Let me know if I can test anything.

Hi @gergtreble , @binhex Did you guys find a solution to this issue in the mean time? I'm also encountering this problem (with one of my private trackers, for the moment) and looking for a solution. I'm open to debug, troubleshoot or help finding a practical solution for this. Do you have a non-dev build-tag which I could use to run as a seperate instance for this tracker? Thanks in advance!

Hi I just switched from 1.3.15 to the new 2.0.4.dev38 version of Deluge client in your image. Everything is running smoothly and I found replacements for all my previous plugins. Only thing which doesn't work are the tracker icons which should show next to the tracker name. I found this thread which suggested renaming the icons (.ico) to .png, but that didn't help. Not sure if you had this issue before (couldn't find anything in this topic)?

I noticed the following in your logs: 2019-08-02 15:41:04,591 DEBG 'start-script' stdout output: [info] Adding 192.168.0.1/24 as route via docker eth0 2019-08-02 15:41:04,593 DEBG 'start-script' stderr output: RTNETLINK answers: Invalid argument  Not sure, but is your LAN NETWORK parameter correctly set? What's your local IP address? Anyone got an answer for my question?

Hi @binhex Been a year since I've first set up your DelugeVPN container and it's been great! Haven't had any major problems and if a problem occured it got resolved pretty easily. Now I'm seeing something weird in the logs that doesn't really seem to cause any issues, but I'm curious if it's known. In the supervisord.log I find this error sometimes: 2019-07-31 00:24:58,530 DEBG 'watchdog-script' stderr output: Unhandled error in Deferred: 2019-07-31 00:24:58,531 DEBG 'watchdog-script' stderr output: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/twisted/protocols/policies.py", line 120, in dataReceived self.wrappedProtocol.dataReceived(data) File "/usr/lib/python2.7/site-packages/deluge/ui/client.py", line 179, in dataReceived d.callback(request[2]) File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 460, in callback self._startRunCallbacks(result) File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 568, in _startRunCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 654, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/usr/lib/python2.7/site-packages/deluge/ui/sessionproxy.py", line 147, in on_status self.torrents[torrent_id][0] = t exceptions.KeyError: u'eed0984ee5d0d9d150d6b1a0e7e57e0b8ef7e61e' Haven't seen this issue discussed in the forum yet. Do you have any clue what could be causing this?

So...I found a comment on reddit: Followed this guy's explanation and voila: Not sure if this does more bad than good, but it seems to work. Anyone with experience with this kind of tinkering to libtorrent?

My ISP is not known to partake in traffic shaping. In the past the VPN has always worked well (on other machines: Windows, Mac). This is the first time I notice slower speeds on PIA. Normal connection on Windows (same network): VPN (France) on Windows:

I tried disabling UPnP and NAT-PMP (not sure if those are necessary on a VPN connection?) Port is open.

I'm using the IP version of the OVPN, that's why this error is shown. binhex actually made a new image which made it possible to use these files and make the portfowarding possible, even though it still gives an error message in the logs. As you can see in the quote below. I also double checked if the port was open with the open port check tool + my trackers tag me as connectable. I also tried different regions (Swiss, CZ, France) and all of them cap at 3MBps. Must be something else

Yup, I confirm, 200/20 (down/up) Mbps or 25/2.5 MBps. So 24 Mbps or 3 MBps is not acceptable even through a VPN.

Hi, me again I'm noticing limited download speeds on my torrents. I max out at 3MB/s on a 25MB/s line. My port is forwarded and open (checked on https://www.yougetsignal.com/tools/open-ports/) On my previous installation on the same network which had no VPN I reached the 25MB/s marker without a hitch. Does my logfile show any weird behaviour? I tried searching for a solution on the forum but I couldn't find a search tool for the topic itself (could this be added to the forum?) Thanks in advance supervisord.log

Awesome! Thanks for the quick update. Pulled the latest image and it fixed both problems. For the icons I had to clear the icons folder under config/, restart the container and clear the website data on my browser. The IP files work as expected too port gets forwarded and set in Deluge. Until the DNS problem gets resolved, I'm happy with this solution. Thanks again

Hi guys, new user here Setup went well except for the Port Forwarding part. I'm also experiencing this on my Synology with a fresh install. I tried using the IP version of the OVPN files (https://www.privateinternetaccess.com/helpdesk/kb/articles/what-s-the-difference-between-the-ovpn-files). It seems to solve the DNS issue, but the supervisord.log says the server (CZ in this case, also tried Swiss) doesn't support PF. 2018-08-14 21:00:52,159 DEBG 'start-script' stdout output: [warn] PIA endpoint '89.238.186.228' doesn't support port forwarding, DL/UL speeds will be slow [info] Please consider switching to an endpoint that does support port forwarding, shown below:- I'm in the process of migrating all my torrent files to the new installation so it's not an urgent issue for me, but very keen for an anwser. If I can help in any way, shout Thanks for the support! Edit: One more thing, I'm noticing the tracker icons in deluge aren't displaying well. They seem to large to show. Seems to be related to this: https://dev.deluge-torrent.org/ticket/2715 Can I fix this myself?