[Support] binhex - DelugeVPN


Recommended Posts

10 hours ago, Inch said:

Hi Binhex, 

First, thank you for all the effort you've put into this. I've setup the delugevpn docker container, I can even see it connecting to the vpn provider i use, when i login to console and run ifconfig.io etc. 

I'm having issues running Radar and Sonarr through it, it seems to just not be routing the ports properly (getting timeouts when i go to the <serverip>:port), and I've added them to input/output port fields. Is the issue I'm running into related to the above mention of a library fix being needed? 

Attached the log file with debug enabled. 

P.S. I've already ran: /sbin/modprobe iptable_mangle.

supervisord.log 16.1 kB · 2 downloads

see Q24 and follow that for a start:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment
3 hours ago, binhex said:

Thank you the only bit i was missing, was to remove the port on a container that I wanted to run through the VPN container. 
I've now got your Radarr container working without issue, for some reason and for the life in me i cannot get Sonarr running on port 8989 via the VPN container. Thanks in advance! 

 

___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2023-04-21 14:52:27.763745 [info] Host is running unRAID
2023-04-21 14:52:27.776590 [info] System information Linux d5fb88195af9 6.1.23-Unraid #1 SMP PREEMPT_DYNAMIC Fri Apr  7 11:30:48 PDT 2023 x86_64 GNU/Linux
2023-04-21 14:52:27.791207 [info] OS_ARCH defined as 'x86-64'
2023-04-21 14:52:27.805291 [info] PUID defined as '99'
2023-04-21 14:52:27.821230 [info] PGID defined as '100'
2023-04-21 14:52:27.855866 [info] UMASK defined as '000'
2023-04-21 14:52:27.869802 [info] Permissions already set for '/config'
2023-04-21 14:52:27.884844 [info] Deleting files in /tmp (non recursive)...
2023-04-21 14:52:27.900617 [info] Starting Supervisor...
2023-04-21 14:52:27,994 INFO Included extra file "/etc/supervisor/conf.d/sonarr.conf" during parsing
2023-04-21 14:52:27,994 INFO Set uid to user 0 succeeded
2023-04-21 14:52:27,995 INFO supervisord started with pid 7
2023-04-21 14:52:28,997 INFO spawned: 'sonarr' with pid 58
2023-04-21 14:52:28,997 INFO reaped unknown pid 8 (exit status 0)
2023-04-21 14:52:29,239 DEBG 'sonarr' stdout output:
[Info] Bootstrap: Starting Sonarr - /usr/lib/sonarr/bin/Sonarr.exe - Version 3.0.10.1567 

2023-04-21 14:52:29,385 DEBG 'sonarr' stdout output:
[Info] AppFolderInfo: Data directory is being overridden to [/config] 

2023-04-21 14:52:29,432 DEBG 'sonarr' stdout output:
[Info] Router: Application mode: Interactive 

2023-04-21 14:52:29,512 DEBG 'sonarr' stdout output:
[Info] MigrationLogger: *** Checking database for required migrations data source=/config/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 

2023-04-21 14:52:29,591 DEBG 'sonarr' stdout output:
[Info] MigrationLogger: *** Checking database for required migrations data source=/config/logs.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 

2023-04-21 14:52:29,683 DEBG 'sonarr' stdout output:
[Info] OwinHostController: Listening on the following URLs: 

2023-04-21 14:52:29,684 DEBG 'sonarr' stdout output:
[Info] OwinHostController:   http://*:8989/ 

2023-04-21 14:52:29,876 DEBG 'sonarr' stdout output:
[Info] SonarrBootstrapper: Starting Web Server 

2023-04-21 14:52:30,876 INFO success: sonarr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

Edited by Inch
Link to comment

Hi everyone! This might be a little off topic, I'm sorry if that's not ok. Is anyone familiar with the scripts that make the reannouncement of a torrent when there's an error for unregistered torrent when getting torrents from IRC channels? There's a few versions of them around, but I can't seem to getting any to work properly.

Herer's one of the scripts I've tried unsuccessfully:
 

#!/bin/bash

torrentid=$1
torrentname=$2
torrentpath=$3

output="/config/deluge-reannounce.log"
ip=127.0.0.1
port=58846 # deluge daemon port

x=1
while [ $x -le 100 ]
do
    sleep 7
    echo "$(date '+%Y.%m.%d-%T') - Running $x times - TorrentID: $torrentid" >> "$output"
    line=$(/usr/bin/deluge-console "connect $ip:$port; info" "$1" | grep "Tracker status")
    echo "$(date '+%Y.%m.%d-%T') - $line" >> "$output"
    case "$line" in
        *Unregistered*|*unregistered*|*Sent*|*End*of*file*|*Bad*Gateway*|*Error*)
        /usr/bin/deluge-console "connect $ip:$port; pause '$torrentid'"
        sleep 5
        /usr/bin/deluge-console "connect $ip:$port; resume '$torrentid'"
        ;;
    *)
    echo "$(date '+%Y.%m.%d-%T') - Working after $x tries: $torrentname $torrentpath $torrentid" >> "$output"
    exit 1;;
esac
x=$(( x+1 ))
done


I add the script via the execute plugin on deluge, and set it to run when a torrent is added. The script seems to run, but the problem is new torrents added from IRC channel get the status "error: unregistered torrent", but when I check the script log file it says "working after 1 tries...".

I'm running this container on docker on an Asustor NAS. I'm not on unraid. Any help would be appreciated. Thank you.

Link to comment

I just tried to switch from rtorrent-vpn to deluge-vpn and am trying to use wireguard as I did with rtorrent-vpn. 
But I can't get it to work correctly, I can add a torrent and in the beginning it starts to download at around 30MiB/s (I am have a 1000/1000MB/s connection). But after a few seconds it goes down to a few KiB/s for a couple of minutes then again up to around 30MiB/s for a few seconds.
So I can only download at a decent speed at a few seconds at a time. 
I did not have this problem with rtorrent, what can cause this problem ?
I am using Wireguard and in rtorrent I had to add the opened wireguard port to the settingsfile in rtorrent under "listening ports"

Where is the correct place to add this port in deluge ?

 

image.png.0b33cb4d3ba399ea33e382ffc9b8588d.png

Link to comment

Hi guys,

Since the last update i cant change the DNS Server of the VPN-Network. It always falls back to the default DNS-Sever mentioned in the Documentation (DNS-Watch Range). In the Past it was sufficient to delete the Nameserver Entry in the Edit Option of the Docker. I Also tired to Edit the wg0.conf but DNS Severs entered or not entered there are also ignored. In the end i want to use the dns sever provided by the vpn-host. Can anyone help me out?

Link to comment

Hi All,

Ran into an interesting but frustrating problem. 

 

After setting up thin client and connect it to DeludgeVPN, the webui (from unraid or via localhost:8112) is no long working as in, I can still login with the password, but it's just blank, no torrents, no setting were saved, nothing. HOWEVER, on the thin client's side (on a win11 pc) everything is there and I can see all my torrents are there and seeding/downloading just fine.

 

Normally this won't be an issue, but all my *arr dockers seems to be broken with no download client error because from localhost:8112 is all blank.

 

Has anyone ran into this issue? any tips on how to fix it?

 

Thanks! 

Link to comment
  • 2 weeks later...
1 minute ago, Gex2501 said:

I'm not using labels...just want to try a nicer UI. Is there something special about the binhex-delugevpn that doesn't work with Flood? Do I need some special config?

No, nothing special. I've just tried it for a few min tho. It was as I said useless to me as it doesn't support labels. 

Link to comment

I've noticed for the past few weeks that whenever my docker containers are stopped by Appdata Backup/Restore for backup, when they come back up, no torrents old or new work.  On the binhex-delugevpn console, I can ping out, but no torrenting works unless I restart the container again.  Has anyone experienced this?

Link to comment

Hi guys. I'm trying to set this up and I'm really running into problems. 

 

I've managed to get deluge setup and it will run but I am having difficulty accessing the webui. When I open the webui sometimes I get an error saying I can't reach the ip address. Sometimes I can access the deluge webui.

 

Once I manage to get into the deluge webui the connection manager dialog pops up and the connect button doesn't respond when I click it. At the bottom left of the screen it says "not connected". If I stop and restart the docker container sometimes I can get the deluge webui to "connect". I managed to load a ubuntu torrent to test things and then it started downloading. After a few minutes the connection manager dialog popped up and is again unresponsive. 

 

 

Link to comment

Hi there - apologies if this has been resolved previously.

I'm trying to use wireguard rather than openvpn as I've moved from TalkTalk (getting c.18MB/s download on a 150Mb connection) to Virgin Media , where I seem to be limited to c.1.2MB/s on a 500Mb connection. I read that it might be Virgin not liking openvpn - hence me trying to use wireguard.

I've installed the container using the following:

 

docker run -d \
    --privileged=true \
    -p 8112:8112 \
    -p 8118:8118 \
    -p 58846:58846 \
    -p 58946:58946 \
    --name=arch-delugevpnwg \
    -v /share/CACHEDEV1_DATA/Data/Multimedia/:/data \
    -v /share/CACHEDEV1_DATA/Data/Deluge_Config/:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_USER= \
    -e VPN_PASS= \
    -e VPN_PROV=custom \
    -e VPN_CLIENT=wireguard \
    -e STRICT_PORT_FORWARD=yes \
    -e ENABLE_PRIVOXY=no \
    -e LAN_NETWORK=192.168.1.0/24 \
    -e NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1 \
    -e DELUGE_DAEMON_LOG_LEVEL=info \
    -e DELUGE_WEB_LOG_LEVEL=info \
    -e DELUGE_ENABLE_WEBUI_PASSWORD=no \
    -e VPN_INPUT_PORTS=1234 \
    -e VPN_OUTPUT_PORTS=5678 \
    -e DEBUG=false \
    -e UMASK=000 \
    -e PUID=0 \
    -e PGID=0 \
binhex/arch-delugevpn

 

It's stopping at "[warn] WireGuard interface failed to come 'up', exit code is '1'"

 

I've attached the wireguard config file as well as the supervisord.log.

 

Any ideas please?

 

PS If there are any other ideas why the Virgin dl rate is so bad I'd love to hear.  I've not changed anything in the deluge preferences so pretty sure that isn't the issue (and I followed the guidance on limiting the ul speeds etc..).

supervisord.log wg0.conf

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.