Hi!
I'm tresting NZBGet and although it looks very promising, it's full of little (and big) bugs.
1) It crashes randomly - without any error message. It's simply gone from one moment to the next. Seems to happen while downloading (probably with direct unpacking - hard to tell...)
2) When double-clicking the NZBGet icon on the desktop with the program already running, it displays the dialog asking me what to do. When I select "Show Web interface", nothing happens. Works fine if I open Chrome and enter "127.0.0.1:6789" manually.
3) When opening the web interface via the tray icon, Chrome opens and displays "Oops, something went wrong...". Works fine if I open Chrome and enter "127.0.0.1:6789" manually.
4) Downloaded items that seem to have been postprocessed and unpacked correctly, sometimes still stay in the "Downloads" list with the status of "Postprocessing", although nothing is done with them.
5) The "intermediate" directory collects orphaned jobs - some have completed successfully long time ago, but there is still a folder with some files in it.
Also, it lacks some very important features:
1) Importing nzbs named "filename{{password}}.nzb" should be supported natively! This format is used so widely that it's a shame to have to install python, install strange half-working scripts, etc. This is so easy to implement - and impossible to understand why it is not supported directly by NZBGet...
2) The free space remaining on the download drive should be displayed directly on the web interface, not only hidden in a sub dialog. SHould be visible immediately if the queue can be completed or not.
3) The "Est Time" should not display the time needed for just this one download, but the total time needed until this item will be completed (including all those before it). Would make much more sense, because what's the point of knowing that a download will take 2 minutes, if there are 200 queue items before it and another 100 after it? Should I manually add all download time to know when I can expect a single one to be finished? Not very logical...
I don't see any of these issues with Sabnzbd on the same system (Windows 10 x64, 6 GB RAM, 500 GB SSD). Only thing that seems to work better in NZBGet is sending a download from another computer with NZBDonkey - this sometimes fails with Sabnzbd and that's why I was looking for an alternative. Unfortunately, although NZBGet looks very promising, it's not quite there yet...
Regards!