Jump to content

[Support] binhex - DelugeVPN


Recommended Posts

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
22 minutes ago, mike_walker said:

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..).

The number one reason for low speed is not having an open incoming port. Have you set that up with your vpn provider and put that port in the deluge settings?

Link to comment

Started to get these messages in the container log.

The lines bellow keep repeating in the log and there is no access to the WebUI of the container

I think the cypher was there before when it used to work OK.


 

2023-05-31 21:14:10,641 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-05-31 21:14:10,645 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 TCP/UDP: Preserving recently used remote address: [AF_INET]185.2.30.216:80
2023-05-31 21:14:10 Attempting to establish TCP connection with [AF_INET]185.2.30.216:80

2023-05-31 21:14:10,748 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 TCP connection established with [AF_INET]185.2.30.216:80
2023-05-31 21:14:10 TCPv4_CLIENT link local: (not bound)
2023-05-31 21:14:10 TCPv4_CLIENT link remote: [AF_INET]185.2.30.216:80

2023-05-31 21:14:10,851 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 Connection reset, restarting [0]

2023-05-31 21:14:10,852 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 SIGHUP[soft,connection-reset] received, process restarting

2023-05-31 21:14:10,853 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

2023-05-31 21:14:10,856 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 WARNING: file 'credentials.conf' is group or others accessible
2023-05-31 21:14:10 OpenVPN 2.6.3 [git:makepkg/94aad8c51043a805+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Apr 13 2023

2023-05-31 21:14:10,856 DEBG 'start-script' stdout output:
2023-05-31 21:14:10 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10
2023-05-31 21:14:10 DCO version: N/A

 

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.

×
×
  • Create New...