[Support] binhex - SABnzbdVPN - Page 69 - Docker Containers

August 28, 20241 yr

I have this back to working but only by using UDP instead of TCP with PIA, and by disabling Strict Port Forward even though I selected a supported server according to PIA.

Not sure where the issue lies.

Quote

August 29, 20241 yr

Hi all, have recently been having an issue where Sab is saying that I have 0 Bytes available. The data folder that Sab reads/writes to resides on my Cache pool and overflows to the array. The cache pool itself has almost 3TB free and the array has quite a bit more than that so I am not sure what is going on. This has never been an issue until yesterday. I did lose a couple of disks last week and the replacements showed up today so I am running a data rebuild right now but this was a problem before the rebuild started. I even went as far as uninstalling and re-installing Sab with no luck. Any idea where is it pulling that free storage number from?

Edit: If I clear my config and setup sab from scratch it shows the correct amount of free space.

Edited August 29, 20241 yr by IndianaJoe1216

Quote

September 5, 20241 yr

I restarted the container today and the PIA Wireguard is not working, the logs show:

Quote

[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

OpenVPN works fine still.

Quote

September 9, 20241 yr

On 8/16/2024 at 3:26 AM, skel2raw said:

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?

I'm having the same issue with all my binhex dockers. In the docker overview there is nothing in the "Port Mapping" column and the majority of my dockers are using custom networks. This was all working fine for years, and seems to have broken recently, perhaps with the last unraid upgrade?

Did you ever figure out a workaround? I'd like to avoid creating all new custom networks and remapping everything.

Quote

September 10, 20241 yr

18 hours ago, Slappy said:

I'm having the same issue with all my binhex dockers. In the docker overview there is nothing in the "Port Mapping" column and the majority of my dockers are using custom networks. This was all working fine for years, and seems to have broken recently, perhaps with the last unraid upgrade?

Did you ever figure out a workaround? I'd like to avoid creating all new custom networks and remapping everything.

Unfortnuately I did not figure out what exactly caused this issue. I eventually ended up creating new custom networks and avoiding br0. I also think it has to do with a recent Unraid update. Though this issue began with the binhex dockers, it was not limited to those. It also happend e.g. with the official Plex container.

Quote

October 3, 20241 yr

ADDITION: Disabling magic dns resolved the issue.

Hello, I have been using this awesome binhex - SABnzbdVPN container on my Unraid server for a long time without any errors.
Today I successfully installed and set up the Tailscale plugin, which allows me to access my Unraid server and the individual Docker containers remotely.
Since then, however, my SABnzbdVPN container no longer (re)starts, but remains in the logs here:

2024-10-03 22:22:15.945030 [info] Host is running unRAID
2024-10-03 22:22:15.973547 [info] System information: Linux 33db1ddc1cd9 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux
2024-10-03 22:22:16.001699 [info] Image tags: INT_RELEASE_TAG=2024073001,IMAGE_RELEASE_TAG=4.3.3-1-01
2024-10-03 22:22:16.033218 [info] PUID defined as '99'
2024-10-03 22:22:16.069592 [info] PGID defined as '100'
2024-10-03 22:22:16.144328 [info] UMASK defined as '000'
2024-10-03 22:22:16.175167 [info] Permissions already set for '/config'
2024-10-03 22:22:16.207825 [info] Deleting files in /tmp (non recursive)...
2024-10-03 22:22:16.244691 [info] VPN_ENABLED defined as 'yes'
2024-10-03 22:22:16.277611 [info] VPN_CLIENT defined as 'wireguard'
2024-10-03 22:22:16.308856 [info] VPN_PROV defined as 'airvpn'
2024-10-03 22:22:16.352572 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2024-10-03 22:22:16.397093 [info] VPN_REMOTE_SERVER defined as 'gb3.vpn.airdns.org'
2024-10-03 22:22:16.430539 [info] VPN_REMOTE_PORT defined as '1637'
2024-10-03 22:22:16.458991 [info] VPN_DEVICE_TYPE defined as 'wg0'
2024-10-03 22:22:16.487447 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2024-10-03 22:22:16.519622 [info] USERSPACE_WIREGUARD not defined (via -e USERSPACE_WIREGUARD), defaulting to 'no'
2024-10-03 22:22:16.571073 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'

If I deactivate the tailscale plugin in the settings, I can start the SABnzbdVPN container again without errors.
I can then reactivate the Tailscale plugin and still access the SABnzbdVPN container (even remotely from the Tailscale network). Only the next time I try to restart, the SABnzbdVPN container does not start up again due to the activated Tailnet plugin, but stops at the beginning of the start.

Does anyone know a way to solve this error?

Edited October 6, 20241 yr by raiderbert

Quote

October 4, 20241 yr

Hey guys,

i have problem. I want to use binhex-sabnzbdvpn with his built in VPN. The network type is bridge and I'm using nordvpn. I filled in the right credentials, uploaded the right udp.opvpn (checked it more than 5 times), STRICT_PORT_FORWARD is set to "NO" and ENABLE_PRIVOXY is set to "YES". When I'm activating the VPN, i have no access to the WebUI, when I'm deactivating it, I have access. Can someone telling me what I'm doing wrong? Yesterday it worked for a short time but now it stopped working out of a sudden.

2024-10-04 06:31:49 VERIFY KU OK
2024-10-04 06:31:49 Validating certificate extended key usage
2024-10-04 06:31:49 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-10-04 06:31:49 VERIFY EKU OK
2024-10-04 06:31:49 VERIFY X509NAME OK: CN=ch223.nordvpn.com
2024-10-04 06:31:49 VERIFY OK: depth=0, CN=ch223.nordvpn.com

2024-10-04 06:31:49,869 DEBG 'start-script' stdout output:
2024-10-04 06:31:49 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519
2024-10-04 06:31:49 [ch223.nordvpn.com] Peer Connection Initiated with [AF_INET]185.156.175.123:1194
2024-10-04 06:31:49 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1

2024-10-04 06:31:49,869 DEBG 'start-script' stdout output:
2024-10-04 06:31:49 TLS: tls_multi_process: initial untrusted session promoted to trusted

2024-10-04 06:31:50,958 DEBG 'start-script' stdout output:
2024-10-04 06:31:50 SENT CONTROL [ch223.nordvpn.com]: 'PUSH_REQUEST' (status=1)
2024-10-04 06:31:50 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,explicit-exit-notify,comp-lzo no,route-gateway 10.100.0.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.100.0.2 255.255.255.0,peer-id 2,cipher AES-256-GCM'

2024-10-04 06:31:50,959 DEBG 'start-script' stdout output:
2024-10-04 06:31:50 OPTIONS IMPORT: --ifconfig/up options modified
2024-10-04 06:31:50 OPTIONS IMPORT: route options modified
2024-10-04 06:31:50 OPTIONS IMPORT: route-related options modified
2024-10-04 06:31:50 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2024-10-04 06:31:50 net_route_v4_best_gw query: dst 0.0.0.0
2024-10-04 06:31:50 net_route_v4_best_gw result: via 172.17.0.1 dev eth0
2024-10-04 06:31:50 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02
2024-10-04 06:31:50 TUN/TAP device tun0 opened
2024-10-04 06:31:50 net_iface_mtu_set: mtu 1500 for tun0
2024-10-04 06:31:50 net_iface_up: set tun0 up
2024-10-04 06:31:50 net_addr_v4_add: 10.100.0.2/24 dev tun0

2024-10-04 06:31:50,960 DEBG 'start-script' stdout output:
2024-10-04 06:31:50 /root/openvpnup.sh tun0 1500 0 10.100.0.2 255.255.255.0 init

2024-10-04 06:31:50,967 DEBG 'start-script' stdout output:
2024-10-04 06:31:50 net_route_v4_add: 185.156.175.123/32 via 172.17.0.1 dev [NULL] table 0 metric -1

2024-10-04 06:31:50,968 DEBG 'start-script' stdout output:
2024-10-04 06:31:50 net_route_v4_add: 0.0.0.0/1 via 10.100.0.1 dev [NULL] table 0 metric -1
2024-10-04 06:31:50 net_route_v4_add: 128.0.0.0/1 via 10.100.0.1 dev [NULL] table 0 metric -1
2024-10-04 06:31:50 Initialization Sequence Completed
2024-10-04 06:31:50 Data Channel: cipher 'AES-256-GCM', peer-id: 2, compression: 'stub'
2024-10-04 06:31:50 Timers: ping 60, ping-restart 180
2024-10-04 06:31:50 Protocol options: explicit-exit-notify 1

2024-10-04 06:31:50,974 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2024-10-04 06:31:51,998 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.100.0.2'

2024-10-04 06:31:51,999 DEBG 'start-script' stdout output:
[debug] Valid gateway IP address from tunnel acquired ''
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-04 06:31:52,008 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-04 06:31:52,045 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.185.132'

2024-10-04 06:31:52,046 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-10-04 06:31:52,048 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '192.0.0.88'

2024-10-04 06:31:52,211 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 194.15.111.220

2024-10-04 06:31:52,211 DEBG 'start-script' stdout output:
[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

2024-10-04 06:31:52,252 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2024-10-04 06:31:52,254 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2024-10-04 06:31:52,256 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2024-10-04 06:31:52,257 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2024-10-04 06:31:52,257 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2024-10-04 06:31:52,649 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process started
[info] Waiting for SABnzbd process to start listening on port 8080...

2024-10-04 06:31:52,868 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080

2024-10-04 06:31:52,869 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2024-10-04 06:31:53,878 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2024-10-04 06:31:53,886 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2024-10-04 06:31:53,886 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.100.0.2

2024-10-04 06:32:23,894 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-04 06:32:23,936 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '192.0.0.88'

2024-10-04 06:32:23,937 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2024-10-04 06:32:23,945 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2024-10-04 06:32:23,955 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.100.0.2

Quote

October 6, 20241 yr

Been pulling my hair out trying to gain access to sabnzbdvpn container on my remote server. System is working but not web gui. After hours tonight I at least have a lead. I connect via tailscale with the tailscale plugin. On a hunch I tried installing the firefox browser container on the remote server and it has no problem accessing the web gui. This has me thinking it is due to the privoxy vpn and me accessing via a vpn. My brother's server is doing the same thing. Anyone have any suggestions on a direction I can take to straighten it out? I use NZB360 Android app and it can't access it either. Seems only devices on the same local network can. One thought I had was to just use swag's integrated tailscale and just proxy it through that. I'll have to test that tomorrow though.

Quote

October 6, 20241 yr

Author

11 hours ago, falkfyrebeard said:

Been pulling my hair out trying to gain access to sabnzbdvpn container on my remote server. System is working but not web gui. After hours tonight I at least have a lead. I connect via tailscale with the tailscale plugin. On a hunch I tried installing the firefox browser container on the remote server and it has no problem accessing the web gui. This has me thinking it is due to the privoxy vpn and me accessing via a vpn. My brother's server is doing the same thing. Anyone have any suggestions on a direction I can take to straighten it out? I use NZB360 Android app and it can't access it either. Seems only devices on the same local network can. One thought I had was to just use swag's integrated tailscale and just proxy it through that. I'll have to test that tomorrow though.

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

Quote

October 6, 20241 yr

1 hour ago, binhex said:

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

Hey, thanks for the reply. I decided to go through all of the questions and just learn a bit more. After adding my tailscale ips/32 to lan network I was at least getting a denied error. I was so focused on trying to just get in I had overlooked external access. I used firefox on the remote server and found remote access was disabled. Set it to full access and everything popped up. It's all good now. Thanks for the direction.

Edited October 6, 20241 yr by falkfyrebeard
realized I did have to have LAN networks set to have my tailscale IPs/32 for it to allow connection even with external access turned on

Quote

October 12, 20241 yr

I'm having issues with this container starting properly. It seems like the VPN is up but DNS resolution fails according to logs:

text  error  warn  system  array  login  

2024-10-12 01:17:37,488 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2024-10-12 01:17:37,497 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
[debug] Running WireGuard kernel implementation...

2024-10-12 01:17:37,506 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2024-10-12 01:17:37,520 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2024-10-12 01:17:37,523 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2024-10-12 01:17:37,525 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

2024-10-12 01:17:37,533 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2024-10-12 01:17:37,538 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2024-10-12 01:17:37,562 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2024-10-12 01:17:37,567 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2024-10-12 01:17:37,569 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2024-10-12 01:17:37,572 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2024-10-12 01:17:37,576 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2024-10-12 01:17:37,579 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2024-10-12 01:17:37,582 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2024-10-12 01:17:37,588 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2024-10-12 01:17:38,599 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.2.0.2'

2024-10-12 01:17:38,600 DEBG 'start-script' stdout output:
[debug] Valid gateway IP address from tunnel acquired ''
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-12 01:17:38,685 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-12 01:18:23,653 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

2024-10-12 01:18:23,740 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

2024-10-12 01:19:13,707 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 10 retries left

2024-10-12 01:19:13,790 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 10 retries left

2024-10-12 01:20:03,752 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 9 retries left

2024-10-12 01:20:03,844 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 9 retries left

[...]
<this continue for until 1 retries and then loops again>

The configuration is a protonVPN with wireguard setup like:

docker run
  -d
  --name='binhex-sabnzbdvpn'
  --net='bridge'
  --cpuset-cpus='0,1,4,5'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Vault"
  -e HOST_CONTAINERNAME="binhex-sabnzbdvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='reducted'
  -e 'VPN_PASS'='reducted'
  -e 'VPN_PROV'='custom'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'LAN_NETWORK'='10.120.10.0/24,192.168.10.0/24,192.168.20.0/24'
  -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4'
  -e 'ADDITIONAL_PORTS'='8081'
  -e 'DEBUG'='true'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'VPN_CLIENT'='wireguard'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png'
  -p '8080:8080/tcp'
  -p '8090:8090/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/volatile/downloads':'/data':'rw'
  -v '/mnt/user/appdata/binhex-sabnzbdvpn':'/config':'rw'
  --memory=4G
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-sabnzbdvpn:latest'

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
48eedf44b7c17b1da6ce21163e144cf1c92f994ce804e3b188edc4806c79d793

The command finished successfully!

Any idea where to look for debug / fixing this ?

Cheers,

Quote

October 12, 20241 yr

Any ideas why this image would be taking nearly 3GB of Docker space? More than other data hungry containers such as Immich.

All paths look to be configured correctly.

I ask as I am currently using quite a lot of my allocated docker image and when updates are applied I get warning notifications:

devid 1 size 30.00GiB used 27.64GiB path /dev/loop2

Quote

October 13, 20241 yr

On 10/12/2024 at 1:26 AM, artafinde said:

I'm having issues with this container starting properly. It seems like the VPN is up but DNS resolution fails according to logs:

text  error  warn  system  array  login  

2024-10-12 01:17:37,488 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2024-10-12 01:17:37,497 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
[debug] Running WireGuard kernel implementation...

2024-10-12 01:17:37,506 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2024-10-12 01:17:37,520 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2024-10-12 01:17:37,523 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2024-10-12 01:17:37,525 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

2024-10-12 01:17:37,533 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2024-10-12 01:17:37,538 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2024-10-12 01:17:37,562 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2024-10-12 01:17:37,567 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2024-10-12 01:17:37,569 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2024-10-12 01:17:37,572 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2024-10-12 01:17:37,576 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2024-10-12 01:17:37,579 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2024-10-12 01:17:37,582 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2024-10-12 01:17:37,588 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2024-10-12 01:17:38,599 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.2.0.2'

2024-10-12 01:17:38,600 DEBG 'start-script' stdout output:
[debug] Valid gateway IP address from tunnel acquired ''
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-12 01:17:38,685 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2024-10-12 01:18:23,653 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

2024-10-12 01:18:23,740 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

2024-10-12 01:19:13,707 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 10 retries left

2024-10-12 01:19:13,790 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 10 retries left

2024-10-12 01:20:03,752 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 9 retries left

2024-10-12 01:20:03,844 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 9 retries left

[...]
<this continue for until 1 retries and then loops again>

The configuration is a protonVPN with wireguard setup like:

docker run
  -d
  --name='binhex-sabnzbdvpn'
  --net='bridge'
  --cpuset-cpus='0,1,4,5'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Vault"
  -e HOST_CONTAINERNAME="binhex-sabnzbdvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='reducted'
  -e 'VPN_PASS'='reducted'
  -e 'VPN_PROV'='custom'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'LAN_NETWORK'='10.120.10.0/24,192.168.10.0/24,192.168.20.0/24'
  -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4'
  -e 'ADDITIONAL_PORTS'='8081'
  -e 'DEBUG'='true'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'VPN_CLIENT'='wireguard'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png'
  -p '8080:8080/tcp'
  -p '8090:8090/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/volatile/downloads':'/data':'rw'
  -v '/mnt/user/appdata/binhex-sabnzbdvpn':'/config':'rw'
  --memory=4G
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-sabnzbdvpn:latest'

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
48eedf44b7c17b1da6ce21163e144cf1c92f994ce804e3b188edc4806c79d793

The command finished successfully!

Any idea where to look for debug / fixing this ?

Cheers,

OK fixed - was issue with the wireguard certificate, had expired!

sorry for the noise

Quote

October 14, 20241 yr

On 3/22/2019 at 12:24 PM, Dutch Vertigo said:

Do's this container support ExpressVPN ?

On 3/23/2019 at 3:49 AM, binhex said:

As long as that VPN provider supports OpenVPN clients then yes.

Sent from my EML-L29 using Tapatalk

Hi - Did you figure out how to use expressvpn with this docker? Moving from PIA to ExpressVPN, the docker starts and seems to get a vpn ip but cannot connect to the gui.

Quote

October 22, 20241 yr

Hi Folks

Could one of you legends tell me how to fix this error in Radarr?

I can't get my head around these paths and I have been going around in circles for a while now and I can't figure out which one that I am supposed to change and to what.

I though it was as per the Trash guide but clearly I am doing something wrong. Here is what i have in SABnzdb:

image.png.28c40b8c3852e0f58d7c5410bd21f39e.png

Thanks in advance...

Quote

October 24, 20241 yr

Hi there, I have recently updated to the latest build available today.

Previously I had STRICT_PORT_FORWARD set to Yes and this has worked without fault for a long time.

Today when I try connecting to any endpoint I get a message to advise port forwarding is not available:

I have contacted my VPN provider and they advise none of their servers support port forwarding.

What are the implications of not having strict port forwarding enabled for this container when downloading and routing other containers through binhex-sabnzbvpn?

Best

GP

Quote

October 24, 20241 yr

Author

1 hour ago, GHOSTPOINT said:

Hi there, I have recently updated to the latest build available today.

Previously I had STRICT_PORT_FORWARD set to Yes and this has worked without fault for a long time.

Today when I try connecting to any endpoint I get a message to advise port forwarding is not available:

I have contacted my VPN provider and they advise none of their servers support port forwarding.

What are the implications of not having strict port forwarding enabled for this container when downloading and routing other containers through binhex-sabnzbvpn?

Best

GP

if your vpn provider is not pia or protonvpn (i assume not due to the statement 'my VPN provider and they advise none of their servers support port forwarding') then STRICT_PORT_FORWARD does nothing.

Quote

October 24, 20241 yr

19 minutes ago, binhex said:

if your vpn provider is not pia or protonvpn (i assume not due to the statement 'my VPN provider and they advise none of their servers support port forwarding') then STRICT_PORT_FORWARD does nothing.

Okay thanks - well certainly seems that way. Not sure why the strict port forwarding option was working okay previously. Unless it was just being ignored by the openvpn agent ?

Quote

October 24, 20241 yr

Author

1 hour ago, GHOSTPOINT said:

Okay thanks - well certainly seems that way. Not sure why the strict port forwarding option was working okay previously. Unless it was just being ignored by the openvpn agent ?

As mentioned above, if your vpn provider is NOT PIA or ProtonVPN then STRICT_PORT_FORWARD is completely ignored, this is for openvpn and wireguard, this has always been the case.

Quote

1

November 5, 20241 yr

I have this exact same problem using wireguard.

Quote

November 5, 20241 yr

Author

17 hours ago, Danoman said:

I have this exact same problem using wireguard.

Intermittent issues on PIA end most probably, keep trying.

Quote

November 7, 20241 yr

On 9/5/2024 at 10:40 AM, MrLinford said:

I restarted the container today and the PIA Wireguard is not working, the logs show:

OpenVPN works fine still.

Same here, still having Wireguard problems. Open vpn is fine.

Quote

November 15, 20241 yr

Hey everyone,

I've recently run into an issue where SABnzbd is unable to download files. The error I'm seeing is:

Cannot connect to server news.usenetserver.com [Server name does not resolve]

I first thought it might be related to my VPN setup (I'm using PrivadoVPN), so I tried switching to a different VPN server and cert, but that didn’t resolve the issue.

Here’s what I’ve tried so far:

Switched VPN servers and certificates: No change.
Checked DNS functionality: The logs indicate that DNS is working correctly. For example, I see:
```
 [debug] DNS operational, we can resolve name 'www.google.com' to address '198.18.0.17'
```
Tested general connectivity: I can access the web interface without any problems through a browser, so it seems like the application and routing itself is functional.

Given the above, it seems like SABnzbd can't resolve the Usenet server's domain, despite DNS working for other services on my system.

I'm at a bit of a loss for what might be causing this. Does anyone have any suggestions for further troubleshooting or know what might be causing the container to fail DNS resolution specifically for the Usenet server?

Thanks in advance for any help you can provide!

Quote

November 20, 20241 yr

On 11/14/2024 at 7:51 PM, Indmenity83 said:
Hey everyone,

I've recently run into an issue where SABnzbd is unable to download files. The error I'm seeing is:
Cannot connect to server news.usenetserver.com [Server name does not resolve]
I first thought it might be related to my VPN setup (I'm using PrivadoVPN), so I tried switching to a different VPN server and cert, but that didn’t resolve the issue.

Here’s what I’ve tried so far:
Switched VPN servers and certificates: No change.
Checked DNS functionality: The logs indicate that DNS is working correctly. For example, I see:
 [debug] DNS operational, we can resolve name 'www.google.com' to address '198.18.0.17'
Tested general connectivity: I can access the web interface without any problems through a browser, so it seems like the application and routing itself is functional.
Given the above, it seems like SABnzbd can't resolve the Usenet server's domain, despite DNS working for other services on my system.

I'm at a bit of a loss for what might be causing this. Does anyone have any suggestions for further troubleshooting or know what might be causing the container to fail DNS resolution specifically for the Usenet server?

Thanks in advance for any help you can provide!

I got this issue and discovered my VPN subscription had run out.

Quote

November 20, 20241 yr

On 8/5/2023 at 4:27 AM, binhex said:

See Q20:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

I'm using ProtonVPN and they provide a nice way to download an entire country file (us.protonvpn.udp.ovpn) that contains the multi remote lines which solves my issue of not hitting a dead endpoint, but the speeds are really crappy on my gigabit ISP connection. I've tried tuning every single knob and can only get 35 MB/s average. Doesn't matter which usenet provider I use or how many connections, it never goes above 42 MB/s on a 10GB test download in sabnzbdvpn.

I'd like to try using Wireguard, but I don't want to go back to being locked to a single endpoint for the reasons stated. Do you know if you can add multiple remote lines/endpoints in a single wg0.conf file that has the same behavior as openvpn that checks them in a round robin fashion?

Quote

[Support] binhex - SABnzbdVPN

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

binhex

binhex

binhex

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

binhex

binhex

binhex

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)