<html><head></head><body>Can you connect manually?<br><br>If so try to set listen - command to "0.0.0.0". That worked for me.<br><br><br><br><div class="gmail_quote">Am 3. November 2019 00:12:56 MEZ schrieb Charles Lepple <clepple@gmail.com>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Oct 26, 2019, at 2:50 PM, EP wrote:<br>> <br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">So long I am struggling with other issues. The "newest" one is, NAT-Server doesn't start anymore after rebooting the pi (USP ist unavailable). It's driving me mad.... 😉<br></blockquote><br>Does this help?<br><br><a href="https://github.com/networkupstools/nut/issues/735#issuecomment-544684998">https://github.com/networkupstools/nut/issues/735#issuecomment-544684998</a><br><br>Check dmesg/journalctl to see when the UPS is recognized by the kernel and/or when it detaches. It may be showing up initially, then dropping off the bus if NUT doesn't connect soon enough.<hr>Nut-upsuser mailing list<br>Nut-upsuser@alioth-lists.debian.net<br><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a></pre></blockquote></div><br><br>*********************************<br><br>Diese Nachricht wurde von einem Mobiltelefon unter Verwendung einer Texterkennungssoftware gesendet.<br><br></body></html>