1 hour ago, neardeaf said:

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?

Nope wireguard does not support multiple remote endpoints 

Hi,

I have a kubernetes cluster that I host my arr apps on and I am having problems with sabnzbdvpn.

 

I have never had any problems with mullvad before. I just recently setup a new cluster on a new os called Talos and now I am having DNS issues with starting up. I changed the dns in the wg0.conf file to be 1.1.1.1 instead of 10.64.0.1 and now I don't get the retrying for dns error and I can download stuff but the privoxy is not working. I am so baffled by this because I've had it setup before and it worked.

On 11/20/2024 at 4:14 PM, binhex said:

Nope wireguard does not support multiple remote endpoints 

That's def true, I was wondering though if there was a way to have like a backup config file in wireguard.  So try wg0 first, then if that doesn't work try wg1 etc?

 

Like today a protonvpn server went down.  I didn't realize it because I had no way to know the vpn just stopped working.  All the torrenting stopped though but I was still able to access web interface etc.  Is there some sort of alert I could get through notifiarr or otherwise that could help notify me of this happening?

 

Thanks!

 

 

Thanks @binhex for another great container! Its an easy decision for me to select your variants every time I install a new app.

 

This is my first time routing a separate docker container through one of your VPN enabled containers. Specifically, I'll be routing nzbhydra through sabnzbd and would like for the ability of those two containers to "talk" to one another (sending nzb's directly to sabnzbd for example). Generally speaking, I understand the process of either enabling Privoxy and configuring proxy settings within nzbhydra, or simply routing nzbhydra directly through sabnzbd's network by editing the docker config. That said, Is there a clear advantage of using one method vs the other?

9 hours ago, cinsun42 said:

Is there a clear advantage of using one method vs the other?

The advantage of sharing network is that ALL traffic is routed over the VPN irrespective of protocol, whereas privoxy will only route http(s), so on a practical level this means things like DNS queries from nzbhydra will go over the VPN, whereas with privoxy this will not be the case.

Also do keep in mind not all applications support proxy (most don't), so again this is where sharing the network of a VPN enabled container has the advantage.

 

Having said all of that, use of a proxy is simple when compared to the additional effort required to configure apps to use a shared network.

Has anyone had an issue with speed lately? I'm using this container and qbittorrentvpn and only seeing speed issues with this one. Only getting about 1.5MB/s on my gig line. I've tried resetting my connection with my news server (Tweaknews) but issue seems to be related to VPN (using PIA+Wireguard thru Ontario...same setup as qbittorrentvpn). Disabling VPN on sabnzbdvpn solves the issue.

 

In general, is there a better vpn setup now with PIA+Wireguard for nzb's and torrents than the individual vpn containers?

Edited December 19, 20241 yr by betaman

Hi, I'm experiencing an issue since upgrading to Unraid 7 RC2 a few hours ago: when trying to reach SABnzbd WebGUI, I encounter a connection time out. I've tried restarting the container, deleting and recreating it, but it did not solve the issue.
I've taken a look at the container log, but did not see anything worrying (but I don't have technical skills, so I might be missing something). I've attached the log to this post.
Any support would be much appreciated.

container_log.txt

4 minutes ago, fabienm said:

Hi, I'm experiencing an issue since upgrading to Unraid 7 RC2 a few hours ago: when trying to reach SABnzbd WebGUI, I encounter a connection time out. I've tried restarting the container, deleting and recreating it, but it did not solve the issue.
I've taken a look at the container log, but did not see anything worrying (but I don't have technical skills, so I might be missing something). I've attached the log to this post.
Any support would be much appreciated.

container_log.txt 25.49 kB · 0 downloads

there is nothing obviously wrong in that log file, what is the ip address of the machine you are using to connect to the web ui of sabnzbd?

On 12/20/2024 at 8:43 PM, binhex said:

there is nothing obviously wrong in that log file, what is the ip address of the machine you are using to connect to the web ui of sabnzbd?

Hi, sorry for the delay in my answer.

The IP address of my PC is 192.168.1.165.

It seems the issue was due to the fact that this was connected to Tailscale. I deconnected it from TS, and I was then able to access the WebGUI. But this is odd: when connected to TS, I'm still able to access other container WebGUI, through their local IP address, but not sabnzbd.

Edited December 23, 20241 yr by fabienm

Hi,

I have cannot to connect to my binhex – SABnzbdVPN.

Unfortunately I am one of the guys who just follow youtube tutorials.

 

In the supervisor log I find after restarting the container:

 

2024-12-24 14:08:23,900 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.39.100'

2024-12-24 14:08:23,900 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

2024-12-24 14:08:23,905 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2024-12-24 14:08:23,912 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 100.64.40.242

 

That looks to me that a connection of the vpn is given.

In the  sabnzbd.log I get:

 

2024-12-24 13:57:06,896::INFO::[_cplogging:213] [24/Dec/2024:13:57:06] ENGINE Bus STARTING

2024-12-24 13:57:06,998::INFO::[_cplogging:213] [24/Dec/2024:13:57:06] ENGINE Serving on http://0.0.0.0:8080

2024-12-24 13:57:07,116::INFO::[_cplogging:213] [24/Dec/2024:13:57:07] ENGINE Serving on https://0.0.0.0:8090

2024-12-24 13:57:07,116::INFO::[_cplogging:213] [24/Dec/2024:13:57:07] ENGINE Bus STARTED

2024-12-24 13:57:07,117::INFO::[_cplogging:213] [24/Dec/2024:13:57:07] ENGINE Client ('127.0.0.1', 36986) lost — peer dropped the TLS connection suddenly, during handshake: (8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)')

 

