Support Forum

Good. Start from fresh. So: stop sabnzbd. Check and recheck it's not running find and rename all sabnzbd.ini files start SAB like this: sabnzbdplus -s 0.0.0.0:8080 -b0 -l2 --inet_exposure 4 access it again, and make sure you get the wizard. If no wizard: go back to step 1 Fill out the wizard with yo...

Yep: the snap is still running, and probably restarting after you kill.

Google-hit:

sudo snap disable vlc

so

sudo snap disable sabnzbd
or
sudo snap disable sabnzbdplus

then verify again.

And if that fails: uninstall the sabnzbd snap, reboot, and verify again.

I would do: back to a fresh config. 1. make sure sabnzbd is not running in any form. Check and recheck! 2. start sabnzbdplus like this: cd sabnzbdplus -s 0.0.0.0:8080 -b0 -l2 --inet_exposure 4 -f blabla$$.ini 3. you should all kind of output. If you do NOT see output, there is still a SAB running, s...

Even then, accessing via 192.168.... should be doable, AFAIK.

OK, a real public IP address. Indeed with "inet_exposure = 4" it should work. The question is: is SAB really using that sabnzbd.ini with its settings? If you go into the VM, and start a browser there, and go into sabnzbd (http://127.0.0.1:8080, can you check Config: Config File: what is us...

what URL do you use to access SABnzbd?

Inside the docker container, is there a "openssl" executable? If so, what do you get when you run that with: openssl s_client -connect news.eweka.nl:563 EDIT ... easier stuff can you fill out as newsserver news.newhosting.com via SSL and Test connection? in SABnzbd RSS section, can you add...

How can we avoid these AI bots?

to which server? newsserver, or the sabnzbd webserver?

In both cases: what URL / FQDN / full address do you use?

check out the other thread in which you posted ... full explanation & howto

ckp33 wrote: ↑April 17th, 2024, 10:43 pm seems to have started this problem only after upgrading to sab 4.2.3

To verify your hypothesis, you can downgrade to sab 4.2.2

Hint: I don't think so.

@safihre

I find defaulting to 0.0 confusing.

Have we considered returning float('nan') in case of problems? Or just -1? So that we can recognize.

So after looking through my docker logs, I was able to find this error - validate protocol negotiate failed: -11 If I google "validate protocol negotiate failed: -11" it gives hits with SMB / CIFS. So filesystem (mount) problem. Indeed you should solve that; not a SABnzbd problem. Good th...

OK. This is how SABnzbd does it: https://github.com/sabnzbd/sabnzbd/blob/develop/sabnzbd/filesystem.py#L1059 Can you do this within your docker, within the SABnzbd directory sander@brixit:~$ cd git/sabnzbd/ # go to directory with SABnzbd.py What does OS say, for working directory: $ df -h . Filesyst...

Indeed: HOW it reports.

I'll check how sabnzbd via a python call checks free system

BRB