Does anyone have a simple solution for creating new torrents?  I have been trying to get the console/ GTK to work and add that way, but I always get a password mismatch message.

 

Either create new from WEBUI, plugin, or otherwise.

Hello, I am trying to get this setup on the --net=br0 instead of bridge, but every time I switch it to br0 I am unable to access the webui or any other docker webui that use dulugevpn privoxy. Am I missing something?

noticed i no longer can add large torrents manually?

 

Edited November 15, 20223 yr by Tolete

On 11/14/2022 at 11:33 PM, Tolete said:

noticed i no longer can add large torrents manually?

 

firewall rules 'this is the way'

@binhex hate to tag you directly but I am still struggling to access the Deluge webUI remotely.  Is the VPN setup for split-tunnel so the webUI can operate on my local IP and the Deluge daemon can operate on the VPN IP?  Seems like not - is there a way to set this up?

Also, as I have asked and @Dschnell89 - is there a way to configure the Deluge GTK client?  I have tried to set this up while on my LAN and have failed.  The webUI works fine on the LAN - ideally I'd like to be able to access both remotely, but some remote access

(whether via the client or webUI) is really needed!

 

Thanks!!

Been battling deluge all morning.

 

My Deluge Web UI was prompting me for a password as is usual, and wouldn't accept my usual password.

 

Some how deluges web ui password had defaulted back to 'deluge'. However, when i tried to reset the password back to my previous peronsal password in the web ui, deluge would hang and crash and need a reboot to become responsive.

 

Seemed that my web.conf file was rammed full of stale sessions as the web.conf file had bloated up to 40MB in size and i think deluge was crasing due to it. Since deleting 99% of the stale sessions in my web.conf deluge loads up a lot quicker from a cold restart, is more responsive and also now allows me to save my password again in the web ui.

 

Leaving it here in case anyone else has this issue!

 

@binhex Should the stale sessions not be removed from the web.conf at some time?

Edited November 21, 20223 yr by thestraycat

Dear binhex 

 

I can not access the webUI but few day ago, it work normally. It can not access after I attached many torrent file. the screen file show nothing and I attached again and restart Delugevpn after that  I can not access the WebUi until now 

 

please kindly check a log file as I attached 

supervisord.log

I am back to having my webserver fail again. I can still get to the GUI, but it appears the internal access to what is going on keeps dying. My old tricks of just restarting the container aren't working, nor has clearing stale sessions from web.conf.

 

In checking the supervisor.log, I see this every time I lose access to the webserver:

2022-11-24 07:55:44,545 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

