ilpixelmatto

Hi, I wrote a comment a few days ago, but the situation has changed. I tried completely removing the plugin, including its data and files, in the hope of fixing the problem, but it didn't help. If Tailscale is active, when I connect to the WEB GUI, I get ERR_CONNECTION_REFUSED. After analyzing, I discovered that the Nginx server daemon crashes and go down. When I try to restart it, I get: root@PixelNAS:~# tailscale up root@PixelNAS:~# /etc/rc.d/rc.nginx start rc.nginx: Starting Nginx server daemon... Starting Unraid API service... Starting flash backup service... Starting the Unraid API [PM2][WARN] Applications unraid-api not running, starting... [PM2][WARN] App unraid-api has option 'wait_ready' set, waiting for app to be ready... [PM2] App [unraid-api] launched (1 instances) +--- unraid-api namespace : default version : 4.29.2+c39b0b26 pid : 417610 pm2 id : 0 status : online mode : fork restarted : 0 uptime : 2s memory usage : 230.0mb error log : /var/log/graphql-api.log watching : no PID file : /var/log/.pm2/pids/unraid-api-0.pid Starting nchan processes... rc.nginx: Nginx server daemon... Failed. If Tailscale is down, it starts correctly and I can access the GUI. I'm attaching the diagnostic ID, which I didn't attach previously, which is why I'm commenting again. diagnostic ID: 93ae698a50ac69e791a4a456c978f602 Thanks, Riccardo

Hi, I've been having problems with the Tailscale plugin for a while now. I don't remember when it first happened, but I'm sure the tailscale plugin updated at least 1 time. I'll try to explain as best I can. I've been using the Tailscale plugin for years to connect to the server when I'm away from home. I also installed the Docker version as a backup, but it's never turned on, only installed. A few months ago, the developer changed the access methods for vaultwarden (Docker), which now requires an HTTPS connection to work. I then activated magicDNS and the HTTPS certificate in the admin console of tailscale. I configured Tailscale for HTTPS access as follows: tailscale serve --bg --https=4744 localhost:4743 If I run the command: "tailscale serve status": https://pixelnas.tailf****.ts.net:4744 (tailnet only) |-- / proxy http://localhost:4743 About a month after making this change (without any problems or further changes to any configuration), my power went out. I have a UPS, and the server shut down normally. When I turned it back on, I couldn't access the WEB GUI (ERR_CONNECTION_REFUSED). The only way I can access the WEB GUI is to log in via SSH, perform a "tailscale down" and then a "/etc/rc.d/rc.nginx start". If tailscale is "up", after a few minutes, the GUI shuts down, and trying "/etc/rc.d/rc.nginx start" again it fails. I solved the problem by deleting the snippet showing the tailscale status from the dashboard. A few days ago, I had to restart the server again. Now the problem has returned: if tailscale is up, after a while the GUI forcefully terminates. If I try to start the GUI with tailscale up, it fails: root@PixelNAS:~# tailscale up root@PixelNAS:~# /etc/rc.d/rc.nginx start rc.nginx: Starting Nginx server daemon... Starting Unraid API service... Starting flash backup service... Starting the Unraid API [PM2][WARN] Applications unraid-api not running, starting... [PM2][WARN] App unraid-api has option 'wait_ready' set, waiting for app to be ready... [PM2] App [unraid-api] launched (1 instances) +--- unraid-api namespace : default version : 4.28.2+d13a1f61 pid : 2146051 pm2 id : 0 status : online mode : fork restarted : 0 uptime : 2s memory usage : 229.9mb error log : /var/log/graphql-api.log watching : no PID file : /var/log/.pm2/pids/unraid-api-0.pid Starting nchan processes... rc.nginx: Nginx server daemon... Failed. If I stop tailscale (tailscale down), the command reactivates the GUI and stay UP. I don't know what else to try to fix the problem. Thanks pixelnas-diagnostics-20251219-1014.zip

Update: I actually never solved the problem. I used NUT to manage the UPS, every 1-3 days I am notified of the error but I don't notice any problems. If the power goes out, the server follows the directions I set without errors.

Hi, after all these months since I created the post, I continue to have the problem, although more occasionally. It happens to me once every 2-5 days. However, with management via NUT I solved the problem relating to premature shutdown. NUT gives a notification, but does not shut down the server. Mine is a somewhat particular case perhaps and these notifications are probably also caused by my home current which is 245V and not 230V, but so far I have never had any problems or sudden shutdowns. You can try doing the test and see how long it lasts on, but please stop the array before doing so.

Hi, a little update, I switched to NUT as suggested, the problem was partially solved, now doing some tests, I stopped the array, turned off the power and the UPS kept the system on for over 30 minutes, once reached 25% battery, it turned off as scheduled. Sometrimes the "battery have failed" error is triggered but it disappears immediately afterwards. All self tests continue to pass without problems. However, I discovered why NUMXFERS is so high, the voltage in my house should be 220 volts, but often it is 240-245 volts, this unfortunately causes the UPS to regulate the voltage which I think is the reason why it doesn't reach never 100%. I'll try keeping the UPS on charge with nothing connected, to see if it gets to 100%.

