[Support] binhex - DelugeVPN


Recommended Posts

I'm having a heck of a time switching from windows to unraid for my new nas.. :)

 

I'm having an issue with the webui being reset anytime I attempt to hit it. (getting connection reset by peer)

In the console I can verify the vpn is running and I do get an external ip that is not my own.

webui works when not connected to vpn.

new opvn files tossed in /config/openvpn - connecting to PIA Montreal which does have port forwarding.

LAN_Network IS correct. (192.168.128.0/24 is my network)

adblock killed. (dunno why I was thinking that)

 

Thoughts?

The only thing I noticed in the log was that the docker interface is defined as eth0 - and I have br0 configured in setting. not sure if that is transparent to the image and its just using eth0 as the generic 1st nic?

 

Appreciate the help, this community has been great!

 

supervisord.log

 

Link to comment
39 minutes ago, Geekd4d said:

and I have br0 configured in setting

This container does not support br0 at this time. Switch to bridge. Or use the deluge desktop/thin client to get access over br0, that might work. See the faq for how to connect with the deamon.

  • Like 1
Link to comment
1 hour ago, strike said:

This container does not support br0 at this time. Switch to bridge. Or use the deluge desktop/thin client to get access over br0, that might work. See the faq for how to connect with the deamon.

Thank you! Had a feeling it was something network related. I'll poke it later on today and report back. (upgrading my parity drives with faster ones)

 

thanks again!

 

Link to comment
10 hours ago, strike said:

This container does not support br0 at this time. Switch to bridge. Or use the deluge desktop/thin client to get access over br0, that might work. See the faq for how to connect with the deamon.

That's exactly what it was!

popped it on bridge. vpn confirmed and webui works!

Thank you so much!

Link to comment

I can't access deluge daemon from a thin client outside LAN. It works fine on LAN but outside of it I can't access using my external IP address. Any thoughts? I tried loading iptable_mangle module on docker host, made sure the thin client version is compatible (same version on both systems on and off LAN), but I can still only access on LAN. I have VPN enabled as well.

Edited by brikn
Link to comment
On 6/9/2020 at 11:00 PM, strike said:

I see you have PIA as your provider. The port forwarding is done automatically for PIA in this container and the log shows that you have got an incoming port so you should be able to upload. Unless you changed the port in deluge yourself, which you shouldn't be doing for PIA.

I haven't made any changes other than the suggestions in spaceinvaderone youtube on how to set it up.  I am also running in through letsencrypt for accessing the UI but I don't think that should matter at all in this instance.  I do not see any issues in the logs and everything appears correctly configured.  I was hoping someone in here has run into this because there isn't anything obviously wrong with my setup.

Link to comment

Anyone having issues adding torrents, with delugesiphon or otherwise? I primarily use two private trackers and one hasn't worked with Deluge for over a year and now the second tracker has stopped working.... I have to manually add the torrent files into an Unraid folder and use the AutoAdd plugin to load them into Deluge - no other method works for me to add torrents to Deluge (i.e. the manual adding of the link url does not work).

Edited by BBLV
Link to comment

Hi,

 

My Docker has been working great for over a year but the last month or so I seem to lose connection to the webgui?  the docker appears to be "running" as I can acess the console but the messages in the log file are hours old so it seems to have stopped?  I can restart the docker and all is well again for a few days, I am not sure the best way to diagnose this?

 

Thank you

Link to comment

My CPU is hitting 100% after upgrading internet speeds.

 

I went from 100/100 to 1000/1000 the other week and now my unraid server is freezing up constantly with the CPU maxed out at 100%. I narrowed it down to delugeVPN writing to the cache taking up all the CPU resources, even pinning deluge to 4 specific cores doesnt help as it still uses all cores at 100%

 

My cache is a cache pool of 2 devices, one 960gb and one 250gb for a total of 1.2TB~

 

Heres disk/cpu activity with 0 torrents downloading to array/cache and around 20~ torrents uploading from array

iCgkPHt.pngptHnkAF.png

Heres disk/cpu activity with 2 torrents downloading to cache capped at 30MB/s and around 20~ torrents uploading from array at around 9MB/s

05gUbYa.png2AYOKCx.png

Heres disk/cpu activity with 2 torrents downloading to cache capped at 10MB/s and around 20~ torrents uploading from array at around 9MB/s

M3K3Y2e.pngB6HSLSh.png

 

is this expected behavior? like is my CPU too shit for my download speed? Why would writes to cache impact my CPU to this extent?

Edited by MammothJerk
Link to comment

Hi, running latest UnRaid and Deluge VPN docker with PIA.

It's been running well and I've had the occasional torret stuck at 100%, a quick force-recheck sorts it out - until today.

Every single torrent is stuck at 100% now and the force-recheck takes much longer - in the region of 30mins a 1% progress.

Driving me crazy, what have I missed? Is there an easy solution? Issues with permissions?? - I haven't changed anything since install.

Link to comment
On 6/15/2020 at 11:02 PM, mbc0 said:

Hi,

 

My Docker has been working great for over a year but the last month or so I seem to lose connection to the webgui?  the docker appears to be "running" as I can acess the console but the messages in the log file are hours old so it seems to have stopped?  I can restart the docker and all is well again for a few days, I am not sure the best way to diagnose this?

 

Thank you

Hi, 

 

This is a regular occurance, and it seems to be every 4-5 days, again today I see the notifications in sonarr/radarr telling me there is no connection? 

Link to comment

Hi there.

 

Im getting error message when starting the container. I haven't done any changed to the docker or to my firewall (pfSense). I see the following errors on the logs

 

2020-06-21 13:20:28,352 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-06-21 13:20:28,354 DEBG 'start-script' stdout output:
[crit] us-nyc-011.mullvad.net cannot be resolved, possible DNS issue

What i have tried to get it to work.

 

- Rebooted container

- Rebooted Unraid/pfSense

- Downloaded new config from VPN provided

- Can ping / traceroute/ dnslook from pfSense to VPN server

 

Attached is the supervisor log

 

Appreciate your help.

 

Thank you.

binhex-delugevpn.6.21.2020

Link to comment
On 6/16/2020 at 4:17 PM, MammothJerk said:

My CPU is hitting 100% after upgrading internet speeds.

 

I went from 100/100 to 1000/1000 the other week and now my unraid server is freezing up constantly with the CPU maxed out at 100%. I narrowed it down to delugeVPN writing to the cache taking up all the CPU resources, even pinning deluge to 4 specific cores doesnt help as it still uses all cores at 100%

 

My cache is a cache pool of 2 devices, one 960gb and one 250gb for a total of 1.2TB~

 

Heres disk/cpu activity with 0 torrents downloading to array/cache and around 20~ torrents uploading from array

iCgkPHt.pngptHnkAF.png

Heres disk/cpu activity with 2 torrents downloading to cache capped at 30MB/s and around 20~ torrents uploading from array at around 9MB/s

05gUbYa.png2AYOKCx.png

Heres disk/cpu activity with 2 torrents downloading to cache capped at 10MB/s and around 20~ torrents uploading from array at around 9MB/s

M3K3Y2e.pngB6HSLSh.png

 

is this expected behavior? like is my CPU too shit for my download speed? Why would writes to cache impact my CPU to this extent?

Can you post the container configuration to see?

Link to comment
9 hours ago, bugster said:

Looks fine.

 

I'm guessing the host path you have is to a download folder under /mnt/user? Within Deluge > Preferences > Downloads. What paths are you using?

My downloads within deluge is set to "/mnt/user/Torrents" which would go through "Host Path 1" to "/mnt/user/Torrents" which in turn would actually be written to "/mnt/cache/Torrents" since the share "Torrents" is a cache-yes share.

CksR1kg.png

Link to comment

Hi, I seem to have having the same issue a number of others have had in the past. I've followed all the suggestions and still my deluge downloads are DOG SLOW... i mean 5 KiB/s SLOW.... Same endpoint, via desktop app... ill max out my connection no problem.

 

Im running the latest delugeVPN container, with PIA, via a port forward enabled endpoint.

 

