[Support] binhex - SABnzbdVPN

[binhex]

Just in time for Friday night, aaaaaaaaaaand relax! 🙂

[srcnet]

I have a similar problem, but forcing it to update didn't fix it. This is a new setup, so it hasn't worked in the past.

 

2024-07-07 11:25:36.429516 [info] Host is running unRAID
2024-07-07 11:25:36.479135 [info] System information Linux xxx 6.1.74-Unraid #1 SMP PREEMPT_DYNAMIC Fri Feb  2 11:06:32 PST 2024 x86_64 GNU/Linux
2024-07-07 11:25:36.539109 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-07 11:25:36.597376 [info] PUID defined as '99'
2024-07-07 11:25:36.812854 [info] PGID defined as '100'
2024-07-07 11:25:36.965900 [info] UMASK defined as '000'
2024-07-07 11:25:37.023515 [info] Permissions already set for '/config'
2024-07-07 11:25:37.086714 [info] Deleting files in /tmp (non recursive)...
2024-07-07 11:25:37.168026 [info] VPN_ENABLED defined as 'yes'
2024-07-07 11:25:37.228004 [info] VPN_CLIENT defined as 'openvpn'
2024-07-07 11:25:37.285699 [info] VPN_PROV defined as 'pia'
2024-07-07 11:25:37.364695 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/bahamas-aes-256-gcm-udp-ip.ovpn
2024-07-07 11:25:37.486260 [info] VPN remote server(s) defined as 'panama.privacy.network,'
2024-07-07 11:25:37.535332 [info] VPN remote port(s) defined as '1197,'
2024-07-07 11:25:37.588995 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-07 11:25:37.649441 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-07 11:25:37.711845 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-07 11:25:37.770074 [info] NAME_SERVERS defined as '1.1.1.1'
2024-07-07 11:25:37.828988 [debug] iptables default policies available, setting policy to drop...
2024-07-07 11:25:37.893977 [debug] ip6tables default policies available, setting policy to drop...
Error: error sending query: Could not send or receive, because of network error
2024-07-07 11:25:53.034055 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
Error: error sending query: Could not send or receive, because of network error
2024-07-07 11:26:13.115609 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...

 

I believe the problem is the name servers are not being added to /etc/resolv.conf

sh-5.2# cat /etc/resolv.conf 
nameserver 127.0.0.11
options ndots:0

 

sh-5.2# iptables -S
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p tcp -m tcp --sport 53 -j ACCEPT
-A INPUT -d 127.0.0.11/32 -j ACCEPT
-A INPUT -s 127.0.0.11/32 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 53 -j ACCEPT
-A OUTPUT -d 127.0.0.11/32 -j ACCEPT
-A OUTPUT -s 127.0.0.11/32 -j ACCEPT

 

I tried to create a script to fix and enabled ENABLE_STARTUP_SCRIPTS, but it doesn't seem to run.

sh-5.2# cat /config/scripts/setdns.sh 
#!/bin/bash

# Use resolv.conf for systems without systemd-resolved
sudo echo "nameserver 1.1.1.1" > /etc/resolv.conf

# echo "options ndots:0" >> /etc/resolv.conf
echo "Cloudflare DNS (1.1.1.1) set using resolv.conf."

 

If I manually run the script, everything works.

