helpermonkey

Here is my docker run for Deluge: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'=REMOVED' -e 'VPN_PASS'='REMOVED' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='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' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'ADDITIONAL_PORTS'='7878,8080,8989,8090,9117' -e 'VPN_CLIENT'='wireguard' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -p '7878:7878/tcp' -p '8080:8080/tcp' -p '8989:8989/tcp' -p '9117:9117/tcp' -p '8083:8083/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn' d976542d729d15115b01223b4e7ebf0ef2808e27c3166100aff6d157e8667580 The command finished successfully! And here it is for SAB: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-sabnzbd' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-sabnzbd':'/config':'rw' --net=container:binhex-delugevpn 'binhex/arch-sabnzbd' 3705fbd979cd8e0906af3032ed41fa19b3bd1b62b2acd046308f009567b2128e The command finished successfully!

Thanks - so I had already restarted by the time i saw this but i did run fix common problems and i guess i do have something misconfigured as you will see in the screenshot. that said, i'm not sure where exact;y the problem is. Attached is the diagnostics per the request - i hope it has sufficient information but just in case ... here's what i'm trying to accomplish: - My cache drive has an appdata share and a downloads share created on it. The appdata share is set to only for cache and the downloads is set to yes. The idea is that my appdata share houses all of my docker configurations and then the downloads share is where anything is downloaded to first before being moved to my data drives. Will post anything else you need. Thanks! buddha-diagnostics-20210407-1454.zip

So I am getting errors like this: 04-06-2021 00:54 Docker critical image disk utilization Alert [BUDDHA] - Docker image disk utilization of 100% Docker utilization of image file /mnt/cache/docker.img alert However, I have a 1TB cache drive so i'm not sure why this is happening. Of note it says in the explorer that i have 54.5gb used - which seems high to me. The docker img itself displays as 21.5 gb. and the drive shows 945gb free. No idea why this is happening - the only thing i can think of is it has to do with my SAB installation perhaps? But i map those downloads to /data/Incomplete and /data/Complete which resides under my downloads share (also on the cache). Happy to share other information but wasn't sure what would be useful.

Not entirely sure how to troubleshoot this - I get these messages quite a bit these days: Docker high image disk utilization: 04-01-2021 05:02 Warning [BUDDHA] - Docker image disk utilization of 87% Docker utilization of image file /mnt/cache/docker.img I have a 1TB cache drive and when i look at the files in the Unraid GUI - the docker.img file has been 21.5g for quite some time. One thing that I *think* it may be is that due to a really long winded situation - i ended up having to do a clean install of my SAB installation and for a little bit it was DLing files into a subfold in the container path. That said, it never got anywhere near 1TB in downloaded files at a single time. I have been able to change the DL paths for incomplete / complete into my downloads share - so perhaps i've already solved this problem but just wanted to check here.

okay -yup it's a bug. they've fixed it but my guess is it won't impact me until you have a chance to update the docker? I am happy to switch so correct me if i'm wrong here's a rough outline of what i need to do. 1) disable vpn in delugevpn 2) Uninstall sabnzbd and install Sabnzbdvpn 3) then basically do everything i did to get delugevpn setup but instead point all of those containers to SAB and change that extra parameter to reference SABnzbdvpn and not delugevpn? Would you still suggest the change once you're able to update the delugevpn docker?

UPDATE: So I wiped the ini file and started over & now SAB won't load the gUI again (same error message). If i need to post in that thread let me know but here's what i did (the end result is that the log is spitting out the same information as you have quoted me on). - I started with a new ini. - logged in to the SAB Gui - rentered by usenet credentials. - went to the configuration page and pointed all of the folder paths to /data/complete/<insert category name here..eg... tv, movies, etc> - went to sonarr and radarr and updated the api key for SAB. - went back to sab and tried to change hte folder paths to /data/complete and /data/incomplete. At that point it said the folder wasn't empty so it couldn't do that. - logged in with krusader and moved the files out of the appdata folder and into the data/incomplete folder. - Tried to change the paths in the SAB GUI, hit save - got the same error message. - Shut down SAB. Turned sab back on. That error that you quoted has reappeared and i cannot access the docker gui anymore.

Okay - so i left things alone for an hour - and i can get back into the deluge GUI. I still can't access the sab gui using either ipaddress:8080 or servername.local:8080

192.168.1.199

ah whoops - yes sorry that was something i tried and forgot to switch it back. FYI - i havej sut switched it back and i'm still not able to access Deluge or SAB gui.

Okay - attached are screen shots of SAB & Deluge (taken before i turned debug on in deluge) as well as the log files per those instructions. supervisord.log supervisord.log

I have been having all sorts of problems and need some help getting everything functional again. Here's a brief timeline of what's gone on. With the recent updates to a variety of dockers, it seems that some configuration changes were needed on my end to get my "setup" functional. Essentially - running DelugeVPN in conjunction with sonarr, radarr, jackett, and sab. With some help from folks here - i managed to work my way through https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md After doing so, everything seemed to be working without trouble. Sometime later, I was unable to access the SAB GUI. Here is a log file from SAB that shows the problems i was having there. https://pastebin.com/cXiZcNwm After being advised to give the fAQ another try - I attempted to add "VPN_INPUT_PORTS" with a value of 8080 to my container. Upon applying that, the command failed - i was taken back to the list of installed dockers and the docker had disappeared. I returned my previously installed apps page - installed it again and again continued to get a command failed notice due to bindings. I restarted my server, all off my dockers are listed again and everything "seems" okay - however, I can't get into DelugeVPN GUI anymore due to the following: 2021-03-15 20:17:47,497 DEBG 'start-script' stderr output: parse error: Invalid numeric literal at line 4, column 0 2021-03-15 20:17:47,956 DEBG 'start-script' stderr output: parse error: Invalid numeric literal at line 1, column 7 2021-03-15 20:17:47,957 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL 'https://143.244.41.129/authv3/generateToken' [info] Retrying in 10 secs... Meanwhile I still cannot access SAB's GUI due to the aforementioned log file (the latest logs have the same exact errors). I can access sonarr and radarr without trouble and both seem to be functional save for sending anything to SAB. Search and such works no problemo. Any idea what's going on here?

okay now something new is happening - i will post over there.

@binhexwondering if you have any thoughts on this ... is it a bug or something else that may be unrelated to the container?

Just wondering if anyone has some thoughts - happy to provide more information if something else is needed to help fix the problem.

So i'm having a problem where I cannot get into SABNZB and i'm occasionally seeing a high image disk utilization warning on my docker image (which sits on a 1TB drive and is "supposedly" 21.5 gb. In addition, i cannot access the SAB Gui. All of my media related containers are binhex docs and i run them through Deluge vpn (sonarr/radarr/jacket). All of them work fine except SAB. Recently, when i went to upgrade to 6.9.0, something happened with my cache drive so i had to reformat it and restore all my cache data from a backup. Then i transitioned to using the wireguard protocol on my VPN and after doing that - everything was running fine. However, shortly thereafter, SAB "broke". I've read that these problems may be due to misconfiguration per this post... However, in both deluge and sab here is how it's set up: https://ibb.co/LYKNt0Y here are my settings for sab: https://ibb.co/Cm0qw83 here are my settings for deluge: https://ibb.co/42yMs9c here's a log file from SAB: https://pastebin.com/EjtAMTL8 I'm happy to run people through how I arrived at this point and I may have used some of the nomenclature incorrectly but I hope what you have is enough to go on. Thanks.

I cannot access the SAB GUI. I am running things through delugeVPN with PIA wireguard. here is a portion of my log file: https://pastebin.com/cXiZcNwm All of my other containers running the same way (Radarr, Sonarr, Jacket) are all up and running no problem. Someone suggested it might be a bug and i'm not sure. I am running the latest stable of all containers.

So i switched my endpoint to "Endpoint = ca-toronto.privacy.network:1337" and now when i try to launch SAB it won't open. Sonarr and Radarr and Deluge and such all work just fine. Here's a log from when i rebooted everything ... https://pastebin.com/cXiZcNwm any thoughts?

ha! tried to delete that before you saw it so as to not waste your time! found it 🙂

thanks i will add that extra parameter then.

That's great - i had it set to privelaged so i just added that. Out of curiosity - which endpoint do you use? Am I correct in that we have to use one of them listed under the port fowarding options here - https://www.privateinternetaccess.com/pages/client-support/? Thanks. I didn't have to do that though. I just followed @Hoopster's advice

Trying to follow the A.21 from https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md and i'm having problems. I am a PIA user. Step 1 is to change the docker parameter from --cap-add=NET_ADMIN to --privileged=true. However, I don't see that NET_ADMIN parameter in place. Should I simply enter in --privileged=true i nthe Extra parameters field?

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?

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.

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?

ever since i had to put the new system in place my downloads have been uber slow. I am using PIA and the CA-Montreal endpoint. Has anyone else experience very slow DL speeds with something like this? Is there a solution? Is there another PIA endpoint that people would suggest - i live in the eastern US if that makes a difference. In addition, the docker seems to only stay up for 12-20 hours at a time. i've noticed since the change that the other dockers that are pointed to it (sab,radarr,sonarr,jackett) that they end up having to rebuild as well - which makes sense b/c if the vpn is restarted they too need to restart.