On this page
- Master, slave and NUT in plain words
- The three UPS modes in QTS
- Power off or auto-protection: what happens when power returns
- Worked example: one UPS, two QNAPs and a Linux PC
- Sharing a QNAP UPS with other QNAP units
- Reading a QNAP UPS from NUT clients
- A QNAP as the client of another NUT server
- QNAP and Synology on one UPS
- The admin / 123456 default is weak
- What this page does not cover
- Frequently asked questions
Master, slave and NUT in plain words
A network UPS master is the NAS that has the UPS data cable plugged in. It reads the battery state and passes it on over the network. A network UPS slave is a NAS with no cable that follows the master's reports and shuts itself down. QNAP still uses the words master and slave in QTS, so this page does too.
NUT (Network UPS Tools) is the free software most NAS and Linux systems use for this job. Under the hood, a QNAP master runs a NUT server that other machines reach on TCP port 3493. That is why a Linux PC or Home Assistant can follow a QNAP, not just another QNAP. Our NUT setup guide explains the parts in depth.
The three UPS modes in QTS
In QTS 5.1, the page is at Control Panel > System > External Device > UPS. You pick one mode.
| Mode | Use when | What you enter |
|---|---|---|
| USB connection | The UPS cable plugs into this NAS | Shutdown choice and delay; optionally, network UPS master and a list of IPs |
| SNMP connection | The UPS has its own network card on the same network | The UPS IP address, the SNMP community (usually public), shutdown choice and delay |
| Network UPS slave | Another device owns the UPS and shares it | The IP address of the UPS server, shutdown choice and delay |
The master option only appears in USB mode, as QNAP's guide states, so a NAS polling an SNMP card cannot pass the UPS on to slaves. The network management card guide covers SNMP cards in detail.
Power off or auto-protection: what happens when power returns
Every mode ends with the same choice. The NAS can power off after a set time on battery, or it can enter auto-protection mode after that time. In auto-protection, QTS stops all services and unmounts all volumes. Shared folders and iSCSI LUNs go offline, but the NAS stays on.
The two choices differ most when power comes back. QNAP's outage table spells it out:
| What happens next | Auto-protection mode | Power off |
|---|---|---|
| Power returns before the UPS runs flat | NAS restarts and resumes its previous state | NAS stays powered off |
| UPS runs flat before power returns | NAS powers off | NAS stays powered off |
| Power returns after the UPS ran flat | NAS applies its power recovery settings | NAS applies its power recovery settings |
Our rule of thumb: pick auto-protection unless someone is on site
Take a 10 minute outage with a 5 minute delay. In power off mode, the NAS shuts down at minute 5. Power returns at minute 10, but the UPS never ran flat, so its outlets never went dark. The NAS stays off until someone presses the button. In auto-protection mode, the same NAS restarts by itself. The data is protected either way, since both modes stop writes before the battery is gone.
The delay, and the 15% override
QNAP's FAQ suggests a delay of 3 to 5 minutes. There is also a rule the settings page does not show. When the outage starts, QTS checks the UPS charge. If it is below 15%, the NAS acts after 30 seconds, whatever delay you set. So an old battery that starts the outage nearly flat gets a fast shutdown.
QTS acts on the OB (on battery) status. A UPS reporting OFF makes the NAS power off. Self-test and SmartBoost states count as normal, so a battery test will not trigger a shutdown.
Worked example: one UPS, two QNAPs and a Linux PC
Take a small office with one 1500 VA UPS on USB to a QNAP at 192.168.1.50. A second QNAP sits at 192.168.1.51. A Linux desktop at 192.168.1.60 runs the NUT client. The switch is on a battery outlet too. Here is how the settings would go.
- Master (192.168.1.50). Select USB connection and auto-protection after 5 minutes. Select Enable network UPS master. Add 192.168.1.51 and 192.168.1.60 to the list. That is 2 of the 20 slots QNAP allows.
- Second QNAP (192.168.1.51). Select Network UPS slave, enter 192.168.1.50, and set auto-protection after 3 minutes. It is on the same subnet, as QNAP requires.
- Linux desktop. Run
upsc -l 192.168.1.50to read the UPS name. If it printsqnapups, the MONITOR line isMONITOR qnapups@192.168.1.50 1 admin 123456 slave. On NUT 2.8 or later,secondaryis the newer word forslave. - Test. Unplug the UPS from the wall at a quiet time. The second QNAP should stop its services at minute 3 and the master at minute 5.
The Linux desktop is the weak point in this plan. A standard NUT client acts when the server reports low battery or a forced shutdown. It does not copy the QNAP's 3 or 5 minute timer. Give it its own on-battery timer with upssched, as shown in the Proxmox shutdown guide. For the runtime budget behind these numbers, see how much runtime you need.
Sharing a QNAP UPS with other QNAP units
QNAP's multi-NAS steps match the worked example. Turn on Enable network UPS master on the USB-connected NAS and list each slave's IP. On every other NAS, select Network UPS slave, enter the master's IP and pick its own shutdown option.
QNAP sets three limits. A USB-connected master takes up to 20 slave connections. Each slave must be on the same subnet as the master. And if the network link between a slave and the master is lost, the slave may not get the warning. So the switch between them needs battery power, or the slaves go deaf the moment the outage starts. Give each slave a fixed IP, or a DHCP reservation, since the master's list is by address.
Reading a QNAP UPS from NUT clients
Any NUT client can read a QNAP master: Linux, a Windows NUT client, a hypervisor or Home Assistant. Three things have to match. A widely shared QNAP gist gives all three:
- The client's IP is on the master's network UPS list.
- TCP port 3493 is open in the QNAP firewall, if you run one.
- The client logs in as
adminwith password123456. This is a NUT account, not your QTS admin login.
The UPS name is where advice splits. The gist, a 2024 write-up on dalbert.net and a Home Assistant thread all use qnapups. The dalbert.net write-up adds that QNAP does not let you change it. A 2025 TrueNAS forum reply says the name must be ups. But that poster's own NUT server was a firewall, not a QNAP, and they said they had read it somewhere. So qnapups has the stronger backing.
You do not have to trust either. From the client, run:
# Lists the UPS names the QNAP serves, one per line
upsc -l 192.168.1.50
# Then read live data with the name it printed
upsc qnapups@192.168.1.50
The -l option asks the server for its UPS names, per the NUT manual. Whatever it prints is the name to use. If it fails to connect, check the IP list and the firewall before the name. In Home Assistant's NUT integration, enter the QNAP address, port 3493, and the same user and password. On a TrueNAS box, enter the same name, user and password in its slave-mode fields, which our TrueNAS UPS setup guide maps one by one. On one QTS 5.0.1 system, upsmon reported NUT 2.7.4. That version predates secondary, so QNAP-side files use slave.
A QNAP as the client of another NUT server
The reverse is harder. QTS slave mode asks only for the server's IP. It has no fields for a UPS name, user or password. Owners who got it working had to make their server look like a QNAP. The dalbert.net write-up adds a proxy UPS named qnapups on the NUT server, using the dummy-ups driver, plus an admin user with password 123456. The Home Assistant thread did the same with the NUT add-on. It also needed i_like_to_be_pwned: 'true', because the add-on rejects 123456 as a leaked password.
# /etc/nut/ups.conf on the NUT server: a proxy the QNAP can find
[qnapups]
driver = dummy-ups
port = myups@localhost
desc = "Proxy UPS for QNAP"
# /etc/nut/upsd.users: the account QTS expects
[admin]
password = 123456
upsmon secondary
Replace myups with the real UPS name on that server. Even then, the QNAP may not obey every signal. A QTS 5.0.1 owner sent a forced shutdown from the server, and only the other clients shut down. Running upsmon -c fsd on the NAS answered "kill: No such process". The real NUT monitor was not running. In 2026 a QTS 5.2.9 owner found the same thing: the GUI starts QNAP's own tool, upsutil, and never starts upsmon.
That second owner posted a workaround, which QNAP does not support. Edit /etc/config/ups/upsmon.conf with the real name and credentials, and start /usr/sbin/upsmon by hand. A cron entry every 5 minutes restarts it after reboots and GUI changes. Also set SHUTDOWNCMD "/sbin/poweroff", since the stock /sbin/shutdown does not exist on QTS. Test this setup with a real outage before you trust it.
QNAP and Synology on one UPS
QNAP states that its Network UPS slave mode cannot use a UPS connected to another NAS. The UPS must be able to work as a server with its own IP. That FAQ dates from 2022 and applies to all models and firmware. QNAP's newer 2025 FAQ still documents one QNAP following another, so read the old one as covering other brands.
For a Synology owner, this rules out the simple setup in both directions. A QNAP cannot follow a Synology through its settings. A Synology cannot easily follow a QNAP either. DSM's client mode asks only for an IP and expects ups, monuser and secret, as our Synology UPS setup guide explains. A QNAP serves qnapups with admin and 123456. Neither side lets you change what it expects.
Two setups get around it. A UPS with a network card can be polled by both NAS units, through SNMP connection on the QNAP and SNMP UPS on the Synology. Or give the USB cable to a third device running NUT, such as a Raspberry Pi NUT server. Define [ups] for the Synology and a qnapups proxy for the QNAP, with both user accounts. The QNAP side then carries the limits from the section above.
| Your setup | What to do | Basis |
|---|---|---|
| QNAP has the USB cable, other QNAPs follow | Network UPS master on one, Network UPS slave on the rest, up to 20 | QNAP FAQs |
| QNAP has the USB cable, Linux or Home Assistant follows | NUT client with admin / 123456, name from upsc -l, IP on the master's list | Gist, NUT manual |
| UPS has a network card | SNMP connection, community usually public | QNAP guide and FAQ |
| Another NUT server has the cable, QNAP follows | qnapups proxy and admin user on the server; upsmon workaround for forced shutdowns | dalbert.net, QNAP Community |
| Synology has the cable | Not supported by QTS. Use a network card or a third NUT server | QNAP FAQ (2022) |
The admin / 123456 default is weak
Treat 123456 as public knowledge, because it is. Anyone who can reach port 3493 and passes the IP check can log in as that NUT user. QNAP documents no way to change it, and every QNAP client expects it. So the IP list and the firewall are the real protection. Never forward port 3493 from the internet.
On a NUT server you run yourself, give the admin account only upsmon secondary, as in the example above. The Home Assistant thread granted instcmds = all. The NUT manual lists that as the right to send commands to the UPS, which a monitoring client does not need.
What this page does not cover
This page follows the QTS 5.1 user guide and QNAP's FAQs. QuTS hero uses the same menu path, per QNAP's FAQ, but its outage tables were not checked here. The NUT details come from owners' reports across QTS 5.0.1 to 5.2.9, not from QNAP. A firmware update may change the UPS name, the bundled NUT version or the slave behavior. Your UPS also has to be on QNAP's compatibility list, and sizing it is a separate job: see choosing a UPS for a NAS. None of it counts until you pull the UPS plug and watch each device shut down.
Frequently asked questions
What is the QNAP NUT username and password?
Community configs for Windows, Mac and Linux clients of a QNAP master use user admin and password 123456. This is a NUT account, not your QTS admin login. The client's IP must also be on the master's network UPS list, and TCP port 3493 must be open on the QNAP.
Is the QNAP UPS name qnapups or ups?
Most reports, including a QNAP owner's working config and a Home Assistant setup, use qnapups. One TrueNAS forum reply says ups, but that poster's own server was a firewall. Run upsc -l followed by the NAS address from any NUT client. It prints the real name.
How many NAS units can follow one QNAP UPS master?
QNAP says a NAS connected to the UPS by USB can list up to 20 UPS slave connections. Add each one by IP address under Enable network UPS master. Slaves must be on the same subnet as the master, and a slave that loses its network link may miss the warning.
Can a QNAP follow a UPS connected to a Synology?
Not through the QTS settings. QNAP states that its Network UPS slave mode cannot use a UPS connected to another NAS, and needs a UPS that works as a server with its own IP. Use a UPS with a network card, or a separate NUT server that both NAS units follow.
Should I choose power off or auto-protection mode on a QNAP?
Auto-protection suits most homes. It protects the data the same way, and the NAS restarts by itself when power returns. Power off is the deeper stop, but if power comes back before the UPS battery runs out, the NAS stays off until someone starts it.
Sources and further reading
- QNAP QTS 5.1.x User Guide: Configuring the UPS settings
- QNAP QTS 5.1.x User Guide: NAS behavior during a power outage
- QNAP QTS 5.1.x User Guide: UPS events and corresponding NAS behavior
- QNAP FAQ: How do I use a UPS with my QNAP NAS? (updated 2025-06-27)
- QNAP FAQ: How many UPS slave connections does my NAS support? (updated 2024-08-13)
- QNAP FAQ: How do I set up multiple NAS devices using one UPS? (updated 2025-11-30)
- QNAP FAQ: Can I use an UPS connected in another NAS as a network UPS slave? (updated 2022-06-24)
- mandria: NUT client settings for a QNAP UPS master (GitHub gist)
- Home Assistant Community: Adding Remote Access to Network UPS Tools (2021)
- QNAP Community: NAS won't shutdown from NUT master (2025 to 2026)
- dalbert.net: QNAP NAS and NUT (2024)
- TrueNAS Forums: UPS Connected as Slave via QNAP (2025)
- NUT manual: upsd.users(5) and upsc(8)