Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - SABnzbdVPN

Featured Replies

FYI Sorted the above.

 

Changed the permission on the unraid share for just the completed folder to match the incomplete folder and now its working. although not touched the settings of the shares in over 3 years so no idea what caused it.

  • Replies 1.8k
  • Views 423.3k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • i'm aware of the issue guys and i think i have a fix, i shall post back when i have built a fixed image.

  • hi guys, spotted the issue regards dos2unix.sh and corrected it, image now  building, should be done in around an hour.. then pull and you should be back up and running.

  • there are ongoing issues with PIA DNS, you can try setting NAME_SERVERS to the following (removes PIA DNS):- 84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1  

Posted Images

@binhex I do have one further question though.

 

I am using PIA via wireguard in the container and am constantly getting the below when trying to DL items... if I click the spanner and click unblock it will eventually work... if I am DL'ing things in the background (on a schedule per se) it may happen when it first gets added but will eventually resolve itself after the 10min wait..

 

any idea why this happens? is it because of the name servers in the template of the container and maybe one of them cannot resolve the server of the news reader?

 

image.thumb.png.4cfc5ef3396fc70de450961dd6dbdb2d.png

Edited by enigma27

  • 2 weeks later...
On 5/21/2024 at 7:04 AM, enigma27 said:

@binhex I do have one further question though.

 

I am using PIA via wireguard in the container and am constantly getting the below when trying to DL items... if I click the spanner and click unblock it will eventually work... if I am DL'ing things in the background (on a schedule per se) it may happen when it first gets added but will eventually resolve itself after the 10min wait..

 

any idea why this happens? is it because of the name servers in the template of the container and maybe one of them cannot resolve the server of the news reader?

 

image.thumb.png.4cfc5ef3396fc70de450961dd6dbdb2d.png

Having the same issue but in my case the timing is coincidental with a modem change from my ISP (Spectrum). Also having DNS issues with Qbittorrentvpn from Binhex (using PIA and Wireguard).  Also, in my case it never resolves itself.

 

image.thumb.png.4f6227b8877290f1d7b65f0b7d713f1a.png

 

EDIT: Pretty sure it's the same issue with both (and related to the new modem) as I have the same DNS failure in both docker logs:

 

image.png.1cedd0580ddc986740e7a1f7c841c64a.png

 

EDIT 2: Idiot alert...never thought to restart the containers after the modem change. Doh..all fixed.

Edited by betaman

Whenever the container restarts, updates, or the system restarts, the app won’t open afterwards. 
 

the webui wont lost at all. I typically have to fiddle with the setting a few time and randomly the container starts working again. This is with PIA. The same issue happens with the qbit-vpn container. 

  • Author
49 minutes ago, Wonka88 said:

Whenever the container restarts, updates, or the system restarts, the app won’t open afterwards. 
 

the webui wont lost at all. I typically have to fiddle with the setting a few time and randomly the container starts working again. This is with PIA. The same issue happens with the qbit-vpn container. 

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

 I swapped out motherboard and CPU on my unraid server, and since then, the sabnzbd UI won't load. I've attached the logs as per the help instructions. Any help would be greatly appreciated. Thank you

sabnzbd_container_out.txt sabnzbd_supervisord.txt

  • Author
33 minutes ago, manderso said:

 I swapped out motherboard and CPU on my unraid server, and since then, the sabnzbd UI won't load. I've attached the logs as per the help instructions. Any help would be greatly appreciated. Thank you

sabnzbd_container_out.txt 1.24 kB · 0 downloads sabnzbd_supervisord.txt 37.68 kB · 0 downloads

from your logs:-
Inactivity timeout (--ping-restart), restarting

 

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

  • 2 weeks later...

Hi I had to reinstall my docker containers and since then I have been unable to access the sabnzbd webgui with the vpn active. Sabnzbd seems to start and sonarr and radarr can access sabz as downloads are passed between the dockers however the GUI is never accessible. If I turn off the vpn and restart the docker then I can access it instantly. I cant see any errors in the log nor nothing seems to fail to start.

 

