Closed codiflow closed 8 months ago
Sorry I missed your issue report - for some reason I did not see an email about it.
This issue was addressed in Pre-Release v2.3.8754 (duplicate #123 ). Please update to that and let us know how it goes.
Closing as duplicate
Sorry for my late response, Pre-Release v2.3.8754 fixed the issue.
Thanks!
WinNUT Version: 2.2.8719.24624 Windows OS Version: Windows Server 2016 1607 (Build 14393.6529)
Describe the bug WinNUT permanently disconnects from NUT running on OPNsense. WinNUT is not reconnecting to the NUT service anymore which has worked just fine a few months ago (I did not track this down immediately as it worked again sometimes). It tries to connect and after the "poll intervall" period it tries to reconnect – see the logs. As this has worked before the only things that changed were the update to the most recent WinNUT version and indeed OPNsense updates.
The setup is as follows: The UPS is connected via USB to the OPNsense firewall. The APCUPSd is the main UPS server on this firewall also providing a netserver instance. The NUT server on OPNsense internally connects to the APCUPSd netserver daemon and provides a NUT server for other devices. This way we can use NUT and APCUPSd in parallel in our network.
Unfortunately I don't have any logs on OPNsense side which could provide additional hints.
There's also a Synology NAS which is connected to the same NUT server and it just works fine – no issues.
Expected behavior Connection should be established and remain stable.
Additional context Debug log from WinNUT:
UPS variables:
While I wanted to copy the UPS variables also this error appeared – maybe this has to do with WinNUT not having been connected to the UPS at this very moment?