2024-07-07 11:31:14.347164 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
Error: error sending query: Could not send or receive, because of network error
2024-07-07 11:31:34.430559 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
2024-07-07 11:31:39.508413 [debug] DNS operational, we can resolve name 'panama.privacy.network' to address '91.90.126.54 91.90.126.85 91.90.126.93'
2024-07-07 11:31:39.604011 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '172.64.151.73 104.18.36.183'
2024-07-07 11:31:39.696812 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.18.159.201 104.19.240.167'
2024-07-07 11:31:39.779550 [debug] Showing name servers in '/etc/resolv.conf' before overwrite from NAME_SERVERS...
2024-07-07 11:31:39.830473 [debug] nameserver 1.1.1.1
2024-07-07 11:31:39.890398 [debug] Showing name servers in '/etc/resolv.conf' after overwrite from NAME_SERVERS...
2024-07-07 11:31:39.942423 [debug] nameserver 1.1.1.1
2024-07-07 11:31:40.516230 [debug] Docker interface name, Gateway interface name, Gateway IP, Docker interface IP, Subnet mask and CIDR are defined as 'eth0,eth0,192.168.0.123,192.168.0.102,255.255.255.0,192.168.0.0/24'
2024-07-07 11:31:40.724860 [info] LAN_NETWORK defined as '192.168.0.0/24'
2024-07-07 11:31:40.812496 [info] LAN_NETWORK exported as '192.168.0.0/24'
2024-07-07 11:31:40.877175 [info] VPN_USER defined as 'xxx'
2024-07-07 11:31:40.939152 [info] VPN_PASS defined as 'xxx'
2024-07-07 11:31:40.999706 [info] STRICT_PORT_FORWARD defined as 'no'
2024-07-07 11:31:41.067426 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-07-07 11:31:41.125338 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-07-07 11:31:41.184590 [info] ENABLE_STARTUP_SCRIPTS defined as 'yes'
2024-07-07 11:31:41.243585 [info] ENABLE_SOCKS defined as 'no'
2024-07-07 11:31:41.303996 [info] ENABLE_PRIVOXY defined as 'no'
2024-07-07 11:31:41.637025 [info] Executing user script '/config/scripts/setdns.sh' in the foreground...
2024-07-07 11:31:41.688619 [script] Cloudflare DNS (1.1.1.1) set using resolv.conf.
2024-07-07 11:31:41.749979 [info] Starting Supervisor...
2024-07-07 11:31:42,330 INFO Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing
2024-07-07 11:31:42,330 INFO Set uid to user 0 succeeded
2024-07-07 11:31:42,336 INFO supervisord started with pid 7
2024-07-07 11:31:43,340 INFO spawned: 'start-script' with pid 566
2024-07-07 11:31:43,343 INFO spawned: 'watchdog-script' with pid 567
2024-07-07 11:31:43,344 INFO reaped unknown pid 8 (exit status 0)
2024-07-07 11:31:43,355 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-07-07 11:31:43,355 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-07 11:31:43,356 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
<snip>

 

So it seems like it gets stuck trying to resolve, before adding the addresses to /etc/resolv.conf or running the scripts.

[skel2raw]

Hi guys, since a couple of days I have the issue, that the webui is not opening up anymore. First I had thiss iusse with binhey-qbittorrentvpn and now with the sabnzbdvpn package as well. Is this a known issue and is there an easy fix?

Replacing vpn config files didn't help, fresh install didn't help either.

[binhex]

2 hours ago, skel2raw said:

Hi guys, since a couple of days I have the issue, that the webui is not opening up anymore. First I had thiss iusse with binhey-qbittorrentvpn and now with the sabnzbdvpn package as well. Is this a known issue and is there an easy fix?

Replacing vpn config files didn't help, fresh install didn't help either.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

[skel2raw]

Here you go

supervisord.log CommandExecution.txt

[binhex]

1 hour ago, skel2raw said:

Here you go

supervisord.log 63.17 kB · 0 downloads CommandExecution.txt 1.26 kB · 0 downloads

nothing obviously wrong in the logfile, what is the IP address of the machine you are using to attempt connection to sabnzbd web ui?

[skel2raw]

2 hours ago, binhex said:

nothing obviously wrong in the logfile, what is the IP address of the machine you are using to attempt connection to sabnzbd web ui?

192.168.178.103

 

But nothing changed on the network side. Strange thing is, that radarr, sonarr etc. are able to download via sabnzbd just as usual. The only thig not working is the web ui. When I click on "WebUi" nothing happens.

I installed another container for qbittorrentvpn and there it works just as usual. I guess it will work with another sabnzbd container as well. But I'd like to avoid chaning a running system.

[binhex]

2 hours ago, skel2raw said:

192.168.178.103

that will be your problem, from your log:-
2024-07-08 14:20:29.693021 [info] LAN_NETWORK defined as '192.168.1.0/24'

 

Please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[srcnet]

Any thoughts on my problem above? 

 

[binhex]

21 minutes ago, srcnet said:

Any thoughts on my problem above? 

 

 try the following:-

 

login to unraid web ui

go to docker tab

left click container and select 'edit' and switch back repository to tag 'latest' and apply

toggle switch top right to 'advanced view' on main docker screen (not edit screen)

click on 'force update' for the container, this will force a refresh of tagged image latest

check logs for errors.

[srcnet]

1 hour ago, binhex said:

 try the following:-

 

login to unraid web ui

go to docker tab

left click container and select 'edit' and switch back repository to tag 'latest' and apply

toggle switch top right to 'advanced view' on main docker screen (not edit screen)

