May 12, 20242 yr It looks like development is now proceeding at https://github.com/nzbgetcom/nzbget and the project is active. It would help if lsio would point the image at this new fork, but I don't know if it meets their requirements yet.
May 23, 20242 yr Glad to see someone getting traction moving forward with reviving nzbget. Used it for a few years, but ended up switching to sabnzbd once nzbget lost its pulse. Looking forward to hearing a review or two on how it works, once we get some installs on Unraid.
October 20, 20241 yr Hello I am new to Unraid and have been farting around for days but cannot get my Radarr/NZBGet working. I would appreciate it immensely if someone could explain to me in plain English, how I get rid of these errors? Does it have anything to do with this? or maybe on of these? Thanks legends... EDIT: While I am at it, I get this in Radarr but not in Sonarr..? EDIT2:Now I am getting it in Sonarr also. I don't get what it means "inside the container"... Edited October 20, 20241 yr by Exsol Added another question.
March 8, 20251 yr I'm getting error messages about not NzbGet not resolving my usenet provider. Could not resolve hostname I see some three year old posts about this same problem but I don't see any resolution. This has started happening over the past couple of weeks. Downloads work and then suddenly stop and the log is just filled with thousands of these error messages. If I restart the docker the downloads start again (for awhile), and then the error messages start again. Any thoughts or suggests?
May 18, 20251 yr I get this error intermittently from every container that uses NZBGet. "Unable to communicate with NZBGet. Http request timed out." I get one of those per minute, until it resolves itself with "The following is now resolved: Unable to communicate with NZBGet. Http request timed out." All the containers are running on the same Docker network. Every time I look at each container's config for NZBGet it is correct and when I test it, it always passes. Since they are all running on the same Docker network, each config uses the containers name to resolve the IP. This issue doesn't happen all the time. It may go weeks or months and not do it. But when it happens, it's constantly losing connection and then reconnecting, rinse and repeat. The only reason I posted in here is NZBGet is the only container that this issue has in common. Anyone else have anything like this happen? Thanks!
May 30, 20251 yr Im trying to switch from binhex to your docker as the binhex unpack process continually fails every couple of hours (known issue with binhex NzbGet). I'm having an issue where by Sonarr cannot rename/move the file to media following download with linuxservers NzbGet. binhex NzbGet is working fine with Sonarr, is im unsure how mappings could be an issue.Im unsure if this is path mapping or permissions issue, but im really stumped. Would appreciate some advice! refer images for set up of both dockers, including path mappings and Sonarr errors.Binhex working mappingLinuxserver set upSonarr errors Edited May 30, 20251 yr by Garthy
February 13Feb 13 anyone updated this recently?i have and it has developed quirks.if you do a new permissions on a share. it now pauses NZBGET downloadsall the history it had is gone and now clears daily. all i've done is updated the container when it suddenly had an update available.
February 13Feb 13 12 minutes ago, Jammy B said:new permissions on a share.You mustn't do New Permissions on appdata.And you shouldn't need to do New Permissions on the share NZBGet is downloading to.
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.