February 19, 20215 yr Everything has been running fine until last night around 8:30pm EST when I got what I believe was a kernel panic but I didn't have a monitor hooked up and no logs were saved that I could find. This morning when I woke up my server was again unresponsive so before I hard rebooted it I plugged in a monitor and saw the attached picture. I've also attached the diagnostics.zip if that helps in any way. IMG_4702.HEIC server-diagnostics-20210219-0745.zip
February 19, 20215 yr Community Expert 8 minutes ago, timstephens24 said: and saw the attached picture Can't open that file, you can display photos directly on de forum.
February 19, 20215 yr Author 1 hour ago, JorgeB said: Can't open that file, you can display photos directly on de forum. Weird. Let’s see if uploading directly from my phone works.
February 22, 20215 yr Community Expert Those photos aren't very helpful, try this and post that log after a crash.
March 8, 20215 yr Community Expert Crash appears to be network related, try to simplify your config as much as possible, also don't assign a custom IP to dockers.
March 8, 20215 yr Author 3 hours ago, JorgeB said: Crash appears to be network related, try to simplify your config as much as possible, also don't assign a custom IP to dockers. Thanks for looking. I had already removed the docker that had a custom IP a few weeks ago since I also thought that it might have been a network issue with the PiHole DoT-DoH docker. All the rest of the dockers either use Bridge or Host except one that's going through a bridged docker (VPN). I'm not sure what you're referring to on simplifying the config as much as possible, though. My network settings are pretty standard, the only thing I did that's not default I believe is turned on IPv6.
Archived
This topic is now archived and is closed to further replies.