Page 1 of 1

Password lost when retrying

Posted: March 11th, 2017, 2:04 am
by FCrane
Hi!

Whenever something goes wrong when unpacking an archive (e.g. disk full, etc) and I click "Retry", the password field is empty and unpacking fails due to the lacking password. Seems that SABNZBD+ forgets the initially password when it can't complete a queue item. Clicking the failed item in the queue doesn't help either, because the information displayed does not contain the password anymore.

That's very inconvenient, because I need to search for the password again on the internet.

Would be great if SABNZBD+ simply could remember the password all the time, so that I can retry any action without losing the password.

Thanks!

Re: Password lost when retrying

Posted: March 11th, 2017, 4:17 am
by safihre
Will add it to the feature request list!

Re: Password lost when retrying

Posted: March 18th, 2017, 8:29 am
by airguy
In the meantime you could try putting the password in the NZB filename using brackets like Something{{password}}.nzb. Then, if you go to your nzb backup folder, the password will be the backed up NZB file. Just cut and paste from that.

I'll go further on the post processing problems. Once post processing hits an error about a password, I usually just do a manual extract with WinRar instead of using the retry option from the history page. Sabnzbd will tell me archive requires a password, then I hit retry with the password, then it tells me Rar files failed to verify (because they already were verified previously so the par files are all gone from the folder). I try again with the password, then it goes out and downloads all the par files again to re-verifiy the files again! (I have Sabnzbd set to download all par files initially and verify). So I just use winrar manually, enter pw and save time. Would be great if Sabnzbd would be intelligent enough to pick up where it failed on the password. You should be able to re-enter the pw and resume unpacking, moving, etc, automatically.

Re: Password lost when retrying

Posted: March 18th, 2017, 9:42 am
by safihre
Just implemented it for 2.0.0
But indeed, need to see if we can be smarter and skip the whole verification again. I also noticed that when testing this change.
Guess we dev's don't usually have passworded jobs!