senpizzle

Thanks, that's my plan for the future, but I'm not really sure how that's relevant to this thread. I'm not able to setup Tailscale until I regain access, right?

A bit of a puzzle here. I keep my unRAID server at my parents house so I do not have physical access, but I can coach my mom through basic things over the phone like "turn it on," or "unplug and re-plug the yellow cable." Last week, my server suddenly stopped responding. So I had my mom turn it back on, and assumed it would work. It did not work. It mostly seems to function normally, I have full access to Plex, Immich, and NextCloud because they're reverse-proxied through NGINX and Cloudflare, but the most important thing doesn't connect, Wireguard. Without it, I cannot connect to the local network, preventing the use of the WebGUI or terminal. I've confirmed that the public IP (though dynamic) has not changed. Similarly, DuckDNS has the correct IP, and my Wireguard config files have the correct DuckDNS url. The port 51280 is also still open. I have a JetKVM that also seems to be connecting, but the Video feed stopped working a while ago, and I gave up after some unsuccessful testing. Oops. Theoretically that means I can still send commands through the terminal, but I'd be acting completely blind. Any suggestions would be helpful!

Hi, I’m pretty sure that I did, in the last line of the post. Is there a different diagnostics that I need?

I think I might be revealing how little I really know, here, but I'm at a loss after pulling out my hair for two weeks on this. I posted this on Reddit and received a bit of help in better diagnosing the issue, but still no solutions. My Server (Unraid 6.11.5) has been a touch unreliable for a few months now, but as I live offsite and keep it at home with my parents, I chalked it up to a power issue, and haven't really bothered to dig too deeply. Until now. I always access my system remotely via Wireguard. As of about three months ago, it started going down once or twice a week. When I was home for Christmas for two weeks, it didn't go down once. But after I came back about two weeks ago, it began shutting down every 1-3 days. So I turned on persistent logging, and now I can see that it isn't crashing or losing power, it's being shut down. I do not have a UPS. The log has the following line preceding every shutdown, with a different PID every time: Jan 25 17:54:39 Halcyon shutdown[13541]: shutting down for system halt I also set up a script that sends me the output of "ps auxef" in a .txt file, a list of all PIDs currently running. I can cross-reference that with the log to figure out what the PID is of the service initiating the shutdown. root 1151 0.0 0.0 6320 2484 ? S Jan23 0:00 elogind-daemon SHELL=/bin/sh RUNLEVEL=3 PWD=/ HOME=/ TERM=linux INIT_VERSION=sysvinit-2.99 SHLVL=2 BOOT_IMAGE=/bzimage CONSOLE=/dev/console PREVLEVEL=N PATH=/bin:/sbin:/usr/bin:/usr/sbin _=/lib64/elogind/elogind root 13541 0.0 0.0 0 0 ? Z 17:54 0:00 \_ [init] <defunct> To me, this means that PID 1151 spawns PID 13541 to initiate the shutdown, which then terminates itself. Some googling around helped me to understand that elogind handles user logins, sessions, and power-related actions like shutdowns, suspends, and reboots. Short of that though, I haven't been able to figure out where to go from here. I'll also include the syslog, output of the most recent ps auxef, elogind/login.conf, and Diagnostics Zip File Any help would be much appreciated!