core.conf file attached, any and all help would be appreciated.

core.conf

Edited by DAVIDP
Link to comment

Deluge 2.0.4dev23: "no route to host"

 

This has happened before, and it went away. I'd rather figure out what's going on and fix it instead of just waiting around. 

 

From my desktop:

 

Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\jeff.lebowski>tracert hdbits.org

Tracing route to hdbits.org [179.43.184.130]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.3.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms    15 ms  096-034-106-128.biz.spectrum.com [96.34.106.128]
  4    14 ms    12 ms     9 ms  096-034-109-208.biz.spectrum.com [96.34.109.208]
  5    10 ms     9 ms    18 ms  096-034-109-139.biz.spectrum.com [96.34.109.139]
  6    13 ms    14 ms    14 ms  096-034-108-178.biz.spectrum.com [96.34.108.178]
  7    24 ms    14 ms    24 ms  bbr01sttlwa-tge-0-1-0-4.sttl.wa.charter.com [96.34.0.92]
  8    19 ms    16 ms    19 ms  prr01sttlwa-bue-1.sttl.wa.charter.com [96.34.3.29]
  9    17 ms    22 ms    14 ms  10ge2-1.core1.sea1.he.net [66.160.133.117]
 10    62 ms    65 ms    73 ms  100ge1-2.core1.msp1.he.net [184.104.194.22]
 11    72 ms    76 ms    72 ms  100ge13-1.core2.chi1.he.net [184.105.223.177]
 12    86 ms    88 ms    88 ms  100ge1-2.core1.nyc4.he.net [184.104.193.174]
 13   161 ms   157 ms   157 ms  100ge16-2.core1.lon2.he.net [72.52.92.165]
 14   168 ms   167 ms   166 ms  100ge7-1.core1.fra1.he.net [184.105.80.38]
 15   180 ms   180 ms   184 ms  184.104.204.250
 16   185 ms   179 ms   183 ms  46.19.136.225
 17   181 ms   179 ms   181 ms  46.19.136.150
 18   184 ms   181 ms   183 ms  179.43.184.130

Trace complete.

 

And from the server:

 

root@Subdivisions:~# traceroute -m 100 hdbits.org
traceroute to hdbits.org (179.43.184.130), 100 hops max, 60 byte packets
 1  pfSense.localdomain (192.168.3.1)  0.236 ms  0.223 ms  0.207 ms
 2  * * *
 3  096-034-106-128.biz.spectrum.com (96.34.106.128)  13.747 ms  13.729 ms  13.715 ms
 4  096-034-109-208.biz.spectrum.com (96.34.109.208)  11.666 ms  11.661 ms  11.648 ms
 5  096-034-109-139.biz.spectrum.com (96.34.109.139)  13.621 ms  13.303 ms  13.570 ms
 6  096-034-108-178.biz.spectrum.com (96.34.108.178)  19.715 ms  14.960 ms  19.084 ms
 7  bbr01sttlwa-tge-0-1-0-4.sttl.wa.charter.com (96.34.0.92)  18.646 ms  17.421 ms  19.549 ms
 8  prr01sttlwa-bue-1.sttl.wa.charter.com (96.34.3.29)  19.959 ms  18.600 ms  17.988 ms
 9  10ge2-1.core1.sea1.he.net (66.160.133.117)  17.562 ms  17.551 ms  17.540 ms
10  100ge1-2.core1.msp1.he.net (184.104.194.22)  67.235 ms  64.905 ms  66.036 ms
11  100ge13-1.core2.chi1.he.net (184.105.223.177)  73.053 ms  72.643 ms  75.201 ms
12  100ge1-2.core1.nyc4.he.net (184.104.193.174)  90.237 ms  90.189 ms  90.189 ms
13  100ge16-2.core1.lon2.he.net (72.52.92.165)  162.390 ms  161.516 ms  161.523 ms
14  100ge7-1.core1.fra1.he.net (184.105.80.38)  171.531 ms  165.929 ms  165.913 ms
15  184.104.204.250 (184.104.204.250)  180.416 ms  178.679 ms  178.223 ms
16  46.19.136.225 (46.19.136.225)  180.414 ms  179.547 ms  184.393 ms
17  46.19.136.150 (46.19.136.150)  184.941 ms  179.959 ms  180.930 ms
repeat

