[Support] binhex - SABnzbdVPN

[Slin]

I have an SSD as a cache drive.

What path do I need to enter here?

[betaman]

36 minutes ago, Slin said:

I have an SSD as a cache drive.

What path do I need to enter here?

The root path to your “downloads” folder (eg /mnt/user/appdata/downloads/). If you match this in all of your dockers your life will be a lot easier. Like I said, binhex uses /data in all of his dockers.

Edited January 16 by betaman

[Slin]

Sin SabNZB I have these settings....

 

Radarr says this......

[betaman]

27 minutes ago, Slin said:

Sin SabNZB I have these settings....

 

Radarr says this......

That’s why I told you that you need a remote path setting in the download clients settings page.

[K1LLA_KING_KING]

Why cant I connect sab to my LAN?

It seems there is a network problem. All was fine before



1 error showing:

 

Edited January 17 by K1LLA_KING_KING

[binhex]

53 minutes ago, K1LLA_KING_KING said:

It seems there is a network problem. All was fine before

firstly you cannot ping an ip address specifying the port.

And as you highlighted, the LAN_NETWORK is incorrectly configured, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[Slin]

21 hours ago, betaman said:

That’s why I told you that you need a remote path setting in the download clients settings page.

Thanks, so based on the share media and the two folders, tv and film in it what do the paths and remote paths need to be, I can't work it out.

[betaman]

15 minutes ago, Slin said:

Thanks, so based on the share media and the two folders, tv and film in it what do the paths and remote paths need to be, I can't work it out.

Something like this In Sonarr (/data/movies in Radar):

 

[K1LLA_KING_KING]

17 hours ago, binhex said:

firstly you cannot ping an ip address specifying the port.

And as you highlighted, the LAN_NETWORK is incorrectly configured, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thank you very much thats worked for me. But also very strange. As I had not changed this setting, and was working fine for months prior. 

[its_me_michael2000]

Hi all. My Sabnzbd container has been working great up until recently. I updated it and it gets stuck at the image attached and goes no further. Any help would be greatly appreciated

[JonathanM]

16 minutes ago, its_me_michael2000 said:

Hi all. My Sabnzbd container has been working great up until recently. I updated it and it gets stuck at the image attached and goes no further. Any help would be greatly appreciated

Try recreating the .ovpn file from your expressvpn account.

[dmoney517]

For awhile now I have not been able to consistently load the SabNZB GUI on my Unraid.  It still starts, and downloads and works.  But getting the UI to load is very inconsistent.  I would say it works 1 out of 10 tries.  I barely every need to look at it, so not a major hindrance.  I noticed today when I tried to launch it, I got this error in my Server log - 

TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters.

Nothing on my server is exposed to the internet.

It used to work flawlessly, so I am guessing a docker update did something that I never really noticed.  As I said, I dont try to access it often.  Appreciate any guidance.

 

[crushed-statute1022]

Hey everyone,
I hope I get some help with my issues here.
I created the arch-sabnzbvpn container via docker and portainer in an LXC-Container (Ubuntu 22.04) on a Proxmox Host (8.1.4).

I used the following code:

 

docker run -d \
    --cap-add=NET_ADMIN \
	--device=/dev/net/tun \
    -p 8080:8080 \
    -p 8090:8090 \
    -p 8118:8118 \
    --name=SABnzbdVPN \
    -v /var/lib/docker/volumes/sabnzbdvpn/_data/data:/data \
    -v /var/lib/docker/volumes/sabnzbdvpn/_data/config:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_USER=xxxxxxx \
    -e VPN_PASS=xxxxxxx \
    -e VPN_PROV=pia \
    -e VPN_CLIENT=openvpn \
    -e VPN_OPTIONS= \
    -e STRICT_PORT_FORWARD=no \
    -e ENABLE_PRIVOXY=yes \
    -e ENABLE_STARTUP_SCRIPTS=no \
    -e LAN_NETWORK=172.16.0.0/12 \
    -e NAME_SERVERS=209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4 \
    -e VPN_INPUT_PORTS= \
    -e VPN_OUTPUT_PORTS= \
    -e DEBUG=false \
    -e UMASK=000 \
    -e PUID=99 \
    -e PGID=100 \
    binhex/arch-sabnzbdvpn

 

After that I followed some steps in the tutorial: https://pve.proxmox.com/wiki/OpenVPN_in_LXC

Now, when I start the container I got the following failures in the log:

 

2024-03-15 10:04:52,166 DEBG 'start-script' stderr output:

modprobe: FATAL: Module tun not found in directory /lib/modules/6.5.13-1-pve

2024-03-15 10:04:52,166 DEBG 'start-script' stdout output:

[warn] Unable to load tun kernel module using modprobe, trying insmod...

2024-03-15 10:04:52,168 DEBG 'start-script' stderr output:

insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2024-03-15 10:04:52,168 DEBG 'start-script' stdout output:

[warn] Unable to load tun kernel module, assuming its dynamically loaded

2024-03-15 10:04:52,178 DEBG 'start-script' stdout output:

[info] Attempting to load iptable_mangle module...

2024-03-15 10:04:52,180 DEBG 'start-script' stderr output:

modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/6.5.13-1-pve

2024-03-15 10:04:52,181 DEBG 'start-script' stdout output:

