For example, the "/config" menu in NZBGet is mapped to /opt/appdata/nzbget (you can see all these in Portainer, clocking on the appropriate docker). NZBGet NZBget script folder. The others are being difficultHmm, interesting. As for seeing scripts, what do the permissions look like on your script folder? The scripts should then appear in NZBGet web-interface. Forums JavaScript is disabled. Then I get to thinking and maybe the path I've been using is the wrong path, since nzbget's maindir is /configI know I was able to add a different file for the MP4 Automator script. For example a video recode script could have a parameter “Resolution”:Post-processing parameters are passed using env-vars with prefix For post-processing scripts NZBGet checks the exit code of the script and sets the status in history item accordingly. By default mine are 001, which isn't bueno I'm guessing. PP-Parameters must be declared in the configuration definition of the script. Restoring configuration. After the download of nzb-file is completed NZBGet can call post-processing scripts (pp-scripts). NZBGet. This is another reason why it's good to save NZB files to a dedicated folder: you can set up NZBGet (or any other newsreader you use) to monitor this folder for new NZBs and automatically start downloading the content associated with them. Best example - unpack password. This allows the scripts called thereafter to process the files in the new location. Use command The scripts executed after your script assume the files in the directory belong to the current download. sudo chmod -R 755 /opt/appdate/nzbget/scripts I'm just surprised that nzbget can't see script files in its own appdata folder. You can define what scripts should be called for the nzb-file using option Please note that these settings define “defaults” for nzb-file. Matt, your apps are all running inside Docker, so file paths can be confusing when trying to translate them to the "outside world". Did you ever figure it out ink0gnito? Please note that the par-check/repair and unpack are performed by NZBGet internally and are not part of post-processing scripts. I did do a chmod 755 on the script folder. Just go to NZBGet’s Settings > Path > NzbDir and change this to the folder in which you save NZB files. Yep haven't messed with the path mappings and that's the path the scripts are in. good to know; i'll check the script to make sure that gets set correctlyYou can't change it from within the Docker container as whatever it has access to can't be changed from within. The most efficient usenet downloader. Well my next step would be to check the scripts to make sure they are valid. It prints one message to log. Here in the# long description we could write instructions for user.# The long description can have multiple paragraphs when needed. Put scripts into ppscripts-folder (option ScriptDir). The information about nzb-file which is currently processed: NZBPP_DIRECTORY - Path to destination dir for downloaded files.

NZBGet provides documented entry points for scripts. I think the permissions are incorrectly set since I get this when I try to run Do a sudo chmod -R 775 instead of the chown command. Maybe try copying the content into a different file that you create and see if it works.

I'm wandering around in the dark with linux terminal, unfortunately...Do you have access to a terminal? You can set message kind by using prefixes:"[ERROR] This nzb-file was not processed correctly, terminating the script"################################################################################# POST-PROCESSING PARAMETERS #### This is a test script. I thought the default PG deployments would set proper perms though so this so confusing. If they are and still no luck, you could add the path directly in Portainer and bind it to /scripts, and then just point nzbget at that and see what happens.Will do. I also have no idea what these scripts do. Though you might have to chown it back to you if it’s messed up.Ok! I'm curious why that would work on one script but not the rest. I'll report back when I have a chance to mess with it some more.The fact that one of them shows up but not the others and they all have the same permissions is puzzling. Hello i have some own nzbget scripts (SafeRename.py, Unpack.py etc).+1, same issue here. You can activate par-check/repair and unpack without using of any post-processing scripts.When a new nzb-file is added to queue it doesn’t have any pp-scripts assigned to it by default. Otherwise the other scripts may process all files in the directory, even the files existed before. Scripts can use following exit codes:Post-processing scripts which move downloaded files can inform NZBGet about that by printing special messages into standard output (which is processed by NZBGet). You'll have to ssh into your machine and run the commands there.When you type in that command does an ls -la command show the appropriate permissions?