Morphed

Yes sir, did it after the upgrade to 6.11.0. This was my first play around with lxc and was looking at moving some VMs to containers instead. Was really hoping that cpu and memory limits would be visible in container, which doesn't seem to be the case.

From this: https://discuss.linuxcontainers.org/t/limitations-not-applied-inside-of-containers/11395/3 Just tried lxc.cgroup2.memory.max = 4G and it at least allows me to start the container, I think the limits are enforced as I tried to make a 4G file in /run and the container died

My logs came from my webserver hosting some websites. I had never thought to run unraid through shodan till now... >442 results with: >208 HTTP/HTTPS >52 SMB yeouch.... just by searching "unraid"

https://www.cvedetails.com/cve/CVE-2017-9841/ I'm not sure if Nextcloud uses phpunit, but its likely just some script somewhere just running through any IP that has 80/443 open and testing for known vulnerable scripts. If it redirects to/loads a login page or nextcloud, you are likely fine if they come back and try to post things to it. Having your server connected to the internet will bring a lot of unwanted traffic. For example: $ grep 183.134.74.13 access.log.1 | wc -l 935 Sample of the logs: 183.134.74.13 - - [13/Feb/2020:02:24:34 +0000] "POST /zmp.php HTTP/1.1" 301 162 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36" 183.134.74.13 - - [13/Feb/2020:02:24:35 +0000] "POST /803.php HTTP/1.1" 301 162 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36" 183.134.74.13 - - [13/Feb/2020:02:24:35 +0000] "POST /zzz.php HTTP/1.1" 301 162 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36" 183.134.74.13 - - [13/Feb/2020:02:24:36 +0000] "POST /ze.php HTTP/1.1" 301 162 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36" 183.134.74.13 - - [13/Feb/2020:02:24:37 +0000] "POST /nnb.php HTTP/1.1" 301 162 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36" And that went on for 10 minutes. That said, if you are worried about one random page hit from a random IP, it might be worth considering if you really need your server connected to the internet and if it wouldn't be better off using a VPN to access services.

I'd say that there is no real advantage to wireguard over setting up a VPN on your router, though I haven't looked into wireguard much myself. Go with what you are comfortable with, but I imagine if you need help you would get more community support here for Wireguard than your router's VPN. VPN (in the context we are talking about) is a way to give you/others a secure, encrypted connection into your own network from outside with out having to open multiple ports to the outside world. The end result would be that you have access to all/most features of your home network securely from anywhere in the world. Edit: I would also focus on clearing up what ever is causing the malicious traffic before looking at setting up a VPN.

It is a nice case. Was really interesting to build into as well.

unRAID badge arrived today, GF approved my putting it on my case as it is in the living room in full view. https://imgur.com/a/twtKa2v Have to say, its a bit bigger than expected, but still very happy with it! Thank you unRAID!

Like: Flexibility and ease of use. Haven't played with VMs yet, but hopefully in the next few weeks when my new motherboard gets in stock! Want to see: The ability to automatically export stats to InfluxDB or prometheus without having to have ~ 3 different docker containers running just for stats logging.