[Support] binhex - DelugeVPN


Recommended Posts

7 minutes ago, RaidBoi1904 said:

Same slow speeds :(

Weird.. You can maybe try the itconfig plugin. I've seen others had success with it when everything else has failed. I've never used it as I always get max speed. But search for itconfig in this thread and you should be able to find the correct settings for it. Use google's "site" option, it's much better then the forum search. I don't know if the plugin is updated to work with version 2 tho..

Link to comment
1 minute ago, strike said:

Weird.. You can maybe try the itconfig plugin. I've seen others had success with it when everything else has failed. I've never used it as I always get max speed. But search for itconfig in this thread and you should be able to find the correct settings for it. Use google's "site" option, it's much better then the forum search. I don't know if the plugin is updated to work with version 2 tho..

Just for fun I tried that file that you asked me to make in QBtorrent and I got the same slow speeds 😮
image.thumb.png.95d27fdc9cf83807d9599312276c9a7f.png

 

I will go look for itconfig like you said thanks. Also any chance you could share your delugeVPN container settings (blurring out sensible stuff) I want to compare a working one with mine, maybe I screwed something up at that level? at any rate thank you for your help and time!

Link to comment

I'm fairly certain it has nothing to do with your container settings but here is my docker run command, you can see my settings from that: 

 

Quote

docker run -d --name='binhex-delugevpn' --net='br0' --ip='192.168.2.218' --cpuset-cpus='0,8' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_8112'='8112' -e 'TCP_PORT_58846'='58846' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='user' -e 'VPN_PASS'='password' -e 'VPN_REMOTE'='' -e 'VPN_PORT'='443' -e 'VPN_PROTOCOL'='udp' -e 'VPN_PROV'='airvpn' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.2.0/24' -e 'DEBUG'='true' -e 'PUID'='1000' -e 'PGID'='100' -v '/mnt/cache/Docker/DelugeVPN/':'/config':'rw' -v '/mnt/user/Downloads/':'/data':'rw' 'binhex/arch-delugevpn'

My template is old tho, so it may differ from yours.

 

The important settings in deluge related to speed are these: Just the incoming port. And peer exchange,dht and lsd should be enabled. Then cap the upoad speed under bandwith.

 

image.thumb.png.0664c1aaef050a61b38757996853987b.png

image.thumb.png.6c3e4004e972c0ca34e30671efe30ef4.png

 

And the test active port in the network settings gives you a check mark I assume? It should when the airvpn port check says it works

Link to comment

Then I'm out of ideas. Check the itconfig plugin as mentioned, might help.

 

31 minutes ago, RaidBoi1904 said:

your ui looks different than mine

 

31 minutes ago, RaidBoi1904 said:

I have no way to test the port inside of delugeVPN

That's because I'm using the thin client on windows not the webui

Link to comment
18 hours ago, orlando500 said:

did you submit a support ticket to pia regarding the sweden node? if not please do.. lets get that node working again

Indeed I did . . Fingers crossed, cause this is a pain. . .

 

EDIT:

Got this back from PIA ->

Please note that our DevOps are currently investigating possible issues related with the IPs for our Sweden server. For the mean time, if you still need to connect to the same server, kindly do through the IP instead of the server host. You can replace sweden.privateinternetaccess.com with 46.246.3.254 within the config file. Kindly check the article below on how to connect to a same IP:
https://www.privateinternetaccess.com/helpdesk/kb/articles/can-i-configure-the-vpn-connection-to-always-use-the-same-ip-address

Edited by elcapitano
Link to comment
2 minutes ago, strike said:

Then I'm out of ideas. Check the itconfig plugin as mentioned, might help.

 

 

That's because I'm using the thin client on windows not the webui

 So I tried to setup my windows thin client but I couldn't get it to work with both of the IPs shown by unraid in the docker list window. I really wanted to click that check button. Any way, I figured out that I could access the terminal for a container and I looked up how to list all the udp ports that were listening and it does show 60694.

image.png.3a5e3510aa8b91ac445bcd4186898a1c.png

 

Edited by RaidBoi1904
Link to comment

I restarted my Deluge container because downloads were not starting and now I can't get the container to load properly anymore. 

 

Log:

 

https://hub.docker.com/u/binhex/

2020-08-08 12:46:58.553742 [info] System information Linux c53cc9e8b761 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-08-08 12:46:58.569905 [info] OS_ARCH defined as 'x86-64'
2020-08-08 12:46:58.585879 [info] PUID defined as '99'
2020-08-08 12:46:58.603101 [info] PGID defined as '100'
2020-08-08 12:46:58.646751 [info] UMASK defined as '000'
2020-08-08 12:46:58.662197 [info] Permissions already set for volume mappings
2020-08-08 12:46:58.679628 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-08-08 12:46:58.695453 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-08-08 12:46:58.711065 [info] VPN_ENABLED defined as 'yes'
2020-08-08 12:46:58.731069 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/czech-aes-128-cbc-udp-ip.ovpn
2020-08-08 12:46:58.762317 [info] VPN remote line defined as 'remote 89.238.186.228 1198'
2020-08-08 12:46:58.778139 [info] VPN_REMOTE defined as '89.238.186.228'
2020-08-08 12:46:58.794037 [info] VPN_PORT defined as '1198'
2020-08-08 12:46:58.812479 [info] VPN_PROTOCOL defined as 'udp'
2020-08-08 12:46:58.828159 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-08-08 12:46:58.843762 [info] VPN_PROV defined as 'pia'
2020-08-08 12:46:58.859426 [info] LAN_NETWORK defined as '192.168.9.0/24'
2020-08-08 12:46:58.874915 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-08-08 12:46:58.890534 [info] VPN_USER defined as 'xxxx'
2020-08-08 12:46:58.906082 [info] VPN_PASS defined as 'xxxx'
2020-08-08 12:46:58.921777 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-08-08 12:46:58.937355 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-08-08 12:46:58.953109 [info] ENABLE_PRIVOXY defined as 'yes'
2020-08-08 12:46:58.968824 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-08-08 12:46:58.986448 [info] Deleting files in /tmp (non recursive)...
2020-08-08 12:46:59.001367 [info] Starting Supervisor...
2020-08-08 12:46:59,097 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-08-08 12:46:59,097 INFO Set uid to user 0 succeeded
2020-08-08 12:46:59,099 INFO supervisord started with pid 6
2020-08-08 12:47:00,101 INFO spawned: 'start-script' with pid 172
2020-08-08 12:47:00,101 INFO spawned: 'watchdog-script' with pid 173
2020-08-08 12:47:00,102 INFO reaped unknown pid 7 (exit status 0)
2020-08-08 12:47:00,105 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-08-08 12:47:00,105 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-08-08 12:47:00,105 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-08-08 12:47:00,146 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-08-08 12:47:00,148 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-08-08 12:47:00,150 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-08-08 12:47:00,152 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-08-08 12:47:00,153 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-08-08 12:47:00,155 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-08-08 12:47:00,157 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-08-08 12:47:00,159 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-08-08 12:47:00,161 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-08-08 12:47:00,162 DEBG 'start-script' stdout output:
89.238.186.228

2020-08-08 12:47:00,176 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-08-08 12:47:00,178 DEBG 'start-script' stdout output:
[info] Adding 192.168.9.0/24 as route via docker eth0

2020-08-08 12:47:00,178 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-08-08 12:47:00,179 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4
192.168.9.0/24 via 172.17.0.1 dev eth0

2020-08-08 12:47:00,179 DEBG 'start-script' stdout output:
--------------------

2020-08-08 12:47:00,180 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 4 iptable_filter,iptable_nat,iptable_mangle

2020-08-08 12:47:00,180 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-08-08 12:47:00,200 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-08-08 12:47:00,201 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.9.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.9.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.9.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.9.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

 

Config:

 

Host Port 1: 8112

Host Port 2: 58846

Host Port 3: 58946

Host Port 4: 58946

Host Port 5: 8118

Host Path 2: /mnt/user/data/plunder/

Key 1: yes

Key 2: piausername

Key 3: piapass

Key 4: pia

Key 5: null

Key 6: yes

Key 7: yes

Key 8: 192.168.9.0/24

Key 9: 209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

Key 10: info

Key 11: info

Key 12: null

Key 13: false

Key 14: 000

Key 15: 99

Key 16: 100

 

Edited by xagrr
Link to comment
1 hour ago, xagrr said:

I restarted my Deluge container because downloads were not starting and now I can't get the container to load properly anymore. 

What vpn provider are you using? Many of the PIA port forwarding servers are no longer working and this has resulted in similar problems for people trying to use them.

Link to comment
1 hour ago, wgstarks said:

What vpn provider are you using? Many of the PIA port forwarding servers are no longer working and this has resulted in similar problems for people trying to use them.

that's what I was using. What's a good one these days?

Link to comment
Just now, xagrr said:

Thanks for pointing that out. How do I use that particular server? Is it in the container config or the vpn settings somewhere?

Watch this video: 

 

He uses PIA so its a step by step setup for your needs. As the past messages said there a few servers showing issues with port forwarding. So use the servers they are recommending. 

Link to comment
5 hours ago, RaidBoi1904 said:

Watch this video: 

 

He uses PIA so its a step by step setup for your needs. As the past messages said there a few servers showing issues with port forwarding. So use the servers they are recommending. 

Thanks back in business but very slow speeds > 30-80kib/s range. Hm

Link to comment

So Not sure how to tell what Incoming port I should select within the Deluge settings, to try and improve speed.  Followed Space Invaders video. Have PIA with port forwarding working through Vancouver currently.  Get the following in the log file  below..  Should I have the incoming port set to  "6890,"  "22509" or "58846"  

 

2020-08-09 12:07:03,955 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 22509 different, marking for reconfigure

2020-08-09 12:07:03,956 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-08-09 12:07:04,314 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.23.11.10'
[info] Deluge key 'listen_interface' will have a new value '10.20.10.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-08-09 12:07:04,479 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-08-09 12:07:04,917 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-08-09 12:07:05,130 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-08-09 12:07:07,153 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-08-09 12:07:09,254 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (22509, 22509)
Configuration value successfully updated.

Link to comment
23 minutes ago, Aceriz said:

So Not sure how to tell what Incoming port I should select within the Deluge settings, to try and improve speed.  Followed Space Invaders video. Have PIA with port forwarding working through Vancouver currently.  Get the following in the log file  below..  Should I have the incoming port set to  "6890,"  "22509" or "58846"  

Don't worry about the port forwarding if you're using PIA, all you need to do is use one of the endpoints that support it. But as PIA is doing network changes I understand that some endpoints don't work right now, which possibly results in heavy load on the few that works.

Link to comment

Hey, i have an issue where whenever i restart my container i have a lot of torrents that have been paused, and i have to manually restart them, this has several issues where sometimes i will get an HnR warning and sometimes a torrent will just stop downloading completely.

 

I recently reached 6000 torrents in my client so i was wondering if there way maybe a cap there or something?

 

any help pointing me in the right direction would be nice, thanks.

 

Here are my settings
1qqdEbO.png

 

Edited by MammothJerk
Link to comment
2 hours ago, MammothJerk said:

I recently reached 6000 torrents in my client so i was wondering if there way maybe a cap there or something?

wow really!? 6000 torrents running deluge, i thought that was pretty much impossible!, there is no hard cap that im aware of but you will run into stability issues with that many torrents when running deluge.

Link to comment
14 hours ago, MammothJerk said:

Hey, i have an issue where whenever i restart my container i have a lot of torrents that have been paused, and i have to manually restart them, this has several issues where sometimes i will get an HnR warning and sometimes a torrent will just stop downloading completely.

 

I recently reached 6000 torrents in my client so i was wondering if there way maybe a cap there or something?

 

any help pointing me in the right direction would be nice, thanks.

 

Here are my settings
 

 

Did you have setup "Maximum Upload Slots" to -1 or 6000? You can find it under Bandwidth.  
If you use "AutoAdd" so control the settings there too. 

Edited by Wetterchen
Link to comment
14 hours ago, binhex said:

wow really!? 6000 torrents running deluge, i thought that was pretty much impossible!, there is no hard cap that im aware of but you will run into stability issues with that many torrents when running deluge.

This is the only real issue i've had so far. as long as i dont access any label that has 1000+ torrents in it it works as smooth as can be.

Is there another client i should be using if i have this many torrents?

 

2 hours ago, Wetterchen said:

Did you have setup "Maximum Upload Slots" to -1 or 6000? You can find it under Bandwidth.  
If you use "AutoAdd" so control the settings there too. 

i haven't changed these settings for a long time so i wouldnt think they are the cause..

PjxvlDM.png

Link to comment
4 hours ago, MammothJerk said:

Is there another client i should be using if i have this many torrents?

rtorrent is well regarded as being able to support thousands of torrents, but even this does struggle when you get above 2000 torrents, so tbh you are probably best sticking with deluge if you are able to keep 6000 torrents active.

 

so one solution is to have two deluge instances and then split the load between the two, its not ideal i know as it means managing two deluge instances but it would work.

Link to comment
On 8/8/2020 at 8:39 AM, elcapitano said:

Indeed I did . . Fingers crossed, cause this is a pain. . .

 

EDIT:

Got this back from PIA ->

Please note that our DevOps are currently investigating possible issues related with the IPs for our Sweden server. For the mean time, if you still need to connect to the same server, kindly do through the IP instead of the server host. You can replace sweden.privateinternetaccess.com with 46.246.3.254 within the config file. Kindly check the article below on how to connect to a same IP:
https://www.privateinternetaccess.com/helpdesk/kb/articles/can-i-configure-the-vpn-connection-to-always-use-the-same-ip-address

yeah after they upgraded i seem to have some issues connection tru that node. When got home.. the deluge seems unresponsive and have not started downloads in que. Got a lot of this when restarting docker:

2020-08-13 16:17:43,212 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 11 retries left
[info] Retrying in 10 secs...

2020-08-13 16:17:53,289 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 10 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:03,548 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 9 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:13,630 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 8 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:13,630 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 8 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:23,723 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 7 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:33,810 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 6 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:43,955 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 5 retries left
[info] Retrying in 10 secs...

2020-08-13 16:18:54,043 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 4 retries left
[info] Retrying in 10 secs...

 

 

Link to comment

Not directly related to DelugeVPN, but I've been experimenting with with IPTV streaming, via PIA VPN, and find that I experience a lot of rebuffering on the stream.  The rebuffering occurs whether I use PriVoxy from DelugeVPN, or I set up a dedicated VPN connection on my router, solely for use by Kodi.  If I stream direct, not via VPN, rebuffering very seldom occurs, so I presume that the problem is due either to PIA, or general VPN overheads.  The rebuffering seems to be most prevalent from about 1400 UTC (10pm here in Philippines).

 

I'm thinking of changing VPN provider - Ivacy and Mullvad both claim to have fast connections and support port forwarding.  Does anyone have relevant experience of these providers, either in terms of configuration/use with DelugeVPN, or streaming performance?

 

Mullvad have the disadvantage that they don't support PPTP/L2TP connections, so wouldn't allow a connection direct from my router.

 

Does anyone have suggestions for other VPN providers to be considered?

 

I have a 100Mbps fibre connection.

Link to comment

I recently ran into an issue where privoxy is functioning as it normally does. There hasn't been any changes to my setup, but I do auto-update the DelugeVPN container. The port is configured to 8118, but none of my containers nor my browser can access it via the host/bridge IP address. I am able to access the DelugeVPN web gui, so I know that the VPN is working. I'm wondering if it has anything to do with the listening address. When I open up a console for the container, I ran netstat and here are the results:

tcp        0      0 127.0.0.1:8118          0.0.0.0:*               LISTEN      -

tcp        0      0 0.0.0.0:8112            0.0.0.0:*               LISTEN      - 

The web admin is configured on 0.0.0.0 for port 8112, while privoxy is configured on 127.0.0.1. Could this be the issue?

Edited by lytener
Updated information
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.