Seems this and DelugeVPN are suffering the same fate the qbittorrent container had.
still techinically working but no web gui
Anyone else havning that also?

 

20 minutes ago, Arcau said:

Seems this and DelugeVPN are suffering the same fate the qbittorrent container had.
still techinically working but no web gui
Anyone else havning that also?

 

nope, that is not true, the sabnzbd image has not been rebuilt so it wouldn't of picked up the bug, and just to be clear if the image build was triggered right now it would not hit the same bug as all the vpn images use a shared intermediate image, which is where the bug was (and has since been fixed).

most probably vpn provider related, but this will identify it:-

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

6 hours ago, binhex said:

nope, that is not true, the sabnzbd image has not been rebuilt so it wouldn't of picked up the bug, and just to be clear if the image build was triggered right now it would not hit the same bug as all the vpn images use a shared intermediate image, which is where the bug was (and has since been fixed).

most probably vpn provider related, but this will identify it:-

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

It was weird that both deluge and sab did this at the same time and the fact it still "works" like homarr integration still shows the activity and things and the files do download when pushed by whichever app. Just can not get the web gui to ever load

Execution Command - SAB supervisord.log

11 hours ago, Arcau said:

It was weird that both deluge and sab did this at the same time and the fact it still "works" like homarr integration still shows the activity and things and the files do download when pushed by whichever app. Just can not get the web gui to ever load

Execution Command - SAB 1.43 kB · 0 downloads supervisord.log 37.61 kB · 0 downloads

ok so that is a successful start, i suspect LAN_NETWORK is wrong, what is the ip address of the machine you are using to attempt connection to the web ui of sabnzbd?

10.100.10.25 - same subnet etc

tried with a diiferent vlan that can access the rest of the unraid server and containers also - same thing

every other container works just both the binhex ones I have no longer load a webgui at all

have tried from in-private window different browser - different PC everything - thats why I thought it was linked to the other one that qbit was experiencing

18 minutes ago, binhex said:

ok so that is a successful start, i suspect LAN_NETWORK is wrong, what is the ip address of the machine you are using to attempt connection to the web ui of sabnzbd?

Have also just tested something - exposed it through a tunnel - its at least giving me a hostname verification error . so I can try updating that in the config and give that a go in a few minutes

ok so remote access works..... I have no idea what is happening - do i need to add the server IP to whitelisted host too or something?

 

Just installed the jshrida nzbgetvpn to test if it was something inherent to downloaders or vpn containers and that works fine.

 

I removed sab completely cleared the appdata and image - redownloaded from scratch set everything up as default (changed other containers ports to compensate around it) - and same thing totally inaccessible locally - but can access it remotely with tunnel.

 

I am so confused why it suddenly decided to do this along with deluge

Hi @binhex, I'm trying to enable https access to the sabnzbd web server, but I can't seem to change the default HTTPS port from 8090. Even if I change this value, it reverts to port 8090 when the container is restarted. 8090 doesn't seem to be mapped in the docker configuration and I suppose I could do this myself, but was hoping I could just set it to 8080 (the default webserver port) and call it a day. Is there a particular reason why this port keeps reverting, or am I going about this all wrong?

 

Hey, I saw that 4.5.0 got released. Any plans on also updating the docker image?

9 hours ago, Koko72 said:

Hey, I saw that 4.5.0 got released. Any plans on also updating the docker image?

Looks like the build workflow on github fails. https://github.com/binhex/arch-sabnzbdvpn/actions

2 hours ago, RaEyE said:

Looks like the build workflow on github fails. https://github.com/binhex/arch-sabnzbdvpn/actions

yep im aware of this guys, its due to 7zip not being available for arm, i shall take a look in the next couple of days.

Hi, I am having the exact same issue, the GUI is not working anymore eventhough the container seems to be running smoothly. I didnt change any setting for more than a year

2 hours ago, Jerlam said:

Hi, I am having the exact same issue, the GUI is not working anymore eventhough the container seems to be running smoothly. I didnt change any setting for more than a year

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

On 2/20/2025 at 10:54 AM, Arcau said:

