[Support] binhex - SABnzbdVPN

[Bluetesteur]

3 hours ago, binhex said:

what is the value for NAME_SERVERS?

I tried without values, not working

Expected using the default ones provided by the container as show in log:

2023-06-23 15:49:19.225366 [warn] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to name servers defined in readme.md

 

 

EDIT:

Just tried with NAME_SERVERS=8.8.8.8,1.1.1.1, it seems to go forward better..

 

But I don't understand why it was not working without this line NAME_SERVERS in docker-compose, this line was never in my conf, and without it, container should use the ones provided by you and should works , no ?

 

 

 

 

Edited June 23, 2023 by Bluetesteur
add more tests

[jenga201]

I've upgraded to unraid 6.12.1 and am having trouble starting up the sabnzbd container again.

 

These are the logs; sabnzbd.txt

It seems the app attempts to start, then restart, then the UI isn't accessible.

 

I had a large queue of files during the upgrade & restart.  The container should have shut down cleanly.

Could the program be choking on hashing a large queue on start?

 

Are there any ways to clear the queue from command line or do some other diagnostic?

 

Thanks for any replies!

Edited June 29, 2023 by jenga201

[Timberwolf]

It's a NordVPN thing, possibly. They recently changed something in 'unattended logins' to require an App account. You need to go to your Nord dash, under account, 'set manually' and copy the manual installation credentials to your Docker settings. See also:

 

 

[binhex]

On 6/23/2023 at 4:48 PM, Bluetesteur said:

I tried without values, not working

Expected using the default ones provided by the container as show in log:

2023-06-23 15:49:19.225366 [warn] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to name servers defined in readme.md

 

 

EDIT:

Just tried with NAME_SERVERS=8.8.8.8,1.1.1.1, it seems to go forward better..

 

But I don't understand why it was not working without this line NAME_SERVERS in docker-compose, this line was never in my conf, and without it, container should use the ones provided by you and should works , no ?

 

 

 

 

i also dont understand why, i have taken a look at my code and it does indeed set NAME_SERVERS to the default list, so i can only assume that the first name server in the list was down, or that your home network is actively blocking name servers from particular ip ranges.

[Bluetesteur]

5 hours ago, binhex said:

i also dont understand why, i have taken a look at my code and it does indeed set NAME_SERVERS to the default list, so i can only assume that the first name server in the list was down, or that your home network is actively blocking name servers from particular ip ranges.

Whatever binhex, thanks a lot for your time, all seems to work fine now with NAME_SERVERS=8.8.8.8,1.1.1.1

[jenga201]

10 hours ago, Timberwolf said:

It's a NordVPN thing, possibly. They recently changed something in 'unattended logins' to require an App account. You need to go to your Nord dash, under account, 'set manually' and copy the manual installation credentials to your Docker settings. See also:

 

 

 

Thanks for some info.

I'm using PIA and it doesn't seem they've updated to use any token system.

 

I re-made the docker container and found there have been a bunch of parameter updates.

Not sure why this happened, but keeping my configurations & remaking the unraid docker container with the same info seemed to do the trick.

[clevoir]

I am running AirVPN and have loaded the OVPN and certs into config / sabnzbd-vpn/ openvpn

 

The Sabnzbd-vpn log file shows that a VPN connection has been set up, I can verify this by going to AirVPN website.

 

However Public IPv4 address reported can't connect and I am unable download using Sonarr / Radaar or Lidarr?

[clevoir]

I am tried removing the line as noted in A22

 

A VPN connection is made but Sonaar et all now can't searth for any files?

 

This is the Sabnzb log

 

2023-07-02 08:51:17,624 DEBG 'start-script' stdout output:
2023-07-02 08:51:17 net_route_v4_add: 0.0.0.0/1 via 10.29.154.1 dev [NULL] table 0 metric -1
2023-07-02 08:51:17 net_route_v4_add: 128.0.0.0/1 via 10.29.154.1 dev [NULL] table 0 metric -1