repeat
100  * * *
root@Subdivisions:~#

 

Other torrents are active on this tracker, just four are having the error.

 

 

Link to comment
On 5/19/2020 at 3:10 PM, binhex said:

ok remove the value for VPN_OPTIONS and then from the unraid console with the container running (NOT the containers console) run the following:-


docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh'

restart container, if no go then try the following:-


docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh'

then restart the container again.

 

i suspect one of these or maybe even both options are required for airvpn, i just dont know which.

Since yesterday morning, my PureVPN connection has been unable to connect. It looks like both of these options are now removed from /root/openvpn.sh — I've tried various combinations of these three options:

 

--pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'redirect-gateway sipv6' --pull-filter ignore 'dhcp-option DNS'

 

but none seems to work.

 

I've attached the log and the latest .ovpn file that I'm using. I downloaded that from PureVPN today, in case the certificates were out of date, but I get the same results. I'm assuming that file is right, but given how their website really makes you search for help if you're daring to not use their GUI, who knows?

 

Does anyone have any idea what could be going wrong here? It would be lovely to be rich enough to throw away the remaining 2.5 years on this PureVPN subscription and just pay PIA's rather higher prices, but it's not really an option, unfortunately…

sweden.ovpn vpn.log

Link to comment
9 hours ago, ElectricBadger said:

Since yesterday morning, my PureVPN connection has been unable to connect. It looks like both of these options are now removed from /root/openvpn.sh — I've tried various combinations of these three options:

 


--pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'redirect-gateway sipv6' --pull-filter ignore 'dhcp-option DNS'

 

but none seems to work.

 

I've attached the log and the latest .ovpn file that I'm using. I downloaded that from PureVPN today, in case the certificates were out of date, but I get the same results. I'm assuming that file is right, but given how their website really makes you search for help if you're daring to not use their GUI, who knows?

 

Does anyone have any idea what could be going wrong here? It would be lovely to be rich enough to throw away the remaining 2.5 years on this PureVPN subscription and just pay PIA's rather higher prices, but it's not really an option, unfortunately…

sweden.ovpn 5.18 kB · 0 downloads vpn.log 8.89 kB · 0 downloads

i can see two issues here, firstly the pushed route from purevpn seems to be invalid, thus this error:-

ERROR: Linux route add command failed: external program exited with error status: 2

and one of the options that you have specified for vpn_options (which you dont need to use), is wrong:-

--pull-filter ignore 'redirect-gateway sipv6'

sipv6 is not right, typo no doubt but remove all the vpn_options you dont need any of them.

 

so the first issue you will need to contact purevpn about, or try another endpoint, purevpn are not good im afraid, ive seen other issues with their configuration in the past.

Link to comment
16 hours ago, binhex said:

so the first issue you will need to contact purevpn about, or try another endpoint, purevpn are not good im afraid, ive seen other issues with their configuration in the past.

 

Thanks — I've opened a second ticket as they seem to be ignoring my first. Wonder if PayPal will authorise a refund this far along?

Link to comment
On 6/26/2020 at 1:12 AM, jeff.lebowski said:

Deluge 2.0.4dev23: "no route to host"

 

This has happened before, and it went away. I'd rather figure out what's going on and fix it instead of just waiting around. 

 

From my desktop:

 

Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\jeff.lebowski>tracert hdbits.org