Just installed the jshrida nzbgetvpn to test if it was something inherent to downloaders or vpn containers and that works fine.

 

I removed sab completely cleared the appdata and image - redownloaded from scratch set everything up as default (changed other containers ports to compensate around it) - and same thing totally inaccessible locally - but can access it remotely with tunnel.

 

I am so confused why it suddenly decided to do this along with deluge

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

With last night's release of 4.5.1-1-02, none of my servers will connect, nothing downloads. When i would hit test on Sab server page, they would all attempt to run for maybe 20 seconds then give me some EOF SSL cert type messages. (sorry, didn't capture logs)

 

Manually switched the release to 4.4.1-1-01 and it's operational again.

 

Anyone else encounter this?

On 4/15/2025 at 4:08 AM, Sanborn said:

With last night's release of 4.5.1-1-02, none of my servers will connect, nothing downloads. When i would hit test on Sab server page, they would all attempt to run for maybe 20 seconds then give me some EOF SSL cert type messages. (sorry, didn't capture logs)

 

Manually switched the release to 4.4.1-1-01 and it's operational again.

 

Anyone else encounter this?

same problem here, rollback to 4.4.1-1-01 also worked for me

11 minutes ago, Retrolamer1337 said:

EOF SSL cert type messages. (sorry, didn't capture logs)

can i get a bit more detail than this guys.

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

I just wanted to mention that i have the same issue. im not able to connect to the WebUI via my local ip. Im using Zerotier and Tailscale and with im also not able to connect. I was able few weeks ago somehow by deactivating Zerotier and connecting via Tailscale but now even that does not work. I cannot see any errors in the log and also the downloader is running normally in the background and im still able to use it via Sonarr / Radarr but like i said no access to the UI.

Having similar issue as others with not being able to connect to webui on my local network.  I run the binhex-delugevpn container and have no issues connecting to the webui for that container.  I added my tailscale network to the container's local network and tried connecting from a machine running tailscale and one not running tailscale but got the same "External internet access denied - https://sabnzbd.org/access-denied" message on both.    

 

Attaching requested files, appreciate your help.

command execution file.txt supervisord.log

1 hour ago, heisenberg815 said:

Having similar issue as others with not being able to connect to webui on my local network.  I run the binhex-delugevpn container and have no issues connecting to the webui for that container.  I added my tailscale network to the container's local network and tried connecting from a machine running tailscale and one not running tailscale but got the same "External internet access denied - https://sabnzbd.org/access-denied" message on both.    

 

Attaching requested files, appreciate your help.

command execution file.txt 1.14 kB · 1 download supervisord.log 34.96 kB · 0 downloads

incorrect LAN_NETWORK, from your log:-

LAN_NETWORK defined as '10.95.58.42/32,192.168.0.1/24'

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

16 hours ago, binhex said:

incorrect LAN_NETWORK, from your log:-

LAN_NETWORK defined as '10.95.58.42/32,192.168.0.1/24'

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

Thank you, I corrected what I think you were referring to and restarted.  I have pasted a new file with what I think is the correct CIDR notation and I am still getting the same error.  The reason I had the LAN_NETWORK defined as I did was because my delugevpn docker works with the 192.168.0.1/24 notation even though it isn't correct. 

supervisord1.log

I figured out my problem, it had to do with the bad CIDR notation being in the sabnzbd.ini file.  I don't think the updated LAN_NETWORK was making it into the local_ranges variable in the ini file for some reason.  When I manually edited the ini file and put in the correct CIDR notation it worked fine.  Hope that helps others if they are having similar issue.

All of a sudden I can't connect to NNTP over SSL via my PIA wireguard tunnel. 

 

PIA support suggest I change MTU in wg0.conf. Only that won't work since wg0.conf is auto generated after each container start. 

 

So what do I do? Ideally I would like to add custom wireguard settings via environment variables but it doesn't seem to be possible so I really have no idea. 

 

Thanks

 

/klaus

I can't connect to NNTP over SSL anymore as well, but with a ProtonVPN wireguard tunnel. Using another SABnzbd container with a GluetunVPN container (also using ProtonVPN) as network works just fine. So I would assume it's not the VPN's fault.