@elvisimprsntr thanks for your suggestion. I will give it a try.

@dennypage said in NUT suddenly stops working every app. 6 minutes:

Okay, that is entertaining to say the least. Does "66da6bc012db26058161" happen to be the locally generated password for local-monitor?

I have not the slightest idea! Never seen this before!!!!

Rest: Will be delighted to do so! Thanks for the instructions.

@viragomann
Yes it definitely is rebooting, but not immediately. I was able to try it 3 more times before putty quit responding.

Here is what shows in putty...

Select function number: 10

This test instructs the UPS to perform a battery calibration
operation and reports the result when the process completes.
The battery level must be at 100% and the load must be at least
10% to begin this test.

Battery level is 100% -- OK
Load level is 14% -- OK
Clearing previous self test result...CLEARED

The battery calibration should automatically end
when the battery level drops below about 25%.
This process can take minutes or hours, depending on
the size of your UPS and the load attached.

Initiating battery calibration...INITIATED

Waiting for calibration to complete...
To abort the calibration, press ENTER.

CALIBRATION COMPLETED
Result of last self test: ABORTED

Test kill UPS power Perform self-test Read last self-test result View/Change battery date View manufacturing date View/Change alarm behavior View/Change sensitivity View/Change low transfer voltage View/Change high transfer voltage Perform battery calibration Test alarm View/Change self-test interval
Q) Quit

Select function number: 10

This test instructs the UPS to perform a battery calibration
operation and reports the result when the process completes.
The battery level must be at 100% and the load must be at least
10% to begin this test.

Battery level 99% is insufficient to run test.

Test kill UPS power Perform self-test Read last self-test result View/Change battery date View manufacturing date View/Change alarm behavior View/Change sensitivity View/Change low transfer voltage View/Change high transfer voltage Perform battery calibration Test alarm View/Change self-test interval
Q) Quit

Select function number: 10

This test instructs the UPS to perform a battery calibration
operation and reports the result when the process completes.
The battery level must be at 100% and the load must be at least
10% to begin this test.

Battery level 99% is insufficient to run test.

Test kill UPS power Perform self-test Read last self-test result View/Change battery date View manufacturing date View/Change alarm behavior View/Change sensitivity View/Change low transfer voltage View/Change high transfer voltage Perform battery calibration Test alarm View/Change self-test interval
Q) Quit

Select function number: 10

This test instructs the UPS to perform a battery calibration
operation and reports the result when the process completes.
The battery level must be at 100% and the load must be at least
10% to begin this test.

@JonesTech I recommend removing all the excess config you have put in.

There are far too many copy/paste magic recipes for NUT on the internet that mislead people. The best approach with NUT is to start with the default configuration, and let NUT and your UPS take care of business as designed. You should only add directives to NUT if you are doing so to address a specific problem, and even then be very minimalist. And with every OS or NUT upgrade, you should retest/reconfirm that the directives are actually still necessary.

ignorelb, while commonly recommended on the internet in various recipes derived from 10 or 15+ year old information, is almost always a very bad idea. It should ONLY be used if you have one of those very unfortunate old UPSs that declare Low Battery immediately on mains fail. On a modern UPS, you simply don't want to ignore the UPS saying "Hey, the battery is low, I'm about to shut down..."

interruptonly is not pertinent to the initial connection of the driver, and should only be done if necessary to address constant disconnects with your UPS. Usually this is used to work around bugs in the USB or driver layer. If you do need to put this in, you should retest this with every OS or NUT upgrade to see if it is still required.

Increasing pollinterval will make it longer before the system knows you are on battery. Almost certainly not what you want.

override.battery.charge.warning has no meaning with the pfSense configuration.

override.battery.charge.low will cause NUT to initiate a shutdown even though you have over a third of your run-time remaining. While this is a meaningful directive, are you sure this is what you want? And are you sure your UPS will work correctly this case?

@Laxarus said in SNMP UPS inconsistent connection:

DNS failure is one of the suspects

