[[Support] binhex - DelugeVPN]

On 8/27/2021 at 1:31 PM, binhex said:

yeah i appreciate you have a high speed line, but what is connected to the end of the line?, a cheap ISP router i would suffice, your Unifi Dream Machine does not come into this, as this is simply a AP, try reducing the number of connections in deluge as well, also reduce the upload rate, if its set to unlimited this will def cause issues.

 

On 8/27/2021 at 1:05 PM, binhex said:

i dont see any dns failure in the log you posted above, can you please do the following and attempt to replicate the issue https://github.com/binhex/documentation/blob/master/docker/faq/help.md

So i went through the steps in the help.md, and everything looks to work as it should now.

 

Just to note, i didnt change anything except deleting and install the container again - every container setting and Deluge setting is the same.

• I already did have a upload limit (25mb/s)
• 40 mb/s download limit
• Had 100 connection limit per torrent (250 global)

Regarding the Unifi Dream Machine, i think you are mistaken - It's just not an AP, it is a full fledged router, but with a built-in and more than capable of running full 1gbit, so the issues wasn't there.

But! it works now, so that's great  (for now at the very least)

I wonder though why just plain a old delete/install worked?

Thanks the the help @binhex

[[Support] binhex - DelugeVPN]

5 minutes ago, binhex said:

no, your physical router.

Ah well i'm pretty sure that's not the case - i have a full 1gbit ISP line, and am only consuming half of that for Deluge.
Spec wise, i'm using a Unifi Dream Machine, and the rest of my home never has any downtime coinciding with what's happening in the delugevpn container.

I tried limiting bandwith to 350mbit, but the same thing is still happening
Also enabled debug output for logging, but nothing of interest really shows up i feel.

 

2021-08-27 12:52:35,597 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2021-08-27 12:52:35,704 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.176.196'

2021-08-27 12:52:35,707 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2021-08-27 12:52:35,740 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2021-08-27 12:52:35,764 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 45387
[debug] Deluge incoming port is 45387
[debug] VPN IP is 10.24.153.129
[debug] Deluge IP is 10.24.153.129

2021-08-27 12:53:05,770 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2021-08-27 12:54:48,884 WARN received SIGTERM indicating exit request
2021-08-27 12:54:48,885 DEBG killing watchdog-script (pid 169) with signal SIGTERM
2021-08-27 12:54:48,886 INFO waiting for shutdown-script, start-script, watchdog-script to die
2021-08-27 12:54:49,887 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22905190581680 for <Subprocess at 22905190580672 with name watchdog-script in state STOPPING> (stdout)>
2021-08-27 12:54:49,888 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 22905190581728 for <Subprocess at 22905190580672 with name watchdog-script in state STOPPING> (stderr)>
2021-08-27 12:54:49,888 INFO stopped: watchdog-script (terminated by SIGTERM)
2021-08-27 12:54:49,889 DEBG received SIGCHLD indicating a child quit
2021-08-27 12:54:49,889 DEBG killing start-script (pid 168) with signal SIGTERM
2021-08-27 12:54:50,891 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22905190407136 for <Subprocess at 22905190406464 with name start-script in state STOPPING> (stdout)>
2021-08-27 12:54:50,892 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22905190581152 for <Subprocess at 22905190406464 with name start-script in state STOPPING> (stderr)>
2021-08-27 12:54:50,892 INFO stopped: start-script (terminated by SIGTERM)
2021-08-27 12:54:50,893 DEBG received SIGCHLD indicating a child quit
2021-08-27 12:54:50,893 DEBG killing shutdown-script (pid 167) with signal SIGTERM
2021-08-27 12:54:50,894 DEBG 'shutdown-script' stdout output:

 

[[Support] binhex - DelugeVPN]

1 hour ago, binhex said:

its possible you are flooding your router and getting into a situation where Deluge is consuming all available bandwidth and thus stopping name resolution from happening, try throttling deluge back to say 450 Mb/s and see if that helps.

I'll try it out and report back.
But when you say router - what do you exactly mean? the routing inside the container?

[[Support] binhex - DelugeVPN]

Hi all, first time poster - long time lurker

I'm having a few issues - primarily when trying to use Wireguard as a protocol.
Everything is nice and dandy, right up until a few minutes into maxing out the bandwith (i have 1gbit fiber, but it seems to max out at 550mbit on Wireguard).
Anyhow - the internet connection simply stops working in the container and then the container restarts since it fails to resolve DNS and etc.. but Wireguard is still dead despite restarting the container and i then run into a restart loop until it work again after maybe 15 minutes or so.

 

I do suspect that this is a fault in PIA's side though.. am i correct in this assumption?

OpenVPN ẃorks as intended btw, but speeds are maxed at 220mbit :/