I tried it with and without tailscale running on local IP and tailscale url. Binhex-sonarr and binhex-radarr can also not connect. 

Can anybody help. My kids want their christmas movies 😊

48 minutes ago, Dr.Tom said:

Hi,

I have cannot to connect to my binhex – SABnzbdVPN.

Unfortunately I am one of the guys who just follow youtube tutorials.

 

In the supervisor log I find after restarting the container:

 

2024-12-24 14:08:23,900 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.39.100'

2024-12-24 14:08:23,900 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

2024-12-24 14:08:23,905 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2024-12-24 14:08:23,912 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 100.64.40.242

 

That looks to me that a connection of the vpn is given.

In the  sabnzbd.log I get:

 

I tried it with and without tailscale running on local IP and tailscale url. Binhex-sonarr and binhex-radarr can also not connect. 

Can anybody help. My kids want their christmas movies 😊

You mention Tailscale but have you tried turning off the VPN in the sabnzbdcpn docker config settings? The fact that your *arr dockers aren’t working though points to a configuration issue with your server. Can you access any docker URL’s on your server?

 

I’m sure someone more experienced will come along but since it’s Christmas Eve responses might be sparse.

Thanks Betamax for your quick response,

I can access all my other docker container via the Web interface. Just the connection to sabnzbd is broken.

5 minutes ago, Dr.Tom said:

Thanks Betamax for your quick response,

I can access all my other docker container via the Web interface. Just the connection to sabnzbd is broken.

I thought you also said connection to binhex *arr containers also didn’t work? If only Sabnzbdvpn isn’t working then try setting vpn configuration setting to no in the docker settings and see if it launches?

Sorry disabling vpn does not help the ui does not start

Edited December 24, 20241 yr by Dr.Tom

Same issue here. The docker container "sabnzbd" (without vpn) runs perfectly. I am in the same loop like Dr. Tom. 

Edited December 27, 20241 yr by sne

On 12/24/2024 at 1:31 PM, Dr.Tom said:

Client ('127.0.0.1', 36986) lost — peer dropped the TLS connection suddenly, during handshake:

looks like a vpn provider issue to me, try a different endpoint, if that still fails then contact your vpn provider.

I tried 5 different locations. Provider is PIA, if it helps anyone.

 

Edited December 27, 20241 yr by sne

22 hours ago, sne said:

I tried 5 different locations. Provider is PIA, if it helps anyone.

 

I’m using Ontario with no issue except the random speed drop. Still wondering if there’s a better setup for all containers vs these vpn specific ones?

Hi,

I tried differnt locations and providers -- did not help

then I downgraded from 4.4.1-1-01 from 20.12.2024  to 4.4.0-1-01 from 22.07.2024 but this did not help

 

I ran out of Ideas

Thomas

Hi all,

 

I have migrated to Cloudflare for remote access, and setting up VPN for SABNZBDVPN.  If I don't have VPN running then my remote connection to the Web gui works perfectly (using qualified domain name).  If I turn on VPN in the docker settings then I lose Cloudflare and local access to the GUI.  

 

Surely there should be a way to have VPN connected AND be able to use Cloudflare for remote access.  I have DelugeVPN running (permanently connected to VPN) and CAN access through Cloudlflare with no issues.  Any help out there?

11 hours ago, Reddwarfusa said:

Hi all,

 

I have migrated to Cloudflare for remote access, and setting up VPN for SABNZBDVPN.  If I don't have VPN running then my remote connection to the Web gui works perfectly (using qualified domain name).  If I turn on VPN in the docker settings then I lose Cloudflare and local access to the GUI.  

 

Surely there should be a way to have VPN connected AND be able to use Cloudflare for remote access.  I have DelugeVPN running (permanently connected to VPN) and CAN access through Cloudlflare with no issues.  Any help out there?

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

Hey, does this work well with the new Tailscale? Mine throws below error.

 

[info] Attempting to start SABnzbd...

2025-01-21 23:21:04,275 DEBG 'watchdog-script' stdout output:
Not all required Python modules are available, please check requirements.txt
Missing module: sabctools
You can read more at: https://sabnzbd.org/wiki/installation/install-off-modules
If you still experience problems, remove all .pyc files in this folder and subfolders

has something happened to this docker? It suddenly is timing out whenever I try to acess it from my local network? I run radarr and sonarr though it as a proxy and they can not connect to it either? I am not really a tech guy... how can I troubleshoot thing and get it working again?

this seems to have resolved itself... not sure what happened.. i just removed it and reinstalled it and used all the same settings and now it works...

On 2/3/2025 at 8:42 AM, questionbot said:

has something happened to this docker? It suddenly is timing out whenever I try to acess it from my local network? I run radarr and sonarr though it as a proxy and they can not connect to it either? I am not really a tech guy... how can I troubleshoot thing and get it working again?

I'm having this problem as well since upgrading to Unraid 7 over the weekend, only I don't have my radarr and sonarr connect through it as a proxy. Both radarr and sonarr can connect to it when I click test in the downloader settings, and they can send it requests but I can't connect to the sabnzb or qbittorrent webui, my browser times out and the downloads fail. I can confirm that both sabnzb and qbittorrent are connected to VPN and there are no errors in the docker logs.

 

Anyone have any tips on what to check? Thanks very much.

 

UPDATE: Like the previous poster the issue has resolved itself. Please disregard.

Edited February 19, 20251 yr by jfs9112
Issue solvd itself