January 16, 20242 yr Author 16 minutes ago, derjp said: So as i tried to make changes in settings of nzbget-ng i receive the following error: you dont know were i can find this folder or what i can do to solv this? you need to go to the support thread for that image, i'm sorry i cannot support other images.
January 16, 20242 yr 7 minutes ago, binhex said: you need to go to the support thread for that image, i'm sorry i cannot support other images. i couldn´t finde one, but no problem, not your image, not your support, thanks anyway
January 16, 20242 yr 4 hours ago, binhex said: you need to go to the support thread for that image, i'm sorry i cannot support other images. Looks as there isn't one. You can reach out to @welfare, but hasn't been on the forum for a month, and last post is Aug 2023. https://forums.unraid.net/profile/129748-welfare/
February 6, 20242 yr Hi Binhex Thanks for your great templates, you and other dev's make Unraid what it is. I've been using the ich777 nzbget image however this is marked as depreciated so I thought I would spin up yours and transition to the more up to date version. Not sure why or whether its the template or some strange Docker behaviour but after installing your nzbget app from the app store the settings for the other (ich777) docker have been altered. steps to recreate - install and set up Ich777 nzbget running default port 6789 click on the nzbget icon and "WEBGUI" a new tab opens correctly to localhost:6789 (yay all good) stop nzbget docker install from apps tab "Binhex-nzbget" with following change from default stipulate a different port other than 6789 (taken by Ich777 nzbget) within the template options. I used port 6799 stipulate a different directory for data to download to start binhex-nzbget open webgui which correctly opens localhost:6799 stop binhex-nzbget remove the app and files restart ich777 nzbget attempt to open ich777 nzbget WEBGUI web gui cannot be reached check nzbget logs - all appears normal and running fine. check ip address which cannot be reached and Ich777 nzbget is now attempting to open localhost:6799 instead of localhost:6789 double check template for ich777 nzbget and it is still showing 6789 restart docker service same incorrect mapping still occurs. Also if running both nzbget instances at the same time, the ich777 nzbget instance incorrectly shows the 6799 port mapping on the docker dashboard. Finally typing the correct ip and port into the address bar (localhost:6789) correctly brings up the ich777 nzbget app Hope that all makes sense. Thanks
February 6, 20242 yr 10 hours ago, dgs2001 said: Hi Binhex Thanks for your great templates, you and other dev's make Unraid what it is. I've been using the ich777 nzbget image however this is marked as depreciated so I thought I would spin up yours and transition to the more up to date version. Not sure why or whether its the template or some strange Docker behaviour but after installing your nzbget app from the app store the settings for the other (ich777) docker have been altered. steps to recreate - install and set up Ich777 nzbget running default port 6789 click on the nzbget icon and "WEBGUI" a new tab opens correctly to localhost:6789 (yay all good) stop nzbget docker install from apps tab "Binhex-nzbget" with following change from default stipulate a different port other than 6789 (taken by Ich777 nzbget) within the template options. I used port 6799 stipulate a different directory for data to download to start binhex-nzbget open webgui which correctly opens localhost:6799 stop binhex-nzbget remove the app and files restart ich777 nzbget attempt to open ich777 nzbget WEBGUI web gui cannot be reached check nzbget logs - all appears normal and running fine. check ip address which cannot be reached and Ich777 nzbget is now attempting to open localhost:6799 instead of localhost:6789 double check template for ich777 nzbget and it is still showing 6789 restart docker service same incorrect mapping still occurs. Also if running both nzbget instances at the same time, the ich777 nzbget instance incorrectly shows the 6799 port mapping on the docker dashboard. Finally typing the correct ip and port into the address bar (localhost:6789) correctly brings up the ich777 nzbget app Hope that all makes sense. Thanks So stopping and restarting the docker service did not fix this, but a server restart has corrected it. Just wondering if I can get the two nzbget dockers to play nice (They are named differently and using different port allocations)
February 7, 20242 yr On 11/13/2023 at 4:24 PM, PBA+J said: If I wanted to restart every 3 minutes, I can use CA User Scripts to accomplish this, correct? I labeled it NZB Restart I used the following in the scripts: #!/bin/bash docker restart binhex-nzbget I run in the background on Custom and set this input for custom: */3 * * * * That should restart NZB every 3 minutes, right? Thanks for posting this. I followed your lead and set this up as well. Script works and the restarts at least allow some of my backlog to process a little at a time. Might tweak the frequency later but good enough for now. *edit: changed to every 30 minutes and is working well for me Edited February 7, 20242 yr by MACGoof
February 7, 20242 yr Author 13 hours ago, dgs2001 said: Just wondering if I can get the two nzbget dockers to play nice (They are named differently and using different port allocations) definitely possible, just ensure the name, the host port is different for each container and also you must have completely separate /config for each container, they cannot share the same path. 13 hours ago, dgs2001 said: check ip address which cannot be reached and Ich777 nzbget is now attempting to open localhost:6799 instead of localhost:6789 The fact it was fixed by a restart probably points the finger of blame at unraid web ui, but you can verify the port used to connect to the web ui by edit/toggling 'advanced view' (top right) and then checking the 'WebUI' port is what you expect, it is possible the web ui port did not update when you changed it.
February 18, 20242 yr how can I run binhex-nzbget through binhex-qbittorrentvpn so it shares the VPN... I have privoxy enabled on the qbittorrent container... but I can not seem to see a privoxy setting in nzbGet Settings? : EDIT : I worked out a way of sharing the vpn form the other docker, but not using privoxy ... I had to change how the networking worked.... instructions can be found here... Q 24/25 https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Seems to be working fine... let me know if there is a better way to do this. Edited February 18, 20242 yr by questionbot
March 13, 20242 yr Hi Binhex, I have been running this image of NZBGET for around a month now but am seeing lots of unpack stalls. Also seeing tls errors. its strange because the old image which was ich777 does not suffer from either problem. just keeps nagging me aboput being depreciated! Have you managed to have a look at any fixes for the unpack issue? Thanks
March 13, 20242 yr Author 1 hour ago, dgs2001 said: Have you managed to have a look at any fixes for the unpack issue? I've tried everything!, im currently out of ideas as to the cause 😞
March 13, 20242 yr 1 hour ago, binhex said: I've tried everything!, im currently out of ideas as to the cause 😞 Have you tried the forked https://nzbget.com/ version as opposed to the archived https://nzbget.net/ ?
May 23, 20242 yr Author I have now switched the build scripts over to https://github.com/nzbgetcom/nzbget/releases next release incoming shortly will be from here and for the foreseeable future.
June 1, 20242 yr On 5/23/2024 at 5:50 AM, binhex said: I have now switched the build scripts over to https://github.com/nzbgetcom/nzbget/releases next release incoming shortly will be from here and for the foreseeable future. Thanks for the update. Unfortunately the stuck on unpacking is still happening so I think I will just setup a script to refresh it occasionally (assuming that is possible)
June 3, 20242 yr On 6/1/2024 at 2:00 AM, AngryPig said: Thanks for the update. Unfortunately the stuck on unpacking is still happening so I think I will just setup a script to refresh it occasionally (assuming that is possible) Just as an FYI, I found the old nzbget Github issue for this - https://github.com/nzbget/nzbget/issues/558 After knowing where to look I found the same issue (unpack that resets to zero) and found that if I cancel the unpack process in the GUI I can manually unpack it from the console of the container. I doubt it helps but at least it is consistent symptoms on the new version some six years later
August 13, 20241 yr I have noticed that on all of my binhex containers the port mappings are now empty after the latest update of the containers. The only one that didn't update was overseerr which still has the port mappings. Any idea how to fix this as it causes issues when I click the webui menu button as it doesn't work.
August 14, 20241 yr 5 hours ago, doma_2345 said: I have noticed that on all of my binhex containers the port mappings are now empty after the latest update of the containers. The only one that didn't update was overseerr which still has the port mappings. Any idea how to fix this as it causes issues when I click the webui menu button as it doesn't work. Have you tried stopping and restarting the docker service? You should be able to use the template function to reinstall with previous mappings…or edit them all as a last resort.
August 14, 20241 yr 4 hours ago, PBA+J said: Have you tried stopping and restarting the docker service? You should be able to use the template function to reinstall with previous mappings…or edit them all as a last resort. Yes, i have tried restarting the docker service. I have tried doing a force update. I am not sure what the 'template function' is (i assume you mean reinstalling from template) i havent tried this and dont really want to delete all of these containers to do this, In terms of editing them i am not sure what has been removed in the last update to edit them to put it back.
September 9, 20241 yr SOLVED: Cannot login to WebUI: "Unable to Connect" New install. docker run -d --name='binhex-nzbget' --net='pearsonproxy' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-nzbget" -e 'SHARED_NETWORK'='no' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:6789]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/nzbget-icon.png' -p '6789:6789/tcp' -v '/mnt/user/appdata/binhex-nzbget':'/config':'rw' -v '/mnt/user/data/usenet/':'/data':'rw' -v '/mnt/user/binhex_shared/':'/shared':'rw' 'binhex/arch-nzbget' 1ba4362e45fc9077e9e4821d567a25e545dd7d578b033e7d25794e9a67ba8914 The command finished successfully! The docker log file Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-09-08 22:02:46.912607 [info] Host is running unRAID 2024-09-08 22:02:46.941091 [info] System information: Linux 1ba4362e45fc 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux 2024-09-08 22:02:46.971572 [info] Image tags: IMAGE_RELEASE_TAG=v24.2-01 2024-09-08 22:02:47.021784 [info] PUID defined as '99' 2024-09-08 22:02:47.078802 [info] PGID defined as '100' 2024-09-08 22:02:47.124132 [info] UMASK defined as '000' 2024-09-08 22:02:47.162507 [info] Permissions already set for '/config' 2024-09-08 22:02:47.195955 [info] Deleting files in /tmp (non recursive)... 2024-09-08 22:02:47.251337 [info] SHARED_NETWORK defined as 'no' 2024-09-08 22:02:47.282331 [info] Starting Supervisor... 2024-09-08 22:02:47,492 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing 2024-09-08 22:02:47,496 INFO Set uid to user 0 succeeded 2024-09-08 22:02:47,500 INFO supervisord started with pid 6 2024-09-08 22:02:48,504 INFO spawned: 'nzbget' with pid 59 2024-09-08 22:02:48,505 INFO reaped unknown pid 7 (exit status 0) 2024-09-08 22:02:48,514 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists [info] Patching NZBGet config file for existing users... 2024-09-08 22:02:48,538 DEBG 'nzbget' stdout output: [info] Starting NZBGet non-daemonised and specify config file (close stdout due to chatter)... 2024-09-08 22:02:49,540 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Edited September 10, 20241 yr by OriginalFlavor
September 9, 20241 yr Author 5 hours ago, OriginalFlavor said: --net='pearsonproxy' not sure how this is configured but i would suspect this is your issue, switch back to the default, which is 'bridge' and i suspect things will work as expected.
November 22, 20241 yr Can anyone give me a suggestion on how to sort these errors? I had one file get stuck unpacking. I just deleted it and it all started working again. Info, Warning, Error are all zero'd out now. Just trying to figure out if I setup something wrong. Edited November 22, 20241 yr by DavePCLoadLetter
January 6, 20251 yr All of sudden today my docker stopped working. Started to get a segmentation fault with unrar. No idea what I should do to fix. I've uninstalled the docker and resinstalled it, the issue still exists. Snippet of the logs: [info] Patching NZBGet config file for existing users... 2025-01-06 05:47:04,502 DEBG 'nzbget' stdout output: [info] Starting NZBGet non-daemonised and specify config file (close stdout due to chatter)... 2025-01-06 05:47:05,502 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-01-06 06:43:29,636 DEBG 'nzbget' stderr output: /home/nobody/start.sh: line 43: 65 Segmentation fault "${app_path}/nzbget" --option UnrarCmd=/usr/sbin/unrar -c "${config_filepath}" -s 1>&- 2025-01-06 06:43:29,636 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23217879134240 for <Subprocess at 23217862778304 with name nzbget in state RUNNING> (stdout)> 2025-01-06 06:43:29,636 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23217862639200 for <Subprocess at 23217862778304 with name nzbget in state RUNNING> (stderr)> 2025-01-06 06:43:29,636 WARN exited: nzbget (exit status 139; not expected) 2025-01-06 06:43:29,637 DEBG received SIGCHLD indicating a child quit 2025-01-06 06:43:29,639 INFO spawned: 'nzbget' with pid 587
January 7, 20251 yr I was able to fix the error above by deleting all files within the destination folder, intermediate folder, and nzb folder. Once they where all deleted, nzbget started without an error.
January 21, 20251 yr for the last month I've got about a 90% failure rate. They all download, but die downloading PAR files. I spoke with a friend that uses the same newserver and he doesn't have issues.
March 4, 20251 yr On 11/22/2024 at 11:26 AM, DavePCLoadLetter said: Can anyone give me a suggestion on how to sort these errors? I had one file get stuck unpacking. I just deleted it and it all started working again. Info, Warning, Error are all zero'd out now. Just trying to figure out if I setup something wrong. Im having this same issue, did you ever figure out the solution? Im having similar errors and warnings as well
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.