[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2024-03-15 10:04:52,182 DEBG 'start-script' stderr output:

insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

 

First I ignored the issues and tried to open up the WebGUI for SABNZB, but the site is not loading.

I hope you can help me with that?

[binhex]

59 minutes ago, crushed-statute1022 said:

insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

you need to ensure iptable_mangle is loaded and available on your host.

[binhex]

On 3/14/2024 at 12:55 AM, dmoney517 said:

But getting the UI to load is very inconsistent.  I would say it works 1 out of 10 tries. 

the lan_network is wrong, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[crushed-statute1022]

On 3/15/2024 at 12:16 PM, binhex said:

you need to ensure iptable_mangle is loaded and available on your host.

Ok, i got this fixed, with installing iptable_mangle with apt install

 

But I got a strange issue with the TUN/TAB Device:
 

First, the log said this:

2024-03-20 15:29:41,485 DEBG 'start-script' stdout output:
2024-03-20 15:29:41 TUN/TAP device tun0 opened
2024-03-20 15:29:41 net_iface_mtu_set: mtu 1500 for tun0

Later then:

2024-03-20 15:29:41,485 DEBG 'start-script' stdout output:
2024-03-20 15:29:41 net_iface_up: set tun0 up
2024-03-20 15:29:41 net_addr_v4_add: 10.xxx.xxx.xxx/xx dev tun0
2024-03-20 15:29:41 /root/openvpnup.sh tun0 1500 0 10.xxx.xxx.xxx 255.xxx.xxx.0 init

 

So I think the tunnel is open and working. But when I try to connect via Proxy-Settings activated in Firefox local-IP_of_Portainer:8118 the tunnel is not up. It shows my normal public IP.

Where and how can I troubleshoot this problem?

[Helmonder]

Question:

 

I am succesfully using binhex-Sabnzbdvpn. SAB works fine.

 

I use wireguard for VPN.

 

There is however one issue.

 

I am using MEDUSA to search for shows, and host my own SPOTWEB server locally to index newsservers.

 

MEDUSA tells spotweb to search and when something is found then shoots a link to sabnzbd with the nzb.  Sabnzbd then needs to download this from my local spotweb server... 

 

This fails because sabnzbd is ofcourse using the tunnel and from the internet my local spotweb server is not reachable...

 

Is there a way to have a specific ip address bypass the tunnel and keep that traffic local ?

 

There is the LAN_NETWORK setting.. I could imagine addresses in that space bypassing the VPN ?

 

If I look on console with in the docker I see there are two network interfaces:

 

wg0 is the wireguard interface

eth0 is the regular docker interface

 

What would need to be done is some kind of routing rule that makes that the address space as configured in the LAN_NETWORK setting is routed thru eth0 and the rest thru wg0.

 

I tried something dirty and changed the AllowedIP's directive in the wireguard config to only show the newssergers I target, but that does not seem to work (also: they change often so that is a bad route)..

 

I need an exclusion instead of an inclusion..

Edited March 23 by Helmonder

[internetfriend]

On 10/9/2023 at 1:44 AM, SaltyKram said:

supervisord.log 38.67 kB · 1 download

 

Hi Binhex, 

 

I'm having an issue with warnings of timeout connections using ProtonVPN with Sabnzbvpn. It looks like the below: 

 

WARNING 4 minutes ago Failed to connect: [Errno 9] Bad file descriptor news.eweka.nl:563 (81.171.92.219)
WARNING 4 minutes ago Failed to connect: [Errno 9] Bad file descriptor news.eweka.nl:563 (81.171.92.219)
WARNING 4 minutes ago Failed to connect: timed out news.eweka.nl:563 (81.171.92.219)

 

Although the above is Eweka, it appears to happen with connections to all of my other backup providers as well - it seems to depend on if it is actively being used/connected to. Sabnzb and my downloads appear to continue downloading even after this error shows up. 

 

Prior to using ProtonVPN, I have used Mullvad in this same container flawlessly. I am currently using ProtonVPN in your qBittorrent container also without issue. 

 

I have switched ports on the providers from 443 to 563, switched from Wireguard back to openvpn, added 8.8.8.8 to the name server - all result in the same error. The only thing that fixes these warnings is switching back to Mullvad, so it seems to be specific to ProtonVPN. 

 

My redacted debug log is attached. Any ideas on how I can make ProtonVPN work?

 

Thanks!

 

 

Its weird, I just started encountering this too when switching from Mullvad to Proton. Eliminating the VPN removes the issue, and using Mullvad doesnt cause it, but something proton is doing just messes with the whole thing. The download usually still completes, so the errors are kind of harmless albeit annoying but even more weird since you'd expect some failures. I tried futzing with the nameservers and the timeout periods within SAB too, because its not a Binhex-sabnzbdvpn container error, its definitely protonVPN, but nothing seems to sort it. Its also not consistent, some downloads go through without a hitch and some do it, but the ones that do it reliably do it. 

If anyone else ran into this and worked out a solve on their side, I'd love to know!
Thank you in advance. 🙇‍♂️

[mgutt]

@binhex

Could you please add this path to the default config to reduce wear on the SSD:

 

 

Sab is permanently writing to these files:

 

root@thoth:~# find /tmp/sabnzbd/
/tmp/sabnzbd/
/tmp/sabnzbd/tmp
/tmp/sabnzbd/tmp/vpngatewayip
/tmp/sabnzbd/tmp/vpnip
/tmp/sabnzbd/tmp/getiptables
/tmp/sabnzbd/tmp/watchdog-script-stderr---supervisor-jgbmg455.log
/tmp/sabnzbd/tmp/watchdog-script-stdout---supervisor-dva2j1vt.log
/tmp/sabnzbd/tmp/start-script-stderr---supervisor-5i8155s4.log
/tmp/sabnzbd/tmp/start-script-stdout---supervisor-whva770j.log
/tmp/sabnzbd/tmp/endpoints

 

And by using /tmp this are written to unRAID's RAM disk.