Skip to content

Instantly share code, notes, and snippets.

@jhelmink

jhelmink/Proxomox - NUT Client - Synology NAS.md

Forked from pae-id/Proxomox - NUT Client.md
Last active September 25, 2025 21:44
Show Gist options
  • Save jhelmink/ba54e11e6a1b9f448a4a9a5c4cb45b89 to your computer and use it in GitHub Desktop.
Save jhelmink/ba54e11e6a1b9f448a4a9a5c4cb45b89 to your computer and use it in GitHub Desktop.
Download ZIP
Proxomox - NUT Client.md
Raw
Proxomox - NUT Client - Synology NAS.md

Configuring Proxmox VE node as client for remote NUT server running on Synology NAS

Network UPS Tools User Manual

  • Use Shell on Proxmox Node to install NUT Client
apt-get install nut-client
  • Edit /etc/nut/nut.conf using vi
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.conf using vi
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 [email protected]

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 [email protected] 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 [email protected]

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
@ylnest2018
Copy link

thanks for this been looking for an easy way to do this.

Couple questions:

  1. Will the upsmon autostart upon reboot or do you need to alter another file to do this?
  2. How do you specify the time after a power outage where a shutdown will be initiated? either by time or power percentage?

@jhelmink
Copy link
Author

jhelmink commented Dec 8, 2024

  1. Will the upsmon autostart upon reboot or do you need to alter another file to do this?

Nah you'll need to use systemctl to enable the services to automatically restart;

sudo systemctl enable nut-client
sudo systemctl enable nut-monitor
  1. How do you specify the time after a power outage where a shutdown will be initiated? either by time or power percentage?

You specify this on your NAS (as that is what is connected to the UPS, and publishes the status to NUT clients/slaves)

Control Panel -> Hardware and Power -> UPS

There are options for time or low battery.

@ylnest2018
Copy link

ah thats awesome! thank you for that been looking for a whole day on how to do this and stumbled across this page

@davoper
Copy link

davoper commented Jan 2, 2025

Instead of calling upsmon start after configuration it might be better to start services right away:

sudo systemctl enable nut-client
sudo systemctl enable nut-monitor

sudo systemctl start nut-client
sudo systemctl start nut-monitor

systemctl status nut-client
systemctl status nut-monitor

Also connect to NUT server and check that clients are registering as connected
upsc -c ups

@jhelmink
Copy link
Author

jhelmink commented Jan 2, 2025

Instead of calling upsmon start after configuration it might be better to start services right away:

sudo systemctl enable nut-client
sudo systemctl enable nut-monitor

sudo systemctl start nut-client
sudo systemctl start nut-monitor

systemctl status nut-client
systemctl status nut-monitor

Also connect to NUT server and check that clients are registering as connected upsc -c ups

Nice, I've amended this now.

@Pipitapi
Copy link

Pipitapi commented Feb 11, 2025 •
edited
Loading

I did it all step by step!
But it doesn't work. It shows the data.

Felvétel03
Felvétel02
Felvétel01

@BhSimon
Copy link

BhSimon commented Sep 9, 2025 •
edited
Loading

Warning. This guide does not work with Proxmox 9, as written. The end result of upsc -c ups is Error: Connection failure: Connection refused.

I have not been able to figure out how to resolve that problem, but certainly this guide should not be used in Proxmox 9 without further testing.

@jhelmink
Copy link
Author

I did it all step by step!
But it doesn't work. It shows the data.

You're logged in as root, so you don't need the "sudo" part of the commands (you can see that all your commands failed with command not found)

@jhelmink
Copy link
Author

Warning. This guide does not work with Proxmox 9, as written. The end result of upsc -c ups is Error: Connection failure: Connection refused.

I have not been able to figure out how to resolve that problem, but certainly this guide should not be used in Proxmox 9 without further testing.

Connection refused might mean that your Proxmox server is just unable to connect with your NAS on your network, you could try to ping the NAS from Proxmox to ensure they can see each other on the network.

@BhSimon
Copy link

BhSimon commented Sep 10, 2025 •
edited
Loading

Connection refused might mean that your Proxmox server is just unable to connect with your NAS on your network, you could try to ping the NAS from Proxmox to ensure they can see each other on the network.

They can. If I do upsc [email protected], I get a response. I feel like I am missing something obvious.

@webysther
Copy link

webysther commented Sep 24, 2025 •
edited
Loading

There some possible optimizations in your script, this is mine I use for years:

# install only the client
apt install nut-client

# enable client mode
sed -i 's/^MODE=none$/MODE=netclient/' /etc/nut/nut.conf

echo "RUN_AS_USER root" | tee -a /etc/nut/upsmon.conf

# change the IP of your NAS (REMEMBER TO ALLOW THE PROXMOX ON SYNOLOGY FIREWALL AND UPS SERVER)
echo "MONITOR ups@<IP>:3493 1 monuser secret slave" | tee -a /etc/nut/upsmon.conf

# BONUS: Disable broadcast and keep only the syslog
echo "NOTIFYFLAG ONLINE SYSLOG" | tee -a /etc/nut/upsmon.conf
echo "NOTIFYFLAG ONBATT SYSLOG" | tee -a /etc/nut/upsmon.conf
echo "NOTIFYFLAG LOWBATT SYSLOG" | tee -a /etc/nut/upsmon.conf

systemctl restart nut-client
systemctl status nut-client
● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
     Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-09-24 09:40:34 CEST; 5s ago
   Main PID: 124400 (upsmon)
      Tasks: 2 (limit: 76809)
     Memory: 852.0K
        CPU: 3ms

UPS Server

image

Synology Firewall

image

@dbsanders
Copy link

Just a couple minor things - I just set this up today using your info, thanks!

  1. All you need to install is the nut-client package, not all of 'nut'. apt install nut-client.

  2. You say: <system> is [email protected]
    This actually needs to be ups@your.nas.ip.address - That's the name Synology NUT gives to your UPS: 'ups'.

  3. The nut-monitor and nut-client services are the same, one is a link to the other. You can just systemctl enable/start nut-monitor, no need to operate on both.

lrwxrwxrwx 1 root root  19 Jan 25  2023 nut-client.service -> nut-monitor.service
-rw-r--r-- 1 root root 961 Jan 25  2023 nut-monitor.service

@BhSimon
Copy link

BhSimon commented Sep 25, 2025

Okay, update. As noted about myself: "I feel like I am missing something obvious." I was.

The final command, upsc -c ups should be run on the server (such as Synology NAS). [facepalm] When you do this, you will see the IP addresses of the Proxmox nodes you have set up.

This means that I can confirm that this walkthrough works on Proxmox 9. Apologies for my misunderstanding, and thank you, @jhelmink, for this useful guide.

@jhelmink
Copy link
Author

Just a couple minor things

Thanks for the feedback, definitely simplifies things, I've made some updates as suggested.

Okay, update. As noted about myself: "I feel like I am missing something obvious." I was.

Glad you were able to get it sorted, I've made a note to make it clearer for the next person.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment