binguser

You may have multiple containers with the (case-insensitive) word 'plex', which is throwing off the script. For example, I have Plex-Meta-Manager and Plex-Image-Cleanup. Make the grep command more specific to grab just the CPU load for the plex container, e.g.: plex_cpu_load=$(docker stats --no-stream | grep -i "plex\s" | awk '{sub(/%/, "");print $3}')

Hi binhex, Just FYI that the natpmpc commands for ProtonVPN have been updated: https://protonvpn.com/support/port-forwarding-manual-setup/ Specifically, the commands are now: natpmpc -g 10.2.0.1 natpmpc -a 1 0 tcp 60 -g 10.2.0.1 natpmpc -a 1 0 udp 60 -g 10.2.0.1

Have you tried leaving them blank? If you have the configuration file with keys in it it should work without having to put a username/password.

Using ProtonVPN and occasionally natpmpc will fail, has anyone else encountered this? Not sure if this is a ProtonVPN issue or a Deluge issue. This can go on for some time with Deluge unable to do any downloading/uploading meanwhile. The only "fix" I've found seems to be to switch to another server but even then it can arise again until I happen to find one where it doesn't... until it happens again later on. 2023-08-10 18:56:03,452 DEBG 'start-script' stderr output: readnatpmpresponseorretry() failed : the gateway does not support nat-pmp errno=11 'Resource temporarily unavailable' 2023-08-10 18:56:03,452 DEBG 'start-script' stdout output: [warn] Unable to assign an incoming port for protocol UDP, returning 1 from function... [warn] Unable to assign incoming port 2023-08-10 18:56:03,453 DEBG 'start-script' stdout output: [info] 11 retries left [info] Retrying in 10 secs... 2023-08-11 15:38:33,354 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 7 retries left 2023-08-11 15:38:35,706 DEBG 'start-script' stderr output: readnatpmpresponseorretry() failed : the gateway does not support nat-pmp errno=11 'Resource temporarily unavailable' 2023-08-11 15:38:35,706 DEBG 'start-script' stdout output: initnatpmp() returned 0 (SUCCESS) using gateway : ***.***.***.*** sendpublicaddressrequest returned 2 (SUCCESS) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -7 (FAILED)

I think the VPN FAQ should be updated, it mentions "Note:- The above is ONLY true for PIA users, the env var 'STRICT_PORT_FORWARD' does nothing for any other VPN providers." in A10.

Hi binhex, I'm using ProtonVPN and the latest image but the forwarded port is not being assigned correctly. As an alternative setup I'm also using GluetunVPN and binhex-deluge and that works with ProtonVPN. EDIT: I reinstalled the container and it's working now. Did a little testing and it seems the STRICT_PORT_FORWARD needs to be 'yes'. I thought the setting was solely for PIA? supervisord.log