May 18, 20251 yr Server locked up using web access and couldn't be accessed over the network or through ssh, giving connection refused message. Media could be played, dockers were operational and accessible but weren't able to access each other. I had to do a hard restart and the problem occurred again as soon as I logged in. Managed to get a diagnostic after another restart. Any suggestions? 192.168.1.44-diagnostics-20250518-1943.zip
May 18, 20251 yr Author It is enabled, I thought diagnostics would have picked up the file. Hopefully I've done it correctly and this log will help. syslog-192.168.1.44.log
May 18, 20251 yr Community Expert Unfortunately, there's nothing relevant logged, this can also be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers. Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.