Support Forum

You'd want to check if the same config file is used (your topic start post mentions '/home/sabnzbd/.sabnzbd/sabnzbd.ini' so you know where to look). As safihre mentioned, you're most likely running two different instances, for example because you setup two different autostart mechanisms and/or combi...

Waarschijnlijk hetzelfde probleem als beschreven in https://github.com/sabnzbd/sabnzbd/issues/1669

Essential details are missing: the ubuntu versions involved, the error you get, and from where you installed sab (ppa or standard repos, before and after the os upgrade).

You can use a postprocessing script to do that. Note that scripts receive a bunch of useful info in the form of environment variables in addition to the 8 command-line params listed, including the full path to the nzb.

For sab to allow external access, the host setting must e changed from its localhost default. Granting other systems access to a service running on a VM is completely dependent on the network settings for that VM, nothing specific to sab.

Als je een cipher forceert in sab die niet door zowel je eigen systeem (openssl) als de server ondersteund is, kan geen versleutelde verbinding opgezet worden en krijg je dus deze melding. Openssl faseert op z'n tijd zwaar verouderde ciphers (zoals rc4-md5) uit, die zo gemakkelijk te kraken zijn dat...

The program cannot dynamically generate that path based on some template. If you want the category name as part of the path, simply setup the per-category path that way (in the category settings, obviously).

The only not so common thing in the log are a bunch of these: INFO::[nzbparser:103] Duplicate part x, but different ID-s The remainder looks like standard cases of content removed server side. Ironically, some servers take longer to admit they don't have an article than it would have taken to downlo...

safihre wrote: ↑

August 27th, 2020, 4:03 pm

Well, I am the maintainer of the Synology package.. So guess I have work to do

Only takes a simple one-liner to mod the shebang to whatever you want:

So my initial guess was right. Best to leave it at /usr/bin/python3, which works in most cases. If the script comes as part of a package (don't have synology stuff around to try but the path /var/packages/sabnzbd/target/var/scripts/Deobfuscate.py does suggests so) and the system uses non-standard lo...

pven wrote: ↑

August 25th, 2020, 3:51 am

nice: can't execute '/var/packages/sabnzbd/target/var/scripts/Deobfuscate.py': No such file or directory

The No such file or directory part could also be referring to whatever is in the shebang line inside the script, for example an outdated or otherwise incorrect path to a python interpreter.

The sabnzbdplus package is not some wrapper around git. You cannot update sab by running 'git pull' unless you're running from git source.

Nice to see thing worked out. Using the init.d service that comes with the package - as you eventually did - had the side effect of letting you benefit from the sane environment it sets up. Basically, LANG is taken from /etc/default/locale (if defined), and PYTHONIOENCODING hardcoded to utf-8 to get...

Indeed just changing the default completed dir (and any such directories you set for categories) should do.

You might want to change that watched dir though, so it's separate from incomplete and complete dirs (e.g. F:\Downloads\WatchDir).

Recent changes to the way the interface templates communicate with the program backend may result in such errors after an upgrade if you didn't restart the application (and maybe clean browser cache). Was there a python traceback or other information on screen when you got this error?