justananon

These trackers work fine on deluge on my home PC, so it seems like it would be something with the docker container?

Anyone? Any ideas?

2021-02-08 08:39:46,543 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2021-02-08 08:39:46,623 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.1.164' 2021-02-08 08:39:46,623 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2021-02-08 08:39:46,634 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2021-02-08 08:39:46,644 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.8.0.2 [debug] Deluge IP is 10.8.0.2 2021-02-08 08:39:47,085 DEBG 'watchdog-script' stderr output: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 1050, in dispatcher return func(*args, **kwargs) File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 1632, in _finishResponse_WAITING self._giveUp(Failure(reason)) File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 1685, in _giveUp self._disconnectParser(reason) File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 1673, in _disconnectParser parser.connectionLost(reason) --- <exception caught here> --- File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 567, in connectionLost self.response._bodyDataFinished() File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 1050, in dispatcher return func(*args, **kwargs) File "/usr/lib/python3.8/site-packages/twisted/web/_newclient.py", line 1306, in _bodyDataFinished_CONNECTED self._bodyProtocol.connectionLost(reason) File "/usr/lib/python3.8/site-packages/deluge/httpdownloader.py", line 75, in connectionLost self.data = self.data.decode(self.encoding).encode('utf8') builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfb in position 319: invalid start byte Trying to add via magnet links from certain trackers is giving me this error (which doesn't seem very helpful). The same magnetlink works fine in the rtorrentvpn docker on the same machine. The delugevpn docker also works on some other trackers. Not sure what more information to get or how to get more thorough logs to see what's going wrong. Edit: Also, if I add via magnet link to rtorrent and then use that torrent file (or just directly download the torrent file to my computer) I can add the torrent fine through the torrent file. So it seems like something with resolving the magnet link?

Have you set an RPC2_PASS variable? If you're using RPC2_AUTH you need to set a password for it

I am trying to use rtorrentvpn with a custom openvpn server and I can get the container running and connecting to torrents, but then after about a minute it disconnects from all peers/trackers, waits about a minute again before reconnecting. I'm not seeing anything about errors in the logs, but I AM seeing that it's trying to "get external IP with name server 'ns1.google.com'" even though I have NAME_SERVERS set to 1.1.1.1,1.0.0.1 which seems weird to me? I have "dhcp-option DNS 1.1.1.1" for my openvpn config as well, so I'm not sure where something is deciding to use google nameservers? The only other suspicious thing I'm seeing is "[server] Inactivity timeout (--ping-restart), restarting" but I'm not sure what kind of timeout that is or what to do about it? The openvpn server and config file work fine with other containers using a different torrent client.