RBoots

That wasn't related to the issue I had. I was actually planning on switching over to running everything through a dedicated vpn docker instead of using the deluge vpn. The issue I was having was specifically related to sonarr and radarr being unable to connect the indexers to jackett. However, I just solved it by changing the url I get from jackett torznab to be 'localhost' instead of using my actual IP address. Thanks for your help though. I think it did, in some way, point me in the right direction.

I've been using Binhex DelugeVPN with Sonarr, Radarr, Lidarr and Jackett all routing their internet through the Deluge docker for a couple months. A couple weeks ago, it stopped working. Sonarr, Radarr and Lidarr are no longer connecting to Jackett or Deluge. I don't remember changing any settings or if there was an update recently, I just noticed one day that nothing was being added to Deluge. I tried a slightly different route by using an openvpn docker and routing everything through that instead, but still nothing. If I disable the vpn and set each docker network type to 'Bridge' everything seems to connect as they should. For obvious reasons, I don't want to do it this way. Could anyone help me out on what could be going on? I currently have openvpn setup with a nordvpn account. I can check my public IP as well as ping google, so I would assume it has proper internet connection. Each docker container that is using openvpn is connected by setting the network type to 'None' with the argument --net=container:openvpn. Those also have the same public IP as well as internet access. But for some reason something seems to be blocking the connection to each other docker container. I don't even know if this is an issue with the docker containers or if I need to do something different on my network I hope I did a good enough job explaining what my issue is, any help is appreciated.

That appears to have fixed my issues. My server has been on for over 17 hours now, which is much longer than it has been for the past week. (Maybe I should give it another day before I declare it officially fixed.) At least it was an easy fix, I just wish I came across this much earlier. Thanks for your help

rbootsserver-diagnostics-20210314-1739.zip

I already have that turned on. I guess I don't really know what I'm looking for, but it doesn't seem to show any errors before it freezes. There's just a gap from the normal logs, to the next boot. If it doesn't appear to be related to a CPU issue, should I go on with listing the things I've tried to fix the problem?

For the past couple of weeks I've occasionally been finding that my server has rebooted or is unresponsive. (The past 1 week it's been basically unusable.) As far as I can tell there is no single-thing that causes this to happen. It will just happen anywhere between 10 minutes to 5 hours. I have tried many different things in attempt to narrow down what the issue is, but nothing fixes the problem. Before I list everything I've done so far I want to ask about something I found in a syslog file. (For some reason it only just crossed my mind to search for "error" in the log files.) .... node #0, CPUs: #1 #2 #3 mce: [Hardware Error]: Machine check events logged mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 5: bea0000000000108 mce: [Hardware Error]: TSC 0 ADDR 1ffff816f2e4a MISC d012000100000000 SYND 4d000000 IPID 500b000000000 mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1615731921 SOCKET 0 APIC 6 microcode 8001138 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 smp: Brought up 1 node, 16 CPUs And another time: .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 mce: [Hardware Error]: Machine check events logged mce: [Hardware Error]: CPU 14: Machine Check: 0 Bank 5: bea0000000000108 mce: [Hardware Error]: TSC 0 ADDR 1ffff8152f996 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1615699503 SOCKET 0 APIC d microcode 8001138 #15 smp: Brought up 1 node, 16 CPUs Is this a good indicator that my CPU is failing? I do have a CPU in my main desktop that will work in the server (the motherboard was just in my desktop until recently.), is it worth the effort to install it in my server for now? Or am I somehow misinterpreting this message? Extra note: Some variation of these same messages have appeared in all of the log files I just searched in. Solution was found here: