Application Name: ngPost

Application GitHub: https://github.com/mbruel/ngPost

GitHub Container: https://github.com/xompage/ngpost/pkgs/container/ngpost 

GitHub: https://github.com/xompage/ngpost

 

Please post any questions/issues relating to this docker you have in this thread.

 

Changelog:

19/09/2023 - Added nzbcheck utility.

18/09/2023 - Applied ngPost article obfuscation fix with 32-62 random characters for each article yenc name. Credits to anon for the original fix.

17/09/2023 - Initial release with ngPost version 4.16.

Edited September 19, 20232 yr by xompage

Excellent. Will be trying this. Was just gonna use the Linux AppImage and continue with that but will definitely try the docker (at some stage!)

2 hours ago, methanoid said:

Excellent. Will be trying this. Was just gonna use the Linux AppImage and continue with that but will definitely try the docker (at some stage!)

If you use the Linux AppImage and want to SSL connect to your provider, but you have the latest distro version, you'll probably run into problems.

This is due to the fact that those images are compiled against the deprecated OpenSSL 1.x.x version:

https://github.com/mbruel/ngPost/issues/182

 

Only way to fix this is by compiling it yourself against OpenSSL 3.x.x or run it with OpenSSL 1.x.x (not recommended).

What was changed in latest update? Nothing showing on GH.    BTW I'm using it now and its working well doing a massive post (will update after) 

27 minutes ago, methanoid said:

What was changed in latest update? Nothing showing on GH.    BTW I'm using it now and its working well doing a massive post (will update after) 

Didn't have time yet to create a Readme, but updated the first post with the changelog

Glad to hear it works good for you! Yesterday I applied patches to fix the articles obfuscation to some random strings to strengthen obfuscation.

EDIT: And latest version from today added the `nzbcheck` utility.

Edited September 19, 20232 yr by xompage

Hi

 

I need to add the --auto-slice-size option to my posts - do you know if that can be done in the config or in the GUI?  To be honest I don't know why that isnt the default (not your fault) anyway

 

EDIT: It's in Par creation so its ParPar, PAR2 args.  I can change mine but it'd make sense to have that in the default config anyway

 

Edited September 19, 20232 yr by methanoid

18 hours ago, methanoid said:

Hi

 

I need to add the --auto-slice-size option to my posts - do you know if that can be done in the config or in the GUI?  To be honest I don't know why that isnt the default (not your fault) anyway

 

EDIT: It's in Par creation so its ParPar, PAR2 args.  I can change mine but it'd make sense to have that in the default config anyway

 

Was not aware of this option.

In what scenarios is it beneficial?

Any time your upload is very large it will barf if the slices are too small and it produces too many. Use the auto sizer and the problem goes away. Its on the GH page for ParPar.   IDK what size upload triggers it but I would guess it is around 50GB as my Linux ISO collection was over 100GB of archives    I'm putting Auto in now and trying again

On 9/20/2023 at 7:21 PM, methanoid said:

Any time your upload is very large it will barf if the slices are too small and it produces too many. Use the auto sizer and the problem goes away. Its on the GH page for ParPar.   IDK what size upload triggers it but I would guess it is around 50GB as my Linux ISO collection was over 100GB of archives    I'm putting Auto in now and trying again

Thanks for the clarification!

If you'd like to check, I created a new docker for Nyuu (v0.4.1 and also master branch) with obfuscation patches applied.

It's supposed to be faster than ngPost, but no GUI.

I added -S to the ParPar options and it was all good.

I'll try the Nyuu container when I get back home. Thanks for that

Sent from my SM-G970F using Tapatalk

Thank you so much

@xompage been using this happily for many months but last time I tried this successfully was XXX and tried it last few days to post a file but every time it crashes when it does the Par creation... it crashes the container I think and KasmVNC loses connection.  After a minute or two it is accessible again but nothing is posted. When it goes down it makes unRAID GUI unresponsive completely and the main share goes offline and comes back AND it starts a Parity check every time...

 

No clue what is going on here.... 

 

EDIT: was my hardware. Somehow it got overclocked 

Edited October 29, 20241 yr by methanoid

Hi,

My apologies for reopening such an old thread. I’m not sure if it’s still actively maintained, but I wanted to ask about enabling auto-monitoring of a folder.

From what I understand, ngpost only supports folder monitoring at startup. Is there any way to achieve dynamic, real-time monitoring using your Docker setup?

Thank you!

--

Solution

--

Note the auto post will disable the GUI so vnc would no longer opens up the console.

Installing nano to edit the config

sudo apt update

sudo apt install nano

config file location

/defaults/autostart

Comment out the dbus-launch /usr/local/bin/ngPost with #

Add in the new line

dbus-launch /usr/local/bin/ngPost --monitor /storage/tmp --compress --rm_posted --disp_progress files

/storage/tmp is the path to your monitored folder, yours might be different.

You can monitor by looking at the logs on your docker page

I noticed the --rm_posted causes the app to crash / randomly

Edited January 6Jan 6 by Zuluuk
I have the solution

Making a docker and publishing it to unraid is a bit of a hassle.
Lets use what we have here, I made a bit of a change to the script and allowing pass through parameters. Due to the way dockers work it self heal so any changes made to the docker isn't permanent. Unless the original creator update the script.

1. Create a tmp local to copy the defaults folder to. This is just a folder redirect. What i did is use point /tmp to /mnt/cache/appdata/ngpost/defaults/

2. Go in to the docker via console. run cp -a /defaults/. /tmp/

3. Change the permissions of the files folder otherwise we can't write to it outside of the docker. run chmod 777 -R /tmp or you will get the following

   

4. Edit the autostart file

   #!/bin/sh

   set -e

   # Check config file

   if [ ! -f "/config/.ngPost" ]; then

   cp /opt/ngPost.sample.conf /config/.ngPost

   fi

   # Create directories

   mkdir -p /output/nzb /output/.logs /output/.tmp

   # Use environment variable for extra args; default is empty

   NGPOST_ARGS="${NGPOST_ARGS:-}"

   exec dbus-launch /usr/local/bin/ngPost $NGPOST_ARGS

5. We are taking the parameters and passing it to the docker. If no parameter are there then just run it like normal.

6. Go into your docker editor and change the /tmp to /defaults

7. Add the to the parameter which we created $NGPOST_ARGS value --auto --monitor /storage --compress --rm_posted --disp_progress files

8. 

This will make the settings persistent. Upload status is reviewed via looking at the logs.

Edited January 7Jan 7 by Zuluuk