February 11, 20197 yr Just within the past day or two I can no longer connect to the web ui. I go to http://ipaddr:6789 and it just spins forever... This is all I see in the log file of the docker: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-02-11 15:20:17.511530 [info] System information Linux d2f2b42ddccb 4.18.20-unRAID #1 SMP Fri Nov 23 11:38:16 PST 2018 x86_64 GNU/Linux 2019-02-11 15:20:17.607347 [info] PUID defined as '99' 2019-02-11 15:20:18.176309 [info] PGID defined as '100' 2019-02-11 15:20:18.650827 [info] UMASK defined as '000' 2019-02-11 15:20:18.683927 [info] Permissions already set for volume mappings 2019-02-11 15:20:19.209837 [info] Starting Supervisor... 2019-02-11 15:20:21,465 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing 2019-02-11 15:20:21,465 INFO Set uid to user 0 succeeded 2019-02-11 15:20:21,471 INFO supervisord started with pid 7 2019-02-11 15:20:22,472 INFO spawned: 'nzbget' with pid 44 2019-02-11 15:20:22,480 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2019-02-11 15:20:23,481 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Anyone have any good ideas on how to troubleshoot/start over/other logs to look in?
February 21, 20197 yr Hi, I recently moved from SAB to nzbget and the only feature I'm missing is notifications. Found a script to send pushover notifications, but it does not work. Aparently it needs phyton for the script to work. Is it installed? Could it be easily added? Thanks in advance!
February 25, 20197 yr Just like some of the others I moved over from SaB to nzbget. Is their any way of adding privoxy support to nzbget? I use all of your contaniers including deluge-vpn, i just want to protect my privacy when I'm useing my downloaders. Thanks for all your hard work making and maintaning these dockers.
February 25, 20197 yr 2 hours ago, dirknina said: Just like some of the others I moved over from SaB to nzbget. Is their any way of adding privoxy support to nzbget? I use all of your contaniers including deluge-vpn, i just want to protect my privacy when I'm useing my downloaders. Thanks for all your hard work making and maintaning these dockers. Since you are using deluge-vpn, there is no need for a second privoxy on your system. Just point all your http proxy settings through the existing deluge-vpn privoxy. If you are talking about sending the actual download traffic through the VPN, that's a different thing altogether. If you are using SSL connections to your usenet servers, there is really no need for a VPN for usenet.
February 25, 20197 yr problem i have is i dont see a proxy setting on nzbget unless its named diffrently. but yes i want to send all download traffic though the vpn. i got sonarr and radarr already set up Edited February 25, 20197 yr by dirknina
March 6, 20197 yr I'm trying to resolve this error I get whenever starting up NZBget. It doesn't hinder me from functioning (from what I can tell) but I want to resolve it if possible. Could not initialize TLS, secure certificate is not configured or the cert-file was not found. Check option <SecureCert> I'm running NZBget through a reverse proxy using letsencrypt. As far as I can tell, everything is working fine there. I have two news-servers (usenetServer and UsenetFarm) both show successful when testing and both are going through SSL. I have a few downloads that are stuck in a "queue" state all at 99.9%. I'm assuming that means there is a missing file from a DMCA take down or something?
March 8, 20197 yr I've scanned through most of the thread and looked around on the interwebs and haventfound an answer yet, but sorry if I missed it. I'm using NZBGet and it all works fine, except it will frequently stall on unpacking things. Other files will download and wait in the unpacking queue, but I seem to have to restart the NZBGet docker to get them unpacking again. Is this just me? Does anyone know what I can do to fix it?
March 13, 20197 yr Hello, is there a way to add the certstore from curl into nzbget? (https://curl.haxx.se/docs/caextract.html) Is it necessary to do so? If so how would one go about doing that? I have had a bunch of TLS certification errors during downloads recently. Oddly enough it has only occurred with downloads coming from sonarr. Nothing that radarr downloads gets certification errors.
March 29, 20197 yr Hope someone has some advice. I'm new to using dockers (been doing it for about two months). I set up Sonarr and NZBGet. The issue I'm having is that when NZBGet tries to unpack it will go on indefinitely. I.e. in the status section it says "unpacking" and the green circle above is spinning, but nothing happens. The solution is always the same, click restart from the docker menu in unraid. Once I do this everything clears and works fine until it happens again. I'd say it is not 100% that this occurs, but pretty close. Is there a setting in NZBGet that needs to be changed? I was about to try SAB, but thought maybe there is an easy fix. If I go into the message section I see 100s of the same error message(s): "URL is not valid:" and then "Download my feed failed." These occur every 15 minutes. Thanks! Brian
March 29, 20197 yr 8 hours ago, BrianB said: The issue I'm having is that when NZBGet tries to unpack it will go on indefinitely. Current version has had the unpacking issue for some time. Solution a couple of pages back is to install previous version...
March 30, 20197 yr So, I went ahead and rolled back to v19, but now I can't get the WebUI to function. It just says "404 Not Found." For the heck of it I went up to v20 and same problem. What am I doing wrong? B.
April 7, 20197 yr On 3/29/2019 at 11:36 PM, BrianB said: So, I went ahead and rolled back to v19, but now I can't get the WebUI to function. It just says "404 Not Found." For the heck of it I went up to v20 and same problem. What am I doing wrong? B. Same happened to me. I just pulled the tag into a new container building it from the template on which i was using 20.0. Seems to be working OK for me now.
April 8, 20197 yr 5 hours ago, JDK said: Same happened to me. I just pulled the tag into a new container building it from the template on which i was using 20.0. Seems to be working OK for me now. I don't know what you mean or how to do that. I just went back to the current version and just restart NZBGet every day or two. Does anyone know if SAB has this problem? Any reason to stick with NZBGet?
April 13, 20197 yr On 4/7/2019 at 9:16 PM, BrianB said: I don't know what you mean or how to do that. I just went back to the current version and just restart NZBGet every day or two. Does anyone know if SAB has this problem? Any reason to stick with NZBGet? I just find NZBget the easiest to configure and use. I havent used SAB in years now, so maybe they improved on that factor since. Anyway, here are some steps you can try to help get NZBget going: 1. Go to your docker page and add a new container 2. From the template dropdown, select "binhex-nzbget", presuming you havent already deleted the template. Basically, this just restores all the settings you used last time, but is also the cause of you getting the 404 when checking out the 19.1 tag: you are most likely mixing the config data. 3. Make the changes to get the previous tag going - i used 19.1-1-02 (https://hub.docker.com/r/binhex/arch-nzbget/tags) Below is a screenshot of how i changed it. The most important part is the AppData Config Path setting, so make sure you change that form the template value. 4. Once you've started the container you will need to configure NZBGet again via its internal settings page (news server, paths, etc). This is because of the change in the appdata location, basically starting fresh. Hope this helps!
April 24, 20197 yr Yes, immensely. It's easy, but I would have never known how to do it without the simple instructions. Thanks much. I've been running it for a few days and haven't run into the unpacking queuing issue, so it seems all is well. Thanks again, Brian
May 4, 20197 yr On 4/13/2019 at 2:01 PM, JDK said: I just find NZBget the easiest to configure and use. I havent used SAB in years now, so maybe they improved on that factor since. Anyway, here are some steps you can try to help get NZBget going: 1. Go to your docker page and add a new container 2. From the template dropdown, select "binhex-nzbget", presuming you havent already deleted the template. Basically, this just restores all the settings you used last time, but is also the cause of you getting the 404 when checking out the 19.1 tag: you are most likely mixing the config data. 3. Make the changes to get the previous tag going - i used 19.1-1-02 (https://hub.docker.com/r/binhex/arch-nzbget/tags) Below is a screenshot of how i changed it. The most important part is the AppData Config Path setting, so make sure you change that form the template value. 4. Once you've started the container you will need to configure NZBGet again via its internal settings page (news server, paths, etc). This is because of the change in the appdata location, basically starting fresh. Hope this helps! Thanks for this, i am having unpacking issues also. Do i have to delete the old NZBget, before i use this method to get the old one?? Thanks
May 4, 20197 yr 4 hours ago, coldjim said: Thanks for this, i am having unpacking issues also. Do i have to delete the old NZBget, before i use this method to get the old one?? Thanks The instructions given insure that your old NZBget isn't touched. It creates a completely new one with a different name, different version, and a different appdata folder, as indicated by the highlights. Up to you whether or not you want to keep the old one around or not.
May 20, 20197 yr On 2/11/2019 at 3:30 PM, slbailey617 said: Just within the past day or two I can no longer connect to the web ui. I go to http://ipaddr:6789 and it just spins forever... This is still happening as of 5/20/2019. I have tried rolling back all the way to 19.1-1-02 and the same results. Here are the latest log files. I notice an issue with supervisord not being on pid 7 like it was previously: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-05-20 08:00:40.381403 [info] System information Linux b00c02037914 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux 2019-05-20 08:00:40.418214 [info] PUID defined as '99' 2019-05-20 08:00:40.692285 [info] PGID defined as '100' 2019-05-20 08:00:41.234005 [info] UMASK defined as '000' 2019-05-20 08:00:41.266205 [info] Setting permissions recursively on volume mappings... 2019-05-20 08:00:41.304443 [info] Starting Supervisor... 2019-05-20 08:00:41,489 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing 2019-05-20 08:00:41,489 INFO Set uid to user 0 succeeded 2019-05-20 08:00:41,492 INFO supervisord started with pid 6 2019-05-20 08:00:42,494 INFO spawned: 'nzbget' with pid 45 2019-05-20 08:00:42,494 INFO reaped unknown pid 7 2019-05-20 08:00:42,505 DEBG 'nzbget' stdout output: [info] NZBGet configuration does not exist, copying default configuration file to /config/... 2019-05-20 08:00:43,506 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Would appreciate some guidance on a solution.
May 21, 20197 yr Author 21 hours ago, slbailey617 said: This is still happening as of 5/20/2019. I have tried rolling back all the way to 19.1-1-02 and the same results. Here are the latest log files. I notice an issue with supervisord not being on pid 7 like it was previously: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-05-20 08:00:40.381403 [info] System information Linux b00c02037914 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux 2019-05-20 08:00:40.418214 [info] PUID defined as '99' 2019-05-20 08:00:40.692285 [info] PGID defined as '100' 2019-05-20 08:00:41.234005 [info] UMASK defined as '000' 2019-05-20 08:00:41.266205 [info] Setting permissions recursively on volume mappings... 2019-05-20 08:00:41.304443 [info] Starting Supervisor... 2019-05-20 08:00:41,489 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing 2019-05-20 08:00:41,489 INFO Set uid to user 0 succeeded 2019-05-20 08:00:41,492 INFO supervisord started with pid 6 2019-05-20 08:00:42,494 INFO spawned: 'nzbget' with pid 45 2019-05-20 08:00:42,494 INFO reaped unknown pid 7 2019-05-20 08:00:42,505 DEBG 'nzbget' stdout output: [info] NZBGet configuration does not exist, copying default configuration file to /config/... 2019-05-20 08:00:43,506 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Would appreciate some guidance on a solution. is the above the full log?, if not please post complete log, also i would try accessing the web ui from another device, such as a smart phone, this rules out the browser and os in one hit then, my guess is that its browser cookie or cache related.
May 23, 20197 yr Is there a way to have nzbget’s intermediate folder on an unassigned drive? Right now everything is located on my cache pool with all paths coming off the root directory; is it possible to relocate the InterDir to a separate disk? If I try to reassign the InterDir to /mnt/[UD]/intermediate it just creates a new path inside the root directory
May 24, 20197 yr 12 hours ago, the_names_james said: Is there a way to have nzbget’s intermediate folder on an unassigned drive? Right now everything is located on my cache pool with all paths coming off the root directory; is it possible to relocate the InterDir to a separate disk? If I try to reassign the InterDir to /mnt/[UD]/intermediate it just creates a new path inside the root directory Haven't tried it, but should be possible. You need to first make your UD folder visible to the docker... Edit the docker At the bottom, add another path Give the Container Path a value of something like /ud_inter (your choice) In the Host Path, navigate to /mnt/disks/...your unassigned inter folder.../ In the Access Mode select RW/Slave Add the new path Apply the changes to the Docker. It will restart and now be able to see the ud folder In NZBGet, settings, paths, set the Inter to /ud_inter (or whatever you set it above)
May 25, 20197 yr On 5/24/2019 at 8:57 AM, Cessquill said: Haven't tried it, but should be possible. You need to first make your UD folder visible to the docker... Edit the docker At the bottom, add another path Give the Container Path a value of something like /ud_inter (your choice) In the Host Path, navigate to /mnt/disks/...your unassigned inter folder.../ In the Access Mode select RW/Slave Add the new path Apply the changes to the Docker. It will restart and now be able to see the ud folder In NZBGet, settings, paths, set the Inter to /ud_inter (or whatever you set it above) Perfect, thank you
May 30, 20197 yr I've recently come across another issue; sometimes NZBget will download a file fully but gets stuck on the unpacking stage. This usually occurs after a file is added to an empty queue, and persists regardless of how many items are added to the queue (first item hangs at unpack, everything else awaits PP). Restarting the container fixes the issue and allows NZBget to pick up where it left off - as soon as the container is restarted it begins unpacking - however until it's restarted the unraid main page shows constant writes to the cache. This can go on for hours and the cache remains at an elevated temperature until I restart the container. Is there a setting I can adjust to minimise the chances of an unpacking freeze?
May 31, 20197 yr 5 hours ago, the_names_james said: Is there a setting I can adjust to minimise the chances of an unpacking freeze? Schedule this to run every hour or so in the user scripts plugin. #!/bin/bash docker restart binhex-nzbget
May 31, 20197 yr Author 15 hours ago, the_names_james said: I've recently come across another issue; sometimes NZBget will download a file fully but gets stuck on the unpacking stage. This usually occurs after a file is added to an empty queue, and persists regardless of how many items are added to the queue (first item hangs at unpack, everything else awaits PP). Restarting the container fixes the issue and allows NZBget to pick up where it left off - as soon as the container is restarted it begins unpacking - however until it's restarted the unraid main page shows constant writes to the cache. This can go on for hours and the cache remains at an elevated temperature until I restart the container. Is there a setting I can adjust to minimise the chances of an unpacking freeze? this is a long standing issue with unpacking with nzbget, it is particular to my docker image (LSIO seem unaffected) so im guessing its some incompatibility with the statically built unrar included with nzbget. i see im not completely alone here, with other people suffering crashes with the included unrar binary, see here:- https://forum.nzbget.net/viewtopic.php?f=3&t=3237 so with that in mind im going to try including a arch linux build of unrar and symlink it in and see if that fixes it, are you up for testing this, as i currently do not have a usenet subscription so kinda need some help to find out if this resolves it.
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.