- Use Shell on Proxmox Node to install NUT Client
apt-get install nut-client
- Edit
/etc/nut/nut.confusingvi
vi /etc/nut/nut.conf
Modify the last line
x to delete existing characters
i to insert characters. ESC to go back to command mode
MODE=netclient
:q! to quit without saving if you fuck it up
:wq to save and quit when you get it right
- Edit
/etc/nut/upsmon.confusingvi
vi /etc/nut/upsmon.conf
There won't be an existing line, look for the other MONITOR example comments and add after that.
MONITOR <system> <powervalue> <username> <password> ("master"|"slave")
<system> is ups@your.nas.ip.address
monuser and secret are the default <username> <password> for a Synology NAS
<powervalue> is going to be 1 unless you have multiple UPS's
Since you're monitoring your NAS you are in slave mode
MONITOR ups@192.168.1.5 1 monuser secret slave
- Enable monitoring services to start up with the machine:
sudo systemctl enable nut-monitor
- Start monitoring:
sudo systemctl start nut-monitor
- Verify monitoring:
systemctl status nut-client
systemctl status nut-monitor
- To check UPS status from your Proxmox Server
upsc <name>@<address>for the remote UPS
upsc ups@192.168.1.5
This will return a bunch of your UPS info if everything is working correctly
- Confirm clients are connecting back on the Synology NAS:
upsc -c ups
can confirm working in prox9.2
but for this synology I had to make a change on the monuser.
SSH into synology and edit.
change [monuser]'s role from master to slave in upsd.users — that account is what your remote nodes log in as, and slave/secondary is the correct role for a remote monitor-only client. The NAS itself doesn't need a master upsmon client in this file at all; Synology's own DSM handles its own local UPS-driven shutdown separately from the upsmon client role.
vi /etc/ups/upsd.users
[monuser]
password = secret
upsmon slave
Then on nodes:
MONITOR ups@192.168.3.11 1 monuser secret slave
**** DONT BE CONFUSED AND TRY YOUR NAS CREDENTIALS HERE. Creds are monuser secret****