"2024-06-16 12:13:08,503 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080"

 

I have looked through help articles and havent found an answer as most indicate that the webgui wont start if there is an issue with the vpn connection, which there isnt in this case as the services start, I just cant access the webgui.

 

I have provided a log output of the supervisors, and obfuscated the IP addresses. One thing that I have noticed is that the vpn start takes a few attempts before establishing, however all seems to start successfully after a few minutes, I just cant access the webgui.

 

 

supervisord.log

  • Author
47 minutes ago, HumanSkunk said:

Hi I had to reinstall my docker containers and since then I have been unable to access the sabnzbd webgui with the vpn active. Sabnzbd seems to start and sonarr and radarr can access sabz as downloads are passed between the dockers however the GUI is never accessible. If I turn off the vpn and restart the docker then I can access it instantly. I cant see any errors in the log nor nothing seems to fail to start.

 

"2024-06-16 12:13:08,503 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080"

 

I have looked through help articles and havent found an answer as most indicate that the webgui wont start if there is an issue with the vpn connection, which there isnt in this case as the services start, I just cant access the webgui.

 

I have provided a log output of the supervisors, and obfuscated the IP addresses. One thing that I have noticed is that the vpn start takes a few attempts before establishing, however all seems to start successfully after a few minutes, I just cant access the webgui.

 

 

supervisord.log 13.29 kB · 1 download

what is the ip address of the machine running the web browser that you are using to attempt connection to the applications web ui?

Hi thanks for the reply. 192.168.0.10 is the ip address of the unraid. I have tried access it from my PC (chrome) which is 0.2 and my MacBook (safari) which is 0.204. Both just time out. If I start it with the argument for the VPN set to no then it is instantly available.

Edited by HumanSkunk
spelling.

Are you kidding me... how did I miss that. I obviously changed it when I set it up the first time as I didnt have this issue originally, but when I had to remake them I missed changing that option. Odd that it works when dont have the vpn active, or does that config setting only get used when the vpn is set to yes? I have changed it and it works now. Thanks... feeling stupid now.

  • Author
1 minute ago, HumanSkunk said:

Odd that it works when dont have the vpn active,

not odd at all, without the vpn active no iptables are active (firewall) so no blocking is enforced.

Ah that makes sense then. Thanks for clarifying.

  • 2 weeks later...

Hey,
i just got a quick question:
Is it possible to add two LAN_NETWORKS?
I got 2 Networks at home and wanted to reach SAB from both networks.

  • Author
1 minute ago, b0rgi85 said:

Hey,
i just got a quick question:
Is it possible to add two LAN_NETWORKS?
I got 2 Networks at home and wanted to reach SAB from both networks.

you add the next network with a comma as the separator e.g.:-
192.168.1.0/24,192.168.2.0/24

I just updated to the latest version yesterday, and now I can't connect to the GUI, and I'm getting this in the logs:

 