click on 'force update' for the container, this will force a refresh of tagged image latest

check logs for errors.

 

Thanks for taking a look. That didn't seem to make a difference. Same problem as above.

 

Pulling image: binhex/arch-sabnzbdvpn:latest
IMAGE ID [468579942]: Pulling from binhex/arch-sabnzbdvpn.
Status: Image is up to date for binhex/arch-sabnzbdvpn:latest

TOTAL DATA PULLED: 0 B


Stopping container: binhex-sabnzbdvpn
Successfully stopped container: binhex-sabnzbdvpn


Removing container: binhex-sabnzbdvpn
Successfully removed container: binhex-sabnzbdvpn


Command execution
docker run
  -d
  --name='binhex-sabnzbdvpn'
  --net='eth0'
  --ip='192.168.0.102'
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-sabnzbdvpn"
  -e 'TCP_PORT_8080'='8080'
  -e 'TCP_PORT_8118'='8118'
  -e 'TCP_PORT_9118'='9118'
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='xxx'
  -e 'VPN_PASS'='xxx'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='openvpn'
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.0.0/24'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='true'
  -e 'TCP_PORT_58946'='58946'
  -e 'UDP_PORT_58946'='58946'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='yes'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='1.1.1.1'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://192.168.0.102:8080'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png'
  -v '/mnt/user/appdata/binhex-sabnzbdvpn':'/config':'rw'
  -v '/mnt/user/IT/downloadsarr/':'/data':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-sabnzbdvpn:latest'

The command finished successfully!

 

[skel2raw]

10 hours ago, binhex said:

that will be your problem, from your log:-
2024-07-08 14:20:29.693021 [info] LAN_NETWORK defined as '192.168.1.0/24'

 

Please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Oh wow I'll check that. But it's weird because I didn't change anything on the IP configuration of my network or the dockers and everything was working flawlessly for months. Might this have happened during an update?

[binhex]

2 hours ago, skel2raw said:

Might this have happened during an update?

Template changes to do not get pushed out, but if you reinstalled sabnzbdvpn from CA (community applications) then its possible you forgot to change this value, in any case this will be your fix.

[Veregon]

I am having the same issue with not being able to bring up the UI. I've been running this image for years with no issue.

supervisord.log command_execution.txt

[Waltm]

I'm also having the same problem of no UI after working for several years. I'm not sure exactly when this started but just noticed it today.

supervisord.log Command execution.txt

[binhex]

On 7/16/2024 at 5:57 PM, Veregon said:

I am having the same issue with not being able to bring up the UI. I've been running this image for years with no issue.

supervisord.log 26.56 kB · 1 download command_execution.txt 1.23 kB · 1 download

 

10 hours ago, Waltm said:

I'm also having the same problem of no UI after working for several years. I'm not sure exactly when this started but just noticed it today.

supervisord.log 28.45 kB · 1 download Command execution.txt 1.21 kB · 0 downloads

you both have the same issue, you have set STRICT_PORT_FORWARD to 'yes' but are attempting connection to a endpoint that does not support port forwarding, either change the endpoint you are connecting to to be a port forward enabled endpoint (see your log for a list of these) or set STRICT_PORT_FORWARD to 'no' if you do not require an incoming port.

[Waltm]

6 hours ago, binhex said:

 

you both have the same issue, you have set STRICT_PORT_FORWARD to 'yes' but are attempting connection to a endpoint that does not support port forwarding, either change the endpoint you are connecting to to be a port forward enabled endpoint (see your log for a list of these) or set STRICT_PORT_FORWARD to 'no' if you do not require an incoming port.

 

Thank you for your quick reply.  I'm sorry to follow up with what are probably basic questions, but where is the setting for STRICT_PORT_FORWARD?  I didn't see it in the edit screen.  Also, it is always trying to connect to 'us-newyorkcity.privacy.network' even though that is not what I have in the settings. None of the US servers have port forwarding and it was set to one in Europe, but I have tried to enter several others on the settings page.  Is there some place else I should be changing this?  

 

I'm assuming there was a change either on SAB or the VPN side of things since this is a new issue.

 

[binhex]

5 hours ago, Waltm said:

I'm sorry to follow up with what are probably basic questions, but where is the setting for STRICT_PORT_FORWARD?  I didn't see it in the edit screen.

You must have an older template, you will need to add it in:-

 

click on edit for the container

click on Add another Path, Port, Variable, Label or Device

set config type to variable

set key to STRICT_PORT_FORWARD and set value to 'no'

 

5 hours ago, Waltm said:

Also, it is always trying to connect to 'us-newyorkcity.privacy.network' even though that is not what I have in the settings. None of the US servers have port forwarding and it was set to one in Europe, but I have tried to enter several others on the settings page.  Is there some place else I should be changing this?  

Not sure where you have seen 'VPN REMOTE' but its not a valid env var and therefore will do nothing, if you want to change endpoint then Please see Q10 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[Waltm]

20 hours ago, binhex said:

You must have an older template, you will need to add it in:-

 

Thank you, this worked.  If there is an advantage to using port forwarding with this container I will edit the list of endpoints to only those that support it.

[binhex]

10 minutes ago, Waltm said:

Thank you, this worked.  If there is an advantage to using port forwarding with this container I will edit the list of endpoints to only those that support it.

Port forwarding is not used by SABnzbd BUT if you route other containers through the network of this container then it is entirely possible you may want an incoming port, thus the reason it was added.

[Veregon]

On 7/20/2024 at 8:04 AM, binhex said:

 

you both have the same issue, you have set STRICT_PORT_FORWARD to 'yes' but are attempting connection to a endpoint that does not support port forwarding, either change the endpoint you are connecting to to be a port forward enabled endpoint (see your log for a list of these) or set STRICT_PORT_FORWARD to 'no' if you do not require an incoming port.

Thanks, that fixed it for me! Not sure how it got turned on since this has been running for a long time.

[Emphyrio]

Edit: I found my answer. There was some scheduling active that set the Speed Limit. Fixed it!

 

Whenever I restart the Sabnzbd container, the download speed limit gets set to 12MB/s. This is ignoring the Tuning settings (set to a line speed of 60 MB/s and to use 100% of line speed). I can manually adjust the slider, that works. But the slider resets to 12 MB/s after some time (every time after a container restart/update, perhaps more often but I can´t pinpoint that).

 

How can I change this behaviour? I would like to download at full speed of course 🙂

 

Some background:

• I recently upgraded my internet speed to 1 Gbit/s, it used to be 100 Mbit/s. Sabnzbd seems to be stuck on the previous speed.
• Screenshots of relevant settings are attached.
• Whatever I set as 'maximum line speed', after restarting the limit always gets set to 12 MB/s. E.g. maximum line speed = 100 MB/s, then the limit will be 12%. Maximum line speed = 60 MB/s, then the limit will be 20%.

 

 

Edited August 11 by Emphyrio
solution was found

[skel2raw]

On 7/8/2024 at 10:45 PM, binhex said:

that will be your problem, from your log:-
2024-07-08 14:20:29.693021 [info] LAN_NETWORK defined as '192.168.1.0/24'

 

Please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Finally I moved to my new place and setup my network again. I did check the IP address issue and corrected it. The "192.168.1.0/24" IP was in the default field which I now changed accordingly to 192.168.178.0/24.

Unfortunately this did not resolve the issue. In addition I now have the problem that almost all of by binhex containers (sonarr, radarr, readarr) are not bringing up the UI either. I did not change anything in the configuration, just usual automatic updates of the containers.

Am I really the only one who is having this issue?

 

Edit:

After looking further and playing around with the settings I figured out, that the issue is somehow caused by the "Network Type" setting. With "Custom:Br0" the UI is not coming up, however when I change it to "Bridge" the webui is coming up again.

 

Edit2:

It seems that for some reason with br0 the portmappings are gone. When I create a new custom network the portmappings are back again and I cann access the UI. Do you know how I can geht the portmappings for the containers on the br0 network back?

Edited August 16 by skel2raw

[EX1]

Thanks for the dockers Binhex!

I upgraded to version 7 of unraid and now when sabnzbdvpn docker is connected to PIA, I can no longer access the webUI. Disabling the VPN allows access to the webUI again. I am embarrassed to ask this, but what am I missing here? webUI port is still set to 8080, Radarr to 7878, and Sonarr to 8989. 

ifconfig.io shows the VPN IP when ran in the dockers so I know I am connected. Sonarr and Radarr both report that the download client in now unreachable and I see the same connection refused error that appears when I try to open the webUI.

I have disabled port forward but this did not resolve the issue. I also created a new ovpn file from PIA with one of the port forward servers just to be sure.

 

supervisord.log.txt

Edited August 19 by EX1

[llamabama]

What's the deal with this /shared path that's down in the more settings of the template? What's the recommendation for where to map it?