2022-11-24 07:55:44,548 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/twisted/internet/base.py", line 1318, in run
    self.mainLoop()
  File "/usr/lib/python3.10/site-packages/twisted/internet/base.py", line 1328, in mainLoop
    reactorBaseSelf.runUntilCurrent()
  File "/usr/lib/python3.10/site-packages/twisted/internet/base.py", line 994, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "/usr/lib/python3.10/site-packages/twisted/internet/task.py", line 251, in __call__
    d = maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 205, in maybeDeferred
    result = f(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/deluge/core/alertmanager.py", line 60, in update
    self.handle_alerts()
  File "/usr/lib/python3.10/site-packages/deluge/core/alertmanager.py", line 128, in handle_alerts
    **{
  File "/usr/lib/python3.10/site-packages/deluge/core/alertmanager.py", line 129, in <dictcomp>
    attr: getattr(alert, attr)
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcd in position 0: invalid continuation byte

 

The log shows the watchdog-script is still processing and it appears Deluge is still actively working, I just cannot access it.  What else can I check to find out what is killing the webserver?

33 minutes ago, MaxTrax said:

I am back to having my webserver fail again. I can still get to the GUI, but it appears the internal access to what is going on keeps dying. My old tricks of just restarting the container aren't working, nor has clearing stale sessions from web.conf.

 

In checking the supervisor.log, I see this every time I lose access to the webserver:

2022-11-24 07:55:44,545 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

2022-11-24 07:55:44,548 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/twisted/internet/base.py", line 1318, in run
    self.mainLoop()
  File "/usr/lib/python3.10/site-packages/twisted/internet/base.py", line 1328, in mainLoop
    reactorBaseSelf.runUntilCurrent()
  File "/usr/lib/python3.10/site-packages/twisted/internet/base.py", line 994, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "/usr/lib/python3.10/site-packages/twisted/internet/task.py", line 251, in __call__
    d = maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 205, in maybeDeferred
    result = f(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/deluge/core/alertmanager.py", line 60, in update
    self.handle_alerts()
  File "/usr/lib/python3.10/site-packages/deluge/core/alertmanager.py", line 128, in handle_alerts
    **{
  File "/usr/lib/python3.10/site-packages/deluge/core/alertmanager.py", line 129, in <dictcomp>
    attr: getattr(alert, attr)
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcd in position 0: invalid continuation byte

 

The log shows the watchdog-script is still processing and it appears Deluge is still actively working, I just cannot access it.  What else can I check to find out what is killing the webserver?

looks like a match:- https://dev.deluge-torrent.org/ticket/3427

 

sadly no resolution for it, so i dont know what to suggest other than try renaming your core.conf file and restart the container to regenerate it, maybe its a non utf-8 character in your config file.

 

@wipzcream looks like you have the exact same error.

I have a small problem with the binhex-delugevpn container. I followed this tutorial:

to "route" the binhex-prowlarr container traffic through the binhex-delugevpn container as this was suggested in some forums. But I'm not able to open the binhex-prowlarr webinterface anymore. even when I enter the ip and port manually.

when I use the console in the binhex-prowlarr container I can see that the vpn is working ( i tested that with command curl ifconfig.io) within the container. and it gives back the ip of the vpn just like when i use the command inside the binhex-deluge container.

I tried to start the containers in different orders since this was suggested by some user. 1st the deluge, then the prowlarr. but i also tried it the other way around. did not work either.

I suspect, that there might be a firewall inside the delugevpn that prevents me from connecting on port 9696.

But since I'm a linux novice I have no idea how to fix that.

Can anyone help me out ?

EDIT
 

sh-5.1# iptables --list
Chain INPUT (policy DROP)
target     prot opt source               destination         
ACCEPT     all  --  172.17.0.0/16        172.17.0.0/16       
ACCEPT     all  --  95.168.167.236       anywhere            
ACCEPT     all  --  95.168.167.236       anywhere            
ACCEPT     all  --  95.168.167.236       anywhere            
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8112
ACCEPT     udp  --  anywhere             anywhere             udp dpt:8112
ACCEPT     tcp  --  192.168.1.0/24       172.17.0.0/16        tcp dpt:58846
ACCEPT     tcp  --  192.168.1.0/24       172.17.0.0/16        tcp dpt:privoxy
ACCEPT     icmp --  anywhere             anywhere             icmp echo-reply
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            

Chain FORWARD (policy DROP)
target     prot opt source               destination         

Chain OUTPUT (policy DROP)
target     prot opt source               destination         
ACCEPT     all  --  172.17.0.0/16        172.17.0.0/16       
ACCEPT     all  --  anywhere             95.168.167.236      
ACCEPT     all  --  anywhere             95.168.167.236      
ACCEPT     all  --  anywhere             95.168.167.236      
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:8112
ACCEPT     udp  --  anywhere             anywhere             udp spt:8112
ACCEPT     tcp  --  172.17.0.0/16        192.168.1.0/24       tcp spt:58846
ACCEPT     tcp  --  172.17.0.0/16        192.168.1.0/24       tcp spt:privoxy
ACCEPT     icmp --  anywhere             anywhere             icmp echo-request
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
sh-5.1# iptables -A INPUT -

I think it does not work since I have the port 9696 nowhere in the IPTABLES of the delugevpn-container.

But I have no idea how to add the rule. Anyone got a clue ?

 

Edited November 27, 20223 yr by matuopm

Much like others on this thread recently, my Web UI isn't loading anymore, but upon checking my log file, I'm seeing that privoxy is connecting and so is my ovpn file from PIA. I'm sure I'm missing something here. The only difference is that I upgraded my mobo, which didn't impact anything in my other containers 

supervisord.log

Hi @binhex, thanks for all your amazing apps! I use quite a few!

 

I've been trying mostly successfully to setup a private tracker and have got stuck at the last bit, making delugevpn load the cookie script on tunnel up! The script works ok if I call it on cmd line, but if I add it to VPN_OPTIONS then the VPN fails to start, this is the suggested command: --script-security 2 --up /config/tun_up.sh

I'm guessing it's overriding your script? How do I achive this please?

Cheers,

Tim

But I'm not able to open the binhex-prowlarr webinterface anymore.

Q25 here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md


Sent from my iPhone using Tapatalk

Trying to install 2.1.1-1-01 on my Synology NAS DSM 7 running docker, and get "Kernel Too Old" when trying to run it.

Any fix for this, or what the latest version that works on DSM 7?  Last working version I tried was 2.0.4

 

Hi. Not sure if I am posting in the right spot but I've been having issues with binhex-delugevpn docker and slow download speeds ever since I transitioned to a new Ubiquiti router/network switch setup in my house. I thought I enabled all the required port forwarding rules but it just isn't performing. I tested downloading two identical torrents one on my laptop directly and one using delugevpn on my UNRAID (both connected to same VPN location server) and deluge had trouble connecting to the torrent even while my laptop using transmission downloaded at over 20MB/s within 30 seconds of starting torrent.  I used to get 40-50MB/s+ in download speeds and now I never get above a combined 4-5MB/s or it just won't connect period to those seeding (new releases with thousands of seeders in RARBG website search, not files with 1 or 2 seeders).

 

I'm not sure what gives but hoping others can help point me in right direction. I tried it-config plugin but upload speeds are way low.  I have a gigabit internet connection and laptop is on Wi-Fi while server is hardwired.  I don't know if this speedtest docker is testing my laptop I'm accessing it from or the actual server but posted a screenshot of that too. I read some posts about kinked cables reverting to 100mbs speeds but if that was the case shouldn't I not be able to register this internet speed in a test or play 4K Remux videos on direct play even locally in Plex?

 

Any ideas?

On 11/23/2022 at 8:34 AM, wipzcream said:

Dear binhex 

 

I can not access the webUI but few day ago, it work normally. It can not access after I attached many torrent file. the screen file show nothing and I attached again and restart Delugevpn after that  I can not access the WebUi until now 

 

please kindly check a log file as I attached 

supervisord.log 5.18 kB · 2 downloads

 

On 11/27/2022 at 8:08 PM, vvolfpack said:

Much like others on this thread recently, my Web UI isn't loading anymore, but upon checking my log file, I'm seeing that privoxy is connecting and so is my ovpn file from PIA. I'm sure I'm missing something here. The only difference is that I upgraded my mobo, which didn't impact anything in my other containers 

supervisord.log 9.89 MB · 6 downloads

 

hello,

 

-stop the docker

-open up terminal and run

/sbin/modprobe iptable_mangle

-start container

-wait a bit then access the webGUI.

Edited December 10, 20223 yr by Tolete

5 hours ago, Tolete said:

-stop the docker

-open up terminal and run

/sbin/modprobe iptable_mangle

-start container

-wait a bit then access the webGUI.

 

This worked - thank you!

17 hours ago, Tolete said:

 

 

hello,

 

-stop the docker

-open up terminal and run

/sbin/modprobe iptable_mangle

-start container

-wait a bit then access the webGUI.

Thank you for your advice I already reinstall it 

Sorry to bother, I tried searching through forums for both delugevpn and qbittorrenvpn.  Looks like some people have similar issues, but didn't find a solution.  For both delugevpn and qbittorrentvpn, I can spin up the containers with no problem.  I have my Webui pointed to port 7070, so I made sure to modify the docker compose to open 7070 and point webui to 7070, for both (deluge and qbt).  I've got wireguard set up, and it appears to connect fine.  I can ping the outside from within the container, so that's working.  

 

My issue is that I can't, for the life of me, get the Webui to connect, I keep getting a "took too long" timeout error.  Sonarr and Radarr both connect fine when testing port 7070.  I have qbt working through lscr.io/linuxserver/qbittorrent container, port 7070, no problem connecting to webui, but I'd prefer to use your built-in wireguard PIA connection.

 

I'm not terribly tech savvy, but I can follow instructions.  Any idea what's going on here?

Hey all.
I found about 15 threads on this topic but no solutions. I'm using all @binhex containers. Deluge, sonarr, radarr.
The issue is that when a torrent completed, deluge pauses it. radarr/sonarr both import the completed torrent. But they do not delete the torrent from cache, and they do not delete the torrent/extra crap that comes with the file from deluge.
I've confirmed that they can download the file.
I confirmed that deluge stops the torrent.
I've confirmed that sonarr/radarr both have the tickbox to remove the completed torrent.
I am not seeing any errors in any logs.

I have recently rebuilt the server. I've moved to a new server with more drives etc, and migrated my old everything, including restoring my dockers.
Prior to this, sonarr and radarr were deleting the files from cache upon ingestion, but they still weren't deleting the torrent and extra files.
Now I appear to have gone back a step and they're not even deleting the file on ingestion.
Please can I get some help with this, I must have read every thread on this topic and looked at every setting. (I've even tried the label addon in deluge and setting lables in the connection settings in radarr/sonarr. That didn't work, and caused errors on restart of deluge as deluge seems to disable the label addon on restart-neither here nor there really)

Spent days on this. Please someone help

Hi, hello! 

I just got Deluge-openvpn to run, and everything seems fine.  Just worrying about the ports. I've set a manual upload port to 58946 in deluge web gui.  Do I also need to portforward this in my router? Is there anything else I have to do? 

10 hours ago, Meatballs said:

Hi, hello! 

I just got Deluge-openvpn to run, and everything seems fine.  Just worrying about the ports. I've set a manual upload port to 58946 in deluge web gui.  Do I also need to portforward this in my router? Is there anything else I have to do? 

No, so depending on the VPN you're using (presumably pia) you need to go into your pia account and forward a port from there. They will give you a port to use, and you plug that port into deluge.
Then you can add this magnet link as a torrent to deluge:
magnet:?xt=urn:btih:4d60844af7e42602086266fcde02971a4fea29cf&dn=checkmyiptorrent%20Tracking%20Link&tr=http%3a%2f%2f143.110.208.40%2f
It'll create a torrent that in the status tab under tracker status, will give you an error with the IP of your VPN connection.
Then you can use something like:
https://portchecker.co/
To plug in the IP from the error, and the port from pia you've put into deluge to see if it's working.
You don't need to worry about your router, because the router isn't the end point of the connection, the exit server of the vpn connection is the end point that other torrent clients will see and try to connect to.

Though depending on how you have your vpn set up, the server you connect to *may*change, when you restart the docker/server or something else maybe. So just keep an eye on that and if it does change use the port checker again, but pia should be able to keep the port forwarded regardless of external IP, just keep an eye on it periodically.

Edited December 17, 20223 yr by 4554551n

My container connection recently stopped working.  No change in the VPN account, settings ,etc. (Mullvad).  I can open up the web console, I am able to add torrents, but the downloads are not starting.   I forced update, however, I haven't tried to rebuild the docker completely.  The logs are below:

 

2022-12-18 09:45:27,973 DEBG 'start-script' stdout output:
--------------------

2022-12-18 09:45:27,975 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-12-18 09:45:27,987 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-12-18 09:45:27,993 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-12-18 09:45:27,995 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-12-18 09:45:27,997 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.66.136.182/32 dev wg0

2022-12-18 09:45:28,003 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2022-12-18 09:45:28,006 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2022-12-18 09:45:28,016 DEBG 'start-script' stderr output:
could not detect a useable init system

2022-12-18 09:45:28,061 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2022-12-18 09:45:28,062 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2022-12-18 09:45:28,063 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2022-12-18 09:45:28,065 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2022-12-18 09:45:28,068 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2022-12-18 09:45:28,070 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2022-12-18 09:45:28,074 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2022-12-18 09:45:28,080 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

2022-12-18 09:45:29,086 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

2022-12-18 09:45:29,093 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

 

---

Update-

I completely reinstalled the docker into a new folder, new ports, etc.  However I am still getting the same errors in the logs.

Edited December 18, 20223 yr by dtctechs
Added troubleshooting step

edit: I'm dumb, nevermind

Edited December 23, 20223 yr by dswanlund

1 hour ago, dswanlund said:

My container also stopped working very recently. It just loops the above logs. Seems like something upstream might have broken? 

 

I tried the the binhex-qbittorrentvpn docker as well and am getting the errors as I posted previously.  I will sit tight until there's an update.