I don't have any sheet with tests performed on the UPS, perhaps they aren't performed in Italy, or they aren't included on Amazon. The 23 referred to the value of NUMXFERS. I tried setting the sensitivity to low, to see if it switches to battery less often. My only doubt is to understand if it is a faulty UPS or not, APC's powerchute software does not detect any problem, it runs the selftest and passes, by turning off the power on unraid it says "running on batteries" and it only happens for an instant "Batteries have failed on UPS" then goes back to running on batteries without giving any more errors. However, this is enough to trigger the shutdown. If I turn off the monitoring from unraid, the UPS holds up without visible errors (from the LEDs) for over 20-30 minutes.

I didn't understand the thing about the mfg test report in package, where can I find it? Now the low line voltage is at 23

Hi everyone, I bought this new UPS from Amazon 3 days ago: APC Back-UPS BX1200MI. I turned it on and unraid immediately recognized it, the problem is that occasionally, I get the notification of battery problems, but I don't see any errors. I tried to run the UPS self test and it didn't give any errors. I tried connecting it to a Windows PC and running the test from its proprietary software and it didn't give any errors. I tried turning off the power and it worked fine for the first 4 minutes, then in unraid it alarmed again and made unraid shut down. I then tried to turn off the power and connecting the USB to the Windows PC to monitor with the proprietary software and it didn't give any type of error for more than 20 minutes. When it reached around 50% battery I turned the power back on. Anyone have any ideas? Could it be due to the date of the batteries which is reported as 2001-01-01? If the product is new and never used, is this a problem? Can I simulate a battery replacement today by telling the UPS that I changed them to see if the error was caused only by the old date? Can it be done from unraid or do I have to use its software? I add that the battery always remains at 99% after 3 days and does not reach 100% so I cannot do the calibration from apctest. Thanks

Just for information, I updated unraid to 6.11.5 and now everything is working again with the latest version of the container.

I try with the "old" 1.8.2 but I have the same problem, I don't understand where is the problem, I don't have made any change in mounths. But now the zerotier-cli info tell me this: zerotier-cli info zerotier-cli: /usr/lib/libstdc++.so.6: no version information available (required by zerotier-cli) [...] zerotier-cli: /usr/lib/libstdc++.so.6: no version information available (required by zerotier-cli) 200 info abcda278f8 1.8.2 TUNNELED (on my.zerotier is offline 1H 34M) zerotier-cli listpeers 200 listpeers <ztaddr> <path> <latency> <version> <role> 200 listpeers 62f8***e71 - -1 - PLANET 200 listpeers 778***190 - -1 - PLANET 200 listpeers a0c***b62a - -1 1.10.2 LEAF 200 listpeers caf***eba9 - -1 - PLANET 200 listpeers caf***feb9 - -1 - PLANET zerotier-cli listnetworks 200 listnetworks <nwid> <name> <mac> <status> <type> <dev> <ZT assigned ips> 200 listnetworks a0cbf4b6***1148 IlPixelMatto 4a:ba:63:**:ce:0c OK PRIVATE ztc***j3c fda0:cbf4:b62a:***:4899:93ab:***:***/88,192.168.191.12/24 I tried enabling ipv6 as well but nothing changed. I've tried using another docker like "tailscale" VPN and it works fine so I'm assuming it's not the router blocking the connection. Also because I've been using zerotier in a virtual machine for more than a year and I've never had connection problems from that zerotier instance). Thanks very much for your hard work. 🥰

Hi, for a few days my unraid no longer connects to the zerotier VPN or does it for a few minutes and then goes offline. I have not made any changes to the server or to the router, I accidentally noticed it while trying to connect from outside the home. I enclose some information, hoping it will be useful: From the logs of the docker: connect: Operation timed out connect: Operation timed out connect: Host is unreachable connect: Host is unreachable connect: Host is unreachable / # zerotier-cli info 200 info abcda***f8 1.10.2 OFFLINE / # zerotier-cli listnetworks 200 listnetworks <nwid> <name> <mac> <status> <type> <dev> <ZT assigned ips> 200 listnetworks a0cbf4b****1148 IlPixelMatto 4a:ba:63:**:ce:0c OK PRIVATE ztc3***j3c 192.168.191.12/24 / # zerotier-cli listpeers 200 listpeers <ztaddr> <path> <latency> <version> <role> 200 listpeers 62f865**71 - -1 - PLANET 200 listpeers 778cde**90 - -1 - PLANET 200 listpeers cafe04**a9 - -1 - PLANET 200 listpeers cafe9e**b9 - -1 - PLANET The router has automatically created: There are no changes on the zerotier website Anyone have any idea what may be causing the problem? My provider is fastweb which is under NAT. Thanks!