Support Forum

Sure, no problem, here's the link . But it probably won't help much, because the problem doesn't seem to be reproducible. Just for kicks, I re-downloaded it again just now, and it worked fine on the first try this time. I also noticed that I had "Action when encrypted RAR is downloaded: Pause&q...

Yes, you're right, now I see what you mean: in lines 246 - 250 from the first log it collects a total of 8 passwords (1 "user supplied" + 2 "from nzb metadata" + 5 "from passwords.ini", and then later on in line 267 it builds what looks like a 100% correct commandline f...

Oooh, I think I misread your reply ... sorry! So you're saying that there's an indication in the logs somewhere that also the password from the NZB itself failed, ie. the one that's encoded within the curly brackets {{...}} in the filename? I guess I must have missed that one. I'm going back to re-r...

Did you read the log yourselves? What did you see? Reason: at passwords, I'm just a user, and in your first log, I see a few "Trying password" (2 from the NZB, 4 or so from password.ini), and that fails. I see no password trying in the other log files ... Ummm ... why, yes, of course I di...

Okay, well that didn't take long, did it? ;) I would have posted the logs here, but as it seems I can't because of: The submitted form was invalid. Try submitting again. Your message contains 99904 characters. The maximum number of allowed characters is 20000. So instead I'll put it up on pastebin.c...

Okay, I'll do that and wait for the next "ENCRYPTED" pause to happen. Thanks!

I've noticed that with 3.1.0 it happens more often again that downloads are stopped/paused with "ENCRYPTED" when they are in fact not. Well, they actually are, of course, but the proper password is already supplied and known to SABnzbd. When this happens, all I have to do is to klick the &...

@sander: I don't think that this would make any sense, as the problem doesn't seem to be reproducible with specific NZBs. I just retried downloading my three examples for kicks, and this time *all* of them worked fine on the first try. So I guess you could basically try to test it with *any* passwor...

That's because I still have the debugging statements active that you asked me to add for hunting down the "additional space at the beginning of the password" phantom bug.

Same here, happens randomly (?) every now and then ... while trying to figure it out, I stumbled across these log entries before the bogus encryption warning: WARNING: You need to start extraction from a previous volume to unpack Awake.S01E13.German.DL.Dubbed.WEBRiP.x264-4SJ.mkv WARNING: You need to...

Yup - download tarball, unpack, 'python setup.py build', 'python setup.py install'. I guess I'll have (to have) a look at installing via pip sooner or later.

Aaaaaaaaaaaaaaah - ha! I think I got it! 8) "If everything else fails, read the docs" ... only by very lucky chance I stumbled across a tiny file called /usr/local/lib/python2.7/site-packages/cryptography-1.7.1-py2.7.egg-info/requires.txt, which says: idna>=2.0 pyasn1>=0.1.8 six>=1.4.1 set...

No, the reinstall did not help, unfortunately, just as I thought. Yes, the Python version is the same for everything. Main stuff directly from Slackware, the rest (SAB, cryptography, Cheetah, NumPy, ...) installed in /usr/local. Strange.

Ah, thanks! :-) Okay, so here's the output: 2017-01-21 11:35:51,845::ERROR::[assembler:361] Error Traceback (most recent call last): File "/usr/local/stow/SABnzbd-1.2.0/lib/python2.7/site-packages/SABnzbd/sabnzbd/assembler.py", line 347, in check_encrypted_and_unwanted_files zf.setpassword...

When I feed an NZB to SABnzbd in the filename{{password}}.nzb format, the password suddenly contains an additional space in the beginning (ie. the password field in the web GUI reads " password"), automatic unpacking fails, and the download gets paused. So I have to klick into the password...