Tracing route to hdbits.org [179.43.184.130]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.3.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms    15 ms  096-034-106-128.biz.spectrum.com [96.34.106.128]
  4    14 ms    12 ms     9 ms  096-034-109-208.biz.spectrum.com [96.34.109.208]
  5    10 ms     9 ms    18 ms  096-034-109-139.biz.spectrum.com [96.34.109.139]
  6    13 ms    14 ms    14 ms  096-034-108-178.biz.spectrum.com [96.34.108.178]
  7    24 ms    14 ms    24 ms  bbr01sttlwa-tge-0-1-0-4.sttl.wa.charter.com [96.34.0.92]
  8    19 ms    16 ms    19 ms  prr01sttlwa-bue-1.sttl.wa.charter.com [96.34.3.29]
  9    17 ms    22 ms    14 ms  10ge2-1.core1.sea1.he.net [66.160.133.117]
 10    62 ms    65 ms    73 ms  100ge1-2.core1.msp1.he.net [184.104.194.22]
 11    72 ms    76 ms    72 ms  100ge13-1.core2.chi1.he.net [184.105.223.177]
 12    86 ms    88 ms    88 ms  100ge1-2.core1.nyc4.he.net [184.104.193.174]
 13   161 ms   157 ms   157 ms  100ge16-2.core1.lon2.he.net [72.52.92.165]
 14   168 ms   167 ms   166 ms  100ge7-1.core1.fra1.he.net [184.105.80.38]
 15   180 ms   180 ms   184 ms  184.104.204.250
 16   185 ms   179 ms   183 ms  46.19.136.225
 17   181 ms   179 ms   181 ms  46.19.136.150
 18   184 ms   181 ms   183 ms  179.43.184.130

Trace complete.

 

And from the server:

 

root@Subdivisions:~# traceroute -m 100 hdbits.org
traceroute to hdbits.org (179.43.184.130), 100 hops max, 60 byte packets
 1  pfSense.localdomain (192.168.3.1)  0.236 ms  0.223 ms  0.207 ms
 2  * * *
 3  096-034-106-128.biz.spectrum.com (96.34.106.128)  13.747 ms  13.729 ms  13.715 ms
 4  096-034-109-208.biz.spectrum.com (96.34.109.208)  11.666 ms  11.661 ms  11.648 ms
 5  096-034-109-139.biz.spectrum.com (96.34.109.139)  13.621 ms  13.303 ms  13.570 ms
 6  096-034-108-178.biz.spectrum.com (96.34.108.178)  19.715 ms  14.960 ms  19.084 ms
 7  bbr01sttlwa-tge-0-1-0-4.sttl.wa.charter.com (96.34.0.92)  18.646 ms  17.421 ms  19.549 ms
 8  prr01sttlwa-bue-1.sttl.wa.charter.com (96.34.3.29)  19.959 ms  18.600 ms  17.988 ms
 9  10ge2-1.core1.sea1.he.net (66.160.133.117)  17.562 ms  17.551 ms  17.540 ms
10  100ge1-2.core1.msp1.he.net (184.104.194.22)  67.235 ms  64.905 ms  66.036 ms
11  100ge13-1.core2.chi1.he.net (184.105.223.177)  73.053 ms  72.643 ms  75.201 ms
12  100ge1-2.core1.nyc4.he.net (184.104.193.174)  90.237 ms  90.189 ms  90.189 ms
13  100ge16-2.core1.lon2.he.net (72.52.92.165)  162.390 ms  161.516 ms  161.523 ms
14  100ge7-1.core1.fra1.he.net (184.105.80.38)  171.531 ms  165.929 ms  165.913 ms
15  184.104.204.250 (184.104.204.250)  180.416 ms  178.679 ms  178.223 ms
16  46.19.136.225 (46.19.136.225)  180.414 ms  179.547 ms  184.393 ms
17  46.19.136.150 (46.19.136.150)  184.941 ms  179.959 ms  180.930 ms
repeat

repeat
100  * * *
root@Subdivisions:~#

 

Other torrents are active on this tracker, just four are having the error.

 

 

Crossing my fingers for some help.

Link to comment

How Can I tell if the vpn is working?

With the latest release yesterday my vpn speeds are a little unrealistic.

 

I hop to the terminal within the docker container and run a curl ifconfig.co and it DOES show my vpn ip, 

BUT: my speed has dramatically increased.. From 1-2mib/sec down to 25-30mib/sec down.. 6gb in 5 minutes? uhh..... that's not right.

I love the speed, but this seems unrealistic.

 

 

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.