*EDIT*

Wow, I feel really dumb. It was a permissions issue, I created the folder in windows so it set me as the owner. Also, Why it stopped working at the beginning of the year? I let my VPN subscription lapse  I am running NZBGet through delugeVPN. I feel so dumb, but maybe someone else will be helped by my mistakes!

 

Hello, close to the beginning of this year. Something happened wit my NZBGet setup. I'm getting errors saying that NZBGet can't create files. I think it's probably a permissions or paths issue. Not sure that the problem is exactly though. I've uploaded my diagnostics. Thanks in advance!

tower-diagnostics-20250411-1749.zip

 

 

Edited April 12, 20251 yr by PrisonMike
facepalm -_-

Hi all,

New to NZBGet.  Have done the following:

1. Created a separate share called nzbdownloads.

2. Pointed the /data in the container config prior to installing to this.

3. Installed the binhex-nzbget container.

4. Configured the container/program leaving most as defaults with the exception of the news server etc.

5. Set the categories as: radarr, tv-sonarr and readarr to match the programs I use

6. Have setup an indexer in Prowlarr

7. Gone to add the download client to radarr, sonarr and readarr ensure the categories match and tested the connections, they get the green tick.

8. I then get the notifcation/error attached in all 3 - radarr, sonarr and readarr.

 

I have tried to understand on the forums what this means and how to fix it but im getting more and more confused.

 

FYI all the radarr, sonarr and readarr are binhex releases.

 

For torrent I use the binhex-qbittorrent-vpn

 

If someone could explain step by step what this means and how to fix it I would really appreciate the help.

 

Thanks,

Dwarfboysim

 

On 4/27/2017 at 11:32 AM, spall said:

@binhex

 

Installed latest, getting constant loop of this in messages:
 

errorThu Apr 27 2017 12:24:17Could not select cipher for TLS
errorThu Apr 27 2017 12:24:17Could not select cipher for TLS: error:1410F0B9:SSL routines:SSL_set_cipher_list:no cipher match
errorThu Apr 27 2017 12:24:17Could not select cipher for TLS
errorThu Apr 27 2017 12:24:17Could not select cipher for TLS: error:1410F0B9:SSL routines:SSL_set_cipher_list:no cipher match

Here's the content of the log:

2017-04-27 12:23:38.031314 [info] Host is running unRAID2017-04-27 12:23:38.049118 [info] System information Linux df54658645ad 4.9.19-unRAID #1 SMP PREEMPT Thu Mar 30 08:32:28 PDT 2017 x86_64 GNU/Linux2017-04-27 12:23:38.069483 [info] PUID defined as '99'2017-04-27 12:23:38.090782 [info] PGID defined as '100'2017-04-27 12:23:38.121204 [warn] UMASK not defined (via -e UMASK), defaulting to '000'2017-04-27 12:23:38.140821 [info] Permissions already set for volume mappings2017-04-27 12:23:38,314 CRIT Set uid to user 02017-04-27 12:23:38,314 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing2017-04-27 12:23:38,315 INFO supervisord started with pid 72017-04-27 12:23:39,317 INFO spawned: 'nzbget' with pid 402017-04-27 12:23:39,322 DEBG 'nzbget' stdout output:
[info] NZBGet configuration file exists

2017-04-27 12:23:40,323 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-04-27 12:24:21,234 WARN received SIGTERM indicating exit request2017-04-27 12:24:21,234 DEBG killing nzbget (pid 40) with signal SIGTERM2017-04-27 12:24:21,234 INFO waiting for nzbget to die2017-04-27 12:24:21,234 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47910989772632 for <Subprocess at 47910989884664 with name nzbget in state STOPPING> (stdout)>2017-04-27 12:24:21,235 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47911003475264 for <Subprocess at 47910989884664 with name nzbget in state STOPPING> (stderr)>2017-04-27 12:24:21,235 INFO stopped: nzbget (terminated by SIGTERM)2017-04-27 12:24:21,235 DEBG received SIGCLD indicating a child quit

 

Reverting back to binhex/arch-nzbget:18.0-1-01 restores normal functionality.

 

Thanks for all your work on this!

I'm having a simliar issue as this. Here's part of the log. Anybody have any solutions? If I restart the docker it just does this again after a day or so.