2024-07-02 06:29:03.508182 [info] Host is running unRAID
2024-07-02 06:29:03.539106 [info] System information Linux 4b1397840fb5 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
2024-07-02 06:29:03.602092 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-02 06:29:03.635790 [info] PUID defined as '99'
2024-07-02 06:29:03.680954 [info] PGID defined as '100'
2024-07-02 06:29:03.745159 [info] UMASK defined as '000'
2024-07-02 06:29:03.775618 [info] Permissions already set for '/config'
2024-07-02 06:29:03.813028 [info] Deleting files in /tmp (non recursive)...
2024-07-02 06:29:03.881986 [info] VPN_ENABLED defined as 'yes'
2024-07-02 06:29:03.924489 [info] VPN_CLIENT defined as 'openvpn'
2024-07-02 06:29:03.945996 [info] VPN_PROV defined as 'pia'
2024-07-02 06:29:04.020537 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca_toronto.ovpn
2024-07-02 06:29:04.147855 [info] VPN remote server(s) defined as 'ca-toronto.privacy.network,'
2024-07-02 06:29:04.183599 [info] VPN remote port(s) defined as '1197,'
2024-07-02 06:29:04.203870 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-02 06:29:04.242027 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-02 06:29:04.289293 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-02 06:29:04.315415 [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'
Error: error sending query: Could not send or receive, because of network error
Error: error sending query: Could not send or receive, because of network error
...

 

The error just keep repeating (I know it retries every 10 seconds or so). I've left it sit overnight and it was still erroring out this morning. I've restarted the app a few times with no luck. 

I don't know if this error is a VPN issue or not, but I have one other docker (qbittorrent) that is connecting to my VPN just fine, and I have my laptop and cell phone also connected to PIA just fine.

  • Author
1 hour ago, Lonewolf147 said:

I just updated to the latest version yesterday, and now I can't connect to the GUI, and I'm getting this in the logs:

 

2024-07-02 06:29:03.508182 [info] Host is running unRAID
2024-07-02 06:29:03.539106 [info] System information Linux 4b1397840fb5 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
2024-07-02 06:29:03.602092 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-02 06:29:03.635790 [info] PUID defined as '99'
2024-07-02 06:29:03.680954 [info] PGID defined as '100'
2024-07-02 06:29:03.745159 [info] UMASK defined as '000'
2024-07-02 06:29:03.775618 [info] Permissions already set for '/config'
2024-07-02 06:29:03.813028 [info] Deleting files in /tmp (non recursive)...
2024-07-02 06:29:03.881986 [info] VPN_ENABLED defined as 'yes'
2024-07-02 06:29:03.924489 [info] VPN_CLIENT defined as 'openvpn'
2024-07-02 06:29:03.945996 [info] VPN_PROV defined as 'pia'
2024-07-02 06:29:04.020537 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca_toronto.ovpn
2024-07-02 06:29:04.147855 [info] VPN remote server(s) defined as 'ca-toronto.privacy.network,'
2024-07-02 06:29:04.183599 [info] VPN remote port(s) defined as '1197,'
2024-07-02 06:29:04.203870 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-02 06:29:04.242027 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-02 06:29:04.289293 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-02 06:29:04.315415 [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'
Error: error sending query: Could not send or receive, because of network error
Error: error sending query: Could not send or receive, because of network error
...

 

The error just keep repeating (I know it retries every 10 seconds or so). I've left it sit overnight and it was still erroring out this morning. I've restarted the app a few times with no luck. 

I don't know if this error is a VPN issue or not, but I have one other docker (qbittorrent) that is connecting to my VPN just fine, and I have my laptop and cell phone also connected to PIA just fine.

check your firewall/router, are you blocking port 53 (name servers), in particular look for any sign of 84.200.69.80 being blocked.

Also no GUI after yesterday's update. I did not have those messages in the log, just a list of locations. Reverted to 4.3.2-1-03 and now working again.

Will do - stand by...

  • Author
23 minutes ago, Lignumaqua said:

Debug files as requested using 'latest'.supervisord.txtsabnzbdvpn_Command_Execution.txt

So i have added in the ability to assign an incoming port for all vpn images, reason why you might want this for sabnzbd (an application that does not require an incoming port) is in case you are sharing the vpn network with other containers that do require an incoming port, for instance deluge.
So you might be asking what has this got to do with your issue, well it looks like you have set STRICT_PORT_FORWARD to 'yes', from your log:-
2024-07-02 13:09:40.800309 [info] STRICT_PORT_FORWARD defined as 'yes'

This did nothing previously as sabnzbd did not require an incoming port, but with my change this setting actually does do something, if you set it to 'yes' (as you have done) you can only connect to endpoints which support port forwarding, your selected endpoint 'us-texas.privacy.network' does NOT support port forwarding, as can be seen from your log:-
[info] PIA endpoint 'us-texas.privacy.network' is NOT in the list of endpoints that support port forwarding shown below

So what's the fix?, either connect to an endpoint that does support port forwarding, check your log for details, or simply set STRICT_PORT_FORWARD to 'no'.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.