bonienl

Plus a VPN solution, like WireGuard has build-in protection to keep intruders out. Though nothing is perfect, at least it is a whole lot harder than a password only defense.

When multiple IP addresses are entered (comma separated) then ALL of them must not answer for s3_sleep to proceed.

Indeed, there is a lot to do at the Unraid front first.

A general tip for those people you use pi-hole as local DNS server. Always make sure your Unraid server does NOT use the pi-hole DNS server, but a "regular" DNS server instead, e.g. google or cloudflare. If you want a docker container to use the pi-hole server, you can add the option --dns=<pi-hole ip-address> in the extra parameters field of the container.

It has been some time since I visited the Unraid forums. Due to health issues I had to take a break, and unfortunately this break took way longer than anticipated. But I am back and will start giving support again to Unraid and plugins. First step is an update to the s3_sleep plugin, which now supports the latest features of Unraid 6.9 properly. Please update this plugin if you are running Unraid 6.9.0 or higher. I need to do a lot of catching up, but feel free to post issues with the Dynamix plugins here and I will look into it.

See the setting "Error logging" under Settings -> File Integrity

Start your server in safemode and test again.

Something has gone wrong in the syslog assignment. Did you make any manual changes? rsyslogd 16070 root 5u IPv4 29802 0t0 UDP 127.0.0.1:514 rsyslogd 16070 root 6u IPv4 29803 0t0 UDP 127.0.0.1:514 rsyslogd 16070 root 8u IPv4 30876 0t0 UDP *:44122 Do the following actions to restore a default configuration and start from scratch. Delete the files "rsyslog.cfg" and "rsyslog.conf" in the /config folder on your flash device Reboot your server Configure the syslog server settings

I introduced a regression error with the last version, sorry. Version 2020.08.03 is available with the correction.

You can always look at the change log. fixed multi cache pool support logrotate updates by Alex R. Berg Always exclude UD devices

Another update to Dynamix cache dirs, version 2020.08.01a

In this update UD is completely excluded. Just remove the entry.

I made an update which fixes the multi pool issue. Please try.

Sure

First picture: names of shares are not translated and are displayed as is. This is correct. Second picture: this is a bug on the Dashboard page (wrong reference). This is fixed in the next version of Unraid. Thanks

I don't see anything going wrong in the log. Try to disable and enable the docker service again.

You need to enable custom network for eth0. See Settings -> Docker Settings

Post your diagnostics

The WG tunnel terminates internally to the system and bypasses the firewall (iptables) function.

Each device is another peer. You can add peers to the tunnel and give the same or a different profile to these peers. One restriction: "VPN tunneled access" must in in its own tunnel and not be shared.

Your controller is indeed found as a USB attached device. Bus 002 Device 002: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN but no drivers are loaded, I am not sure if the reason is because it is a USB attached device, though likely it is a missing driver.

Your system only reports two Intel controllers 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM 02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 Is your RealTek NIC an add-on? If so try a different PCI slot. Ps. No need to post the syslog separately, everything (and more) is included in the diagnostics.

I wanted to put some more perspective into this request. It is definitely more than simply adding some drivers as was said in an earlier post. I didn't say yes or no either!

Yes

One of the most beneficial things about Unraid, is the ability to move the USB key to another (new) system with complete different hardware, and start it like nothing has ever changed.