2025-08-03 23:13:11,253 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2025-08-04 19:40:29,432 WARN received SIGTERM indicating exit request

2025-08-04 19:40:29,432 DEBG killing nzbget (pid 53) with signal SIGTERM

2025-08-04 19:40:29,432 INFO waiting for nzbget to die

2025-08-04 19:40:29,433 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23311664241296 for <Subprocess at 23311665603520 with name nzbget in state STOPPING> (stdout)>

2025-08-04 19:40:29,433 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23311663913936 for <Subprocess at 23311665603520 with name nzbget in state STOPPING> (stderr)>

2025-08-04 19:40:29,433 WARN stopped: nzbget (exit status 143)

2025-08-04 19:40:29,433 DEBG received SIGCHLD indicating a child quit

5 hours ago, jdsutt said:

I'm having a simliar issue as this. Here's part of the log. Anybody have any solutions? If I restart the docker it just does this again after a day or so.

2025-08-03 23:13:11,253 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2025-08-04 19:40:29,432 WARN received SIGTERM indicating exit request

2025-08-04 19:40:29,432 DEBG killing nzbget (pid 53) with signal SIGTERM

2025-08-04 19:40:29,432 INFO waiting for nzbget to die

2025-08-04 19:40:29,433 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23311664241296 for <Subprocess at 23311665603520 with name nzbget in state STOPPING> (stdout)>

2025-08-04 19:40:29,433 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23311663913936 for <Subprocess at 23311665603520 with name nzbget in state STOPPING> (stderr)>

2025-08-04 19:40:29,433 WARN stopped: nzbget (exit status 143)

2025-08-04 19:40:29,433 DEBG received SIGCHLD indicating a child quit

can you try pulling the latest image just built.

Hello,

I'm having an issue with binhex-nzbget when I updated from 7.1.4 to 7.2. Once I updated nzbget could not write to queue/tmp/nzb directories, but if I restart unraid, it will regain read/write for a while then it looses access. When I down grade to 7.1.4 no issues with nzbget at all, I figure it must be a permissions issue but I can't find it and everything looks good. I've tried to delete and recreate those three directories and that does not work either. It is only the nzbget container that is giving me this issue.

Any help would be appreciated.

4 minutes ago, PatrickS said:

Hello,

I'm having an issue with binhex-nzbget when I updated from 7.1.4 to 7.2. Once I updated nzbget could not write to queue/tmp/nzb directories, but if I restart unraid, it will regain read/write for a while then it looses access. When I down grade to 7.1.4 no issues with nzbget at all, I figure it must be a permissions issue but I can't find it and everything looks good. I've tried to delete and recreate those three directories and that does not work either. It is only the nzbget container that is giving me this issue.

Any help would be appreciated.

this maybe totally unrelated, but thought i would link you to it as it sounds similar:- https://forums.unraid.net/bug-reports/stable-releases/720-array-write-issues-r4165/

Looks like this fixed the issue.

On the latest version 26.1-01, I'm getting an error 'Could not load certificate store location from /usr/local/share/nzbget/cacert.pem.' I verified through the console that the location with the file exists. Currently, I pinned the container to version 26.0-01 until I can figure out what's going on.

4 hours ago, akai008 said:

On the latest version 26.1-01, I'm getting an error 'Could not load certificate store location from /usr/local/share/nzbget/cacert.pem.' I verified through the console that the location with the file exists. Currently, I pinned the container to version 26.0-01 until I can figure out what's going on.

Ive just done a clean install with the latest and i see no sign of an error in the web ui or the log, where are you seeing this error?.

Spotted it in messages in the web ui, i've resolved the issue, please pull down at your convienience.

Had the same issue. Did a force update on the docker and it solved the issue with what i'm guessing is an outdated certificate.

12 minutes ago, sverker670 said:

Had the same issue. Did a force update on the docker and it solved the issue with what i'm guessing is an outdated certificate.

missing root CA certs actually, nzbget used to maintain a root ca cert file, looks like that is missing now so switched over to another source.

2 hours ago, binhex said:

Ive just done a clean install with the latest and i see no sign of an error in the web ui or the log, where are you seeing this error?.

Spotted it in messages in the web ui, i've resolved the issue, please pull down at your convienience.

Thanks for the fix. Sorry, I should’ve specified it was from in the Web UI.