NZBGet 9.0/10.0 discussion

[hugbug]

I see the questions about NZBGet 9.0 in different threads.
It make sense to have a separate topic for NZBGet 9.0.

The main feature of 9.0 is the all new web-interface.



For more screenshots and description of the new web-interface see page Web-Interface on NZBGet web-site.

For full list of changes see announcement nzbget 9.0-testing-r497.

---

How to install the newest version of NZBGet on NMT? The easiest way is of course to use CSI but you can also install manually.

Installing using CSI-package

1. Download CSI-package from this link;
2. Load CSI, go to File -> Install from file -> Select the downloaded zip-file file, install;
3. Using CSI, restart NZBGet.
4. Your new NZBGet URL will be http://NMTIP:6789 (default username/pass nzbget/tegbzn6789 )

The package is made by forum member jhmiller and hosted by NaaN. The instructions above are written by moddigi. Thanks to all guys!

How to install the newest version manually without CSI.

The NZBGet Download Page provides binaries for NMT-100 and NMT-200 series (should also work on 300 series).

1. Download the binary archive for NMT100 or NMT200;
2. Unpack the archive somewhere on NMT drive;
3. Stop NZBGet;
4. Replace your existing binary nzbget with the new one from the unpacked archive (it's under /usr/local/bin in the archive);
5. Add new option WebDir with the path to unpacked folder /usr/local/shared/nzbget/webui (replace the path with a correct one);
6. Check the option ServerIP (or ControlIP, see below). It shouldn't be set to 127.0.0.1 or localhost. Set it to 0.0.0.0 or the real IP-Address of NMT (something like 192.168.1.1);
7. Start NZBGet.

Now you should be able to connect to the new web-interface via http://ip-of-nmt:ServerPort/ where ServerPort is the value of option ServerPort (or ControlPort, see below) in config file (not the port used in the old web-interface!). For authorization use username nzbget and the password as defined in the option ServerPassword (or ControlPassword, see below) in the config file.

Note regarding options ServerIP, ServerPort and ServerPassword: in NZBGet-9.0-tesing-r477 these options were renamed to ControlIP, ControlPort and ControlPassword. They were renamed because I saw the users confuse them with options ServerX.Host, ServerX.Port and ServerX.Password. The old options names are still accepted by the program.

[zurie]

I appreciate you trying to help, but your tutorial does not work for me. alot of the stuff you are telling us to do is wrong. there is nothing about permissions of files, nothing about which config to edit, and you openly admit you haven't done this on a NMT... it would be great if someone could post a valid tutorial on how to get this working 100% on the NMT...

looks like .8 is calling my name because .9 is not ready for prime time.

[hugbug]

(10-07-2012 04:58 AM)zurie Wrote:  alot of the stuff you are telling us to do is wrong.

Could you be more specific? These instructions were already posted in another thread and do worked for at least one forum member.

For me it looks like you are just too lazy . Nothing bad about wanting a one-click-install but this is not what the instructions were about.

Taking into account jhmiller has given up his efforts regarding CSI it may take a while until a CSI package is available - weeks, months, who knows?

[jhmiller]

(10-07-2012 04:58 AM)zurie Wrote:  I appreciate you trying to help, but your tutorial does not work for me. alot of the stuff you are telling us to do is wrong. there is nothing about permissions of files, nothing about which config to edit, and you openly admit you haven't done this on a NMT... it would be great if someone could post a valid tutorial on how to get this working 100% on the NMT...

looks like .8 is calling my name because .9 is not ready for prime time.

I think the only thing missing from his instructions is to have a CSI version installed first.
I did have a CSI version of nzbget 0.9.0 that was made using basicly the same instructions above(was posted in the nzbget thread), so i can confirm they do work.

[hugbug]

(10-07-2012 11:47 AM)jhmiller Wrote:  I think the only thing missing from his instructions is to have a CSI version installed first.

This should work even with the stock version. It could be more difficult to replace the binary because as far as I can remember (I have used NMT for the last time about 2 years ago) the nmt-apps partition is not exposed via samba/ftp and you have to use terminal.

[jhmiller]

(10-07-2012 12:00 PM)hugbug Wrote:  

(10-07-2012 11:47 AM)jhmiller Wrote:  I think the only thing missing from his instructions is to have a CSI version installed first.

This should work even with the stock version. It could be more difficult to replace the binary because as far as I can remember (I have used NMT for the last time about 2 years ago) the nmt-apps partition is not exposed via samba/ftp and you have to use terminal.

Thats is what i was refering to. The average user would not know how to replace the system nzbget binary.

[moddigi]

Just tried this, working on A200.

New web interface is much nicer than old, thanks hugbug!

[edit] I installed this via editing the old 0.8.0 CSI file that JHMiller created... If he allows it, I'll post an edited 0.9 CSI file, otherwise you'll just have to manually follow hugbugs instructions (which also work fine - however if you need help following it just ask!)

[hugbug]

You already have the permission from the license terms. It's GPL software. You may change and redistribute it. The CSI package has the same license of course.

BTW, it's 9.0, not 0.9.0.

Before you make the package please test if the settings page works. There is a bug causing the settings page not to load if the post-processing config template file is not present in webui-folder (see this topic on NZBGet forum).

[moddigi]

Settings page works.

[moddigi]

Okay, after lots of playing around I now know why a new install from csi zip wouldn't work... it was using the new config file where path settings etc weren't edited for the NMT. It took me ages to figure that one out, lol. Upgrading from an old CSI install worked because it used the old settings (plus the webui and 0.0.0.0 edits of course).

Anyway, new config file edited with appropriate settings, all installed and runs fresh from either an upgrade or new install. However, upon startup on the webUI messages I get

Code:

nzbget.conf(106): Invalid value for option "OutputMode": program was compiled without curses-support

Is this an issue, hugbug?

[meskaya]

I changed it to loggable (I had this in my old config)
In Display section I set this:
OutputMode=loggable

I thing it's important to change it as it pauses all server activities:

Sun Oct 7 14:19:32 2012 ERROR nzbget.conf(982): Invalid value for option "OutputMode": program was compiled without curses-support
Sun Oct 7 14:19:32 2012 INFO Pausing all activities due to errors in configuration

[hugbug]

(10-07-2012 05:27 PM)moddigi Wrote:  

Code:

nzbget.conf(106): Invalid value for option "OutputMode": program was compiled without curses-support

Is this an issue, hugbug?

Set the option OutputMode=loggable. The nurses interface is interested only for users using terminal and therefore is not relevant for NMT users.

---

(10-07-2012 05:42 PM)moddigi Wrote:  

(10-06-2012 09:02 PM)hugbug Wrote:  The old web-interface under the old address should still work too.

The old URL doesn't work, when I try http://NMTIP:9999/NZBget_web we get

I'd say if the old web-interface was working before, it should work after you replace the old binary with the new one.

Do you include the old web-interface (NZBGetWeb) within your package? I wouldn't do that. The new web-interface has almost every feature of the old one.

(10-07-2012 05:42 PM)moddigi Wrote:  I'm guessing this error message shown in the new UI is related:

Code:

Web-Server: 404 Not Found, Resource: /.conf

Do you get this log-message when you try to access the old web-interface?

One more thing, can you please include the fixed config.js as described here. You can call it r478 then.

[moddigi]

No, from a new install I didn;t include NZBGetWeb, I'm not even sure where that directory would be.

Nope, that log appears every 10 minutes or so, regardless of any attempt to access the old web interface URL. Shall include that config.js file.

[hugbug]

(10-07-2012 07:31 PM)moddigi Wrote:  Shall include that config.js file.

You can call it r478 then.

[moddigi]

(10-07-2012 07:14 PM)hugbug Wrote:  Do you get this log-message when you try to access the old web-interface?

Just seen that it happens a couple of seconds every time after I manually refresh the (new) web interface.