After installation, the package may be configured at Services > NUT.
The following is an example of the NUT status screen:
The package does not have a lot of input validation in the GUI. If NUT will not start after configuration, check the System log (Status > System Logs) for log entries from nut. The culprit is likely explained there, such as selecting a cable for a driver type that does not need (nor permit) the cable selection.
If the system log doesn’t offer adequate information, such as simply logging “nut: Service failed to start: check configuration”, log in via SSH and choose option 8, then run the following command:
Configuration errors will be displayed in the output if any are found.