No need to keep the "suspect" waiting, as you can consult the proof right away.
Go here : Status > System Logs > System > DNS Resolver and see if you can find :

59c728e4-a985-4222-b07d-e0d394cb1ebb-image.png

If you find them, match the related time stamp info with the NUT UPS events (main system log).

If they match, and it happens to often, get yourself this mission :
Figure out why unbound restarts, then evaluate the conditions that made it restart.
The final goal is (always) : make DNS as accessible as possible.

For example : a default, "clean" pfSense install won't restart unbound for days, even weeks.
Start plugging in and moving network cables into pfSense, or power down and power up devices attached to pfSense directly by cable, and every time packages get restarted.
Install pfBlockerng and according its settings it can restart unbound many time per day.
Depending how you use pfSense, what you've installed extra can make live hard for your DNS ... for yourself.
Your mission as an admin : find the right balance.

@firefox said in ups shutdown pfsense after 30 seconds:

Could this be an incorrect setting in the SNMP card's graphical interface?

I took the SNMP card from another UPS that is from the same manufacturer as my UPS.

this is the model of my ups AON1500-2
this is the model of the ups i took the card from top v pro 6

When I connected the snmp card to the ups
it seemed to recognize that it was a different ups

I assume this is the same UPS as you were asking about last December?

I do not have familiarity with that UPS manufacturer, so I really can't answer your question. You can either reach out to the manufacturer and ask them about NUT SNMP support for their UPSs, or go down the path of learning about SNMP and diagnose the issue yourself. Unless you happen to find someone with the exact same UPS and SNMP card, already working with NUT, this is going to require some effort.

FWIW, the odds are that either the SNMP driver is incorrect, or the MIB is incorrect. For me, the first step would be to learn about the available MIBs, and begin exploring the SNMP interface with snmpwalk.

@AngryAnt said in pfSense -> pfSense NUT connection issues:

I had explicited the firewall allow rules to the NUT port only

Yes, that is appropriate. The allow example really should have had a destination port like so:

Screenshot 2025-06-03 at 10.56.00.png

@dennypage
I added back in the listen directive and removed the port forward. Seems to work well also. Not sure why my arp table got mussed, but I guess that can happen.

Thanks, all! Upgrading to the latest pfSense Beta fixed it!

@rdibley said in Linefeed in pfSense email notifications (with Network UPS Tools):

So one more question: if most people don't use the Advanced section (and the users.conf is blank), how does a secondary system connect to the primary? Is it that most people don't define a user/password for monitoring, but that the primary is just open to any secondary system that might want to connect?

I'm using it 😊

b852fa0b-7f4c-4461-8c73-3867487db57f-image.png

The third entry is for my Synology NAS :

And the NAS side :

c67da02f-ce7a-456c-a7e1-fede22ed4b6b-image.png

and done.

I've also installed "Windows NUT Client" on two PC's nearby.
Example : PC 1 with user name "pcrecep1" and password "secret1" :

e41ec81d-1698-431f-98f9-17e142c93132-image.png

Works fine also.
So I've 4 devices protected with one big 1000 VA APC UPS, where pfSense is the NUT 'server' as it has a USB cabled UPS hooked up to it, and now 4 devices are controlled by this UPS instead of one.

@dennypage I will go for your suggested solution:

UPS 1: pfSense as NUT server and the rest as NUT clients
UPS 2: one system attached to the UPS as the NUT server and the others as NUT clients

Since I don't have enough knowledge of NUT I guess I will be back several time to this forum.
Thanks for you gudelines and Merry Christmas !!!

@firefox Glad you got it working

@netboy Glad you got it sorted.

@jrey: Very helpful! Thank you very much!

Note that these are two quite different questions:

Once the UPS declares a low battery, does the UPS have enough battery remaining to cover the time required for the NUT primary, and potentially secondaries, to complete their shutdowns? This is potentially several minutes.

After being instructed to cut the power by the NUT primary, does the UPS wait long enough for the NUT primary, and potentially secondaries, to complete their shutdowns before turning off the power? This is usually 20-60 seconds.