Using A VPN w. Docker - Some Questions on Speed (Deluge, SAB, Radarr, Sonarr, Etc...)

[helpermonkey]

Hi folks,

I'm one of those "knows enough to screw things up kind of person" so please bear with me.

 

I use Private Internet Access and have a Unifi network. FWIW.

 

In any event, I use Binhex-DelugeVPN as well as Radarr, Sonarr, Jackett, and SAB. Recently, some stuff was changed that required me to adjust how my dockers worked together to make sure i'm on my VPN. I'm not sure what - it's above my pay grade so to speak but regardless, i've changed all the necessary things so my system is working again. Since then, I've noticed some "slowness" around these things and wanted to see if anyone could help me figure out what if anything can be done to speed things back up. I'm aware that VPNs are subject to speed fluctuations and such.

 

Symptom 1: The DL speeds on SAB seem to be quite slow. I haven't seen it exceed 7 or 8 mbps down since the change. I am using CA-Montreal endpoint - might that be the problem? That's obviously a PIA issue but if someone uses PIA maybe you'll know what's what. I'm in the US in EST and there is a PIA server in my city.

 

Symptom 2: Opening Radarr, Sonarr, SAB, seems to take a moment or two longer than I would expect. Here's a recent ping report - i see 4 times that are abnormally high. I'm suspecting this is a local issue?
 

PING server.local (192.168.1.199): 56 data bytes
64 bytes from 192.168.1.199: icmp_seq=0 ttl=64 time=1.826 ms
64 bytes from 192.168.1.199: icmp_seq=1 ttl=64 time=2.659 ms
64 bytes from 192.168.1.199: icmp_seq=2 ttl=64 time=2.326 ms
64 bytes from 192.168.1.199: icmp_seq=3 ttl=64 time=1.473 ms
64 bytes from 192.168.1.199: icmp_seq=4 ttl=64 time=1.504 ms
64 bytes from 192.168.1.199: icmp_seq=5 ttl=64 time=2.475 ms
64 bytes from 192.168.1.199: icmp_seq=6 ttl=64 time=2.625 ms
64 bytes from 192.168.1.199: icmp_seq=7 ttl=64 time=25.225 ms
64 bytes from 192.168.1.199: icmp_seq=8 ttl=64 time=62.974 ms
64 bytes from 192.168.1.199: icmp_seq=9 ttl=64 time=25.211 ms
64 bytes from 192.168.1.199: icmp_seq=10 ttl=64 time=30.587 ms
64 bytes from 192.168.1.199: icmp_seq=11 ttl=64 time=2.577 ms
64 bytes from 192.168.1.199: icmp_seq=12 ttl=64 time=1.438 ms
64 bytes from 192.168.1.199: icmp_seq=13 ttl=64 time=1.878 ms
64 bytes from 192.168.1.199: icmp_seq=14 ttl=64 time=1.600 ms
64 bytes from 192.168.1.199: icmp_seq=15 ttl=64 time=2.452 ms
64 bytes from 192.168.1.199: icmp_seq=16 ttl=64 time=2.711 ms

 

FWIW - i've run several pings and thse 25+ ms times have not appeared in any of the other reports. It usually takes around 5-6 seconds for any of the GUIs to open.

 

Any suggestions on what to do?

Edited March 10, 2021 by helpermonkey

[eat_eat_the_doreets]

For symptom 1, look in the binhex-delugevpn thread or on dockerhub for his instructions on how to change your endpoint. You should definitely use a New York or something endpoint, you don't need your traffic to go through Montreal for no reason. It's just editing a text file then restart the container. For me it's here:

 

/mnt/cache/appdata/binhex-delugevpn/wireguard/wg0.conf

(private information omitted...) 
Endpoint = ca-toronto.privacy.network:1337 

 

For symptom 2, I'm not really sure 30ms is anything to be concerned about. It might vary widely if you're on wireless, your router /AP are busy, etc... 5 to 6 seconds really doesn't seem like a problem

[tjb_altf4]

I set up a separate PrivoxyVPN container for all my searcher apps, that way they shouldn't be impacted by heavy loads (or my own maintenance) in the delugevpn container.

PIA is pretty generous and gives you 10 simultaneous connections.

[helpermonkey]

53 minutes ago, eat_eat_the_doreets said:

For symptom 1, look in the binhex-delugevpn thread or on dockerhub for his instructions on how to change your endpoint. You should definitely use a New York or something endpoint, you don't need your traffic to go through Montreal for no reason. It's just editing a text file then restart the container. For me it's here:

 

/mnt/cache/appdata/binhex-delugevpn/wireguard/wg0.conf

(private information omitted...) 
Endpoint = ca-toronto.privacy.network:1337 

 

For symptom 2, I'm not really sure 30ms is anything to be concerned about. It might vary widely if you're on wireless, your router /AP are busy, etc... 5 to 6 seconds really doesn't seem like a problem

thanks - i used to be on toronto and then it stopped working for me. I am on wireless but just thought it was a little concerning that it was taking "that long". i will not worry about that in the future.

[helpermonkey]

4 minutes ago, tjb_altf4 said:

I set up a separate PrivoxyVPN container for all my searcher apps, that way they shouldn't be impacted by heavy loads (or my own maintenance) in the delugevpn container.

PIA is pretty generous and gives you 10 simultaneous connections.

yeah that's why i am a little surprised .... i actually am not using torrenting anymore since my ISP put in a data cap so the only thing that's downloading is SAB and it's only pulling one file at a time. I'm not using heavy networking stuff otherwise - so just curious - what do you think might be causing the slow down?