2023-07-02 08:51:17,625 DEBG 'start-script' stdout output:
2023-07-02 08:51:17 Initialization Sequence Completed
2023-07-02 08:51:17 Data Channel: cipher 'CHACHA20-POLY1305', peer-id: 4, compression: 'stub'
2023-07-02 08:51:17 Timers: ping 10, ping-restart 60
2023-07-02 08:51:17 Protocol options: explicit-exit-notify 5

2023-07-02 08:51:33,833 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2023-07-02 08:51:33,844 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2023-07-02 08:51:33,844 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2023-07-02 08:51:35,644 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process started
[info] Waiting for SABnzbd process to start listening on port 8080...

2023-07-02 08:51:35,657 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080

2023-07-02 08:51:35,660 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2023-07-02 08:51:36,675 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2023-07-02 08:51:36,686 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2023-07-02 08:51:38,742 DEBG 'start-script' stdout output:
[info] Application does not require external IP address, skipping external IP address detection

2023-07-02 08:51:38,763 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

[jbrenner3]

I have recently been unable to connect to the web gui with vpn enabled.  the logs just continually flash this error.

 

OpenSSL: error:0A00018E:SSL routines::ca md too weak

[lukeoslavia]

I am trying to run this on docker desktop. With openvpn I can connect fine, but when I try to use wireguard I get this same series of messages repeating.

Spoiler

2023-07-07 10:44:28 2023-07-07 14:44:28,512 DEBG 'start-script' stdout output:
2023-07-07 10:44:28 [info] Attempting to bring WireGuard interface 'up'...
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,535 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 Warning: `/config/wireguard/wg0.conf' is world accessible
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,554 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip link add wg0 type wireguard
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,557 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] wg setconf wg0 /dev/fd/63
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,655 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip -4 address add 10.12.178.109 dev wg0
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,667 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip link set mtu 1420 up dev wg0
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,742 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] wg set wg0 fwmark 51820
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,744 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,748 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip -4 rule add not fwmark 51820 table 51820
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,753 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip -4 rule add table main suppress_prefixlength 0
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,760 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,762 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] iptables-restore -n
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,816 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 Warning: Extension CONNMARK revision 0 not supported, missing kernel module?
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,816 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 Warning: Extension CONNMARK is not supported, missing kernel module?
2023-07-07 10:44:28 iptables-restore: line 7 failed
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,828 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip -4 rule delete table 51820
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,836 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip -4 rule delete table main suppress_prefixlength 0
2023-07-07 10:44:28 
2023-07-07 10:44:28 2023-07-07 14:44:28,853 DEBG 'start-script' stderr output:
2023-07-07 10:44:28 [#] ip link delete dev wg0
2023-07-07 10:44:28 
2023-07-07 10:44:29 2023-07-07 14:44:29,256 DEBG 'start-script' stdout output:
2023-07-07 10:44:29 [warn] WireGuard interface failed to come 'up', exit code is '1'

 

I have tried the default config that gets generated and I made my own with hsand/pia-wg generator but I get the same result either way. Is there something I am not configuring properly?

Edited July 7, 2023 by lukeoslavia
added spoiler to logs

[jbrenner3]

22 hours ago, jbrenner3 said:

I have recently been unable to connect to the web gui with vpn enabled.  the logs just continually flash this error.

 

OpenSSL: error:0A00018E:SSL routines::ca md too weak

solved. add [tls-cipher "DEFAULT:@SECLEVEL=0"] to OVPN file

Edited July 7, 2023 by jbrenner3

[binhex]

solved. add [tls-cipher "DEFAULT:@SECLEVEL=0"] to OVPN file

Just to say, that is a workaround, openvpn is telling you your VPN provider is using weak security, by setting that option you are in effect saying you don't care.

Sent from my 22021211RG using Tapatalk

[ConnerVT]

I could put this in any of a half dozen threads, but this is the most recent of the @binhex containers I've installed.  I have been using NBZGET running through DelugeVPN for the past few years.  But with NZBGET development on hold (was hoping the -ng group would pull something together) it was time to move on to SABnzb.

 

Again, you did not let me down.  I first loaded the non-vpn version and configured one of my arr containers to use it.  Worked smooth as silk.  After a few days testing (my boss expects me to work, dammit!) I switched to the SABnzbVPN container and set up for PIA.  Again, totally painless.  Today, I moved the rest of the arr containers to use SABnzbVPN and shut down DelugeVPN and NZBget (I haven't used the torrent part of the container in well over a year).  A Docker cleanup I've been planning to do for too long, and one of the few times everything just worked as it should.

 

Enjoy a beer, and some pizza, as a token of my appreciation.  My thanks to you, for all you provide to the Unraid community.

[binhex]

9 hours ago, ConnerVT said:

I could put this in any of a half dozen threads, but this is the most recent of the @binhex containers I've installed.  I have been using NBZGET running through DelugeVPN for the past few years.  But with NZBGET development on hold (was hoping the -ng group would pull something together) it was time to move on to SABnzb.

 

Again, you did not let me down.  I first loaded the non-vpn version and configured one of my arr containers to use it.  Worked smooth as silk.  After a few days testing (my boss expects me to work, dammit!) I switched to the SABnzbVPN container and set up for PIA.  Again, totally painless.  Today, I moved the rest of the arr containers to use SABnzbVPN and shut down DelugeVPN and NZBget (I haven't used the torrent part of the container in well over a year).  A Docker cleanup I've been planning to do for too long, and one of the few times everything just worked as it should.

 

Enjoy a beer, and some pizza, as a token of my appreciation.  My thanks to you, for all you provide to the Unraid community.

Thank you for the kind words and the donation, i am sad that nzbget has not continued as it was (and still is) a pretty solid application (albeit with the unpack issue), oh well im glad old faithful SABnzbd has kept going all these years 🙂

[Sweex]

Hi! 

 

I've been having some problems with PIA and Wireguard recently. Sab works fine with Openvpn, full speed (40MB/s), PIA client on macbook on the same network with Wireguard full speed, Deluge with PIA wireguard full speed. 

 

But if i change to Wireguard on Sab, my speed is 1MB/s max. Same endpoint on pia, NL. 

I've deleted the docker (and appdata folder) and reinstalled and configured it, same problem. 

 

What do you need from me and what more can i try?

 

Best regards

Sweex 

[Brian5542]

Hello

 

Same for me dont work with the VPN, disable the VPN ok enable VPN not ok.

 

[carlos067]

On 9/13/2021 at 5:45 PM, rnobarr said:

SABnzbd Config > General > SABnzbd Host is set to 0.0.0.0.  When I set my RADARR and SONARR (Settings > Download Clients) Host to my Unraid Server IP (10.0.1.20) I get an error that reads:

 

Test was aborted due to an error: Unable to connect to SABnzbd, HTTP request failed: [503:ServiceUnavailable] [GET] at [https://10.0.1.20:8080/api?mode=get_config&apikey=***API KEY***&output=json]

 

That was why I changed them to 0.0.0.0

 

I followed SpaceinvaderOne's videos on how to set up all 3.  But theyre from ~2017.  Wondering if an update may have changed something.  He even sets his RADARR/SONARR hosts to his Unraid IP.  Not sure why mine stopped working when I set them to 10.0.1.20

I know it's been a long time since you asked, but I had the same problem and I searched forever. For any future person running into the same issue here is the solution.

 

I read everything including the VPN faq. Turns out I just suck at reading comprehension. The answer was in the vpn faq (https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md) Q24 Note 1:

"1. Please keep in mind that when defining connections from an application to another application in the same VPN container network that you will need to set the host to 'localhost' and NOT the LAN IP address, this is because the applications are now bound to the same network and thus should communicate over 'localhost' and NOT the unRAID host IP address."  So literally set the host on all the apps on the VPN network to 'localhost' then you wont have to worry about changing ip addresses. 

[neardeaf]

On 7/31/2023 at 4:05 AM, Sweex said:

Hi! 

 

I've been having some problems with PIA and Wireguard recently. Sab works fine with Openvpn, full speed (40MB/s), PIA client on macbook on the same network with Wireguard full speed, Deluge with PIA wireguard full speed. 

 

But if i change to Wireguard on Sab, my speed is 1MB/s max. Same endpoint on pia, NL. 

I've deleted the docker (and appdata folder) and reinstalled and configured it, same problem. 

 

What do you need from me and what more can i try?

 

Best regards

Sweex 

I'm in the process of redoing my sabnzbdvpn setup and run into the same issue. Isolated slow speeds all the way down to using a mullvad wireguard .conf file. The logs also show things moving slowly. Direct unpack takes forever, etc. I have a very fast server so it's down to this one thing and it's driving me crazy

[neardeaf]

On 6/8/2023 at 6:13 AM, binhex said:

Hi all, I have made some nice changes to the core code used for all the VPN docker images I produce, details as follows:-

• Randomly rotate between multiple remote endpoints (openvpn only) on disconnection - Less possbility of getting stuck on a defunct endpoint
• Manual round-robin implementation of IP addresses for endpoints - On disconnection all endpoint IP's are rotated in /etc/hosts, reducing the possibility of getting stuck on a defunct server on the endpoint.

I also have a final piece of work around this (not done yet), which is to refresh IP addresses for endpoints on each disconnect/reconnect cycle, further reducing the possibility of getting stuck on defunct servers.
 

In short the work above should help keep the connection maintained for longer periods of time (hopefully months!) without the requirement to restart the container.
 

The work was non-trivial and it is possible I have introduced some bugs (extensively tested) so please keep an eye out of for unexpected issues as I roll out the this change (currently rolled out to SABnzbdVPN and PrivoxyVPN), if you see a new image released then it will include the new functionality.

 

Would you mind going into detail about how to set this up? Do we just put our openvpn files in the /openvpn directory with each different endpoint as a subdirectory? Thanks

[binhex]

5 hours ago, neardeaf said:

Do we just put our openvpn files in the /openvpn directory with each different endpoint as a subdirectory? Thanks

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

[JonathanM]

16 hours ago, neardeaf said:

Direct unpack takes forever,

Maybe try separating the download and unpack destinations into different pools?

[Sweex]

On 8/5/2023 at 4:29 AM, neardeaf said:

I'm in the process of redoing my sabnzbdvpn setup and run into the same issue. Isolated slow speeds all the way down to using a mullvad wireguard .conf file. The logs also show things moving slowly. Direct unpack takes forever, etc. I have a very fast server so it's down to this one thing and it's driving me crazy

Sab in general is quite quick for me, with unpack and such. 

 

I've made new wireguard config files and tried copy the one from Deluge that, in Deluge, goes fast. But to no avail, Sab+Wireguard is still <1MB/s.

[BudgetAudiophile]

Hi all, I updated to Unraid 6.11.5 a few months ago, and ever since then I've been having a weird issues related to Sab. 

 

This started as soon as I updated to this version of Unraid, basically whenever a download is completed and it begins to unpack my CPU usage goes way up and it takes forever to unpack the file. Then when it's doing that or copying the file to my array from the cache drive it basically brings my server to a standstill with high CPU usage. 

 

My other docker containers will begin to flake out, for instance Plex will start to be unable to play back media or the web UI will be inaccessible for a bit. It will periodically come back up but while the download is unpacking or copying it is hit or miss. 

 

I tried running the "Fix common problems" script thinking maybe it was some sort of permissions issue or something but I'm still having the issue and unsure what the solution would be. Any ideas? I can provide logs if needed, just need to know where to find them...

[nekromantik]

hello

anyone else have strange issue with privoxy last few days. I can now no longer view any videos on browser via privoxy on most sites. Youtube works but for example titter videos dont. the spinning buffering sign just stays there and it never starts. Its not vpn issue as connecting to vpn on same endpoint without privoxy and i can view all videos without issues.

[manofoz]

Hello!

 

I just migrated from binhex-sabnzbd to binhex-sabnzbdvpn and download speeds are 1000x less, dropped from around  500 Mpbs to 500 Kpbs. I am using Pravado VPP's OpenVPN configs. 

 

Also, these warnings stated popping up when I switched versions:

 

API key incorrect, Use the API key from Config->General in your 3rd party program: 192.168.0.129 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36]

 

I could use a pointer to help figure out what is causing the bottle neck. I don't see anything in Pravado about throttling speed like this. 

Thanks!