bonienl

It is possible to run pi-hole on a host network on port 80. This requires however the GUI to use a different port, which can be set under Management Access -> HTTP port.

Another excellent step-by-step guide is written by @Hoopster

Yes, you can, see Make sure your pi-hole container is running on its own IP address and have the peer use that IP address as DNS server. To allow communication between host (wireguard) and container (pi-hole), it is required the container runs on a VLAN or different interface.

Better move this discussion to general support and continue there. This is not really related to the new release.

Type "exit" and choose as boot option the emulated cd-rom with the ISO image (you propably need to press the "enter" key to start from cd-rom)

Two things to try: 1. Do not use CPU 0 / 8 for the VM. These are used by Unraid itself 2. Try a different machine type, e.g. Q35-3.1

I have both Ubuntu 19.10 desktop and server VMs running without issue on Unraid 6.8 What are your VM settings?

This is the screen of the IPMI tools plugin. Please report in the plugins section.

You need to remove the gateway assignment (192.168.0.1) under interface eth1. This is causing routing issues.

I don't think there is any bad intention in the reply of itimpi. In general if you have an issue, question it, but don't make it as a big warning and let it appear as given fact. If you do find a bug, please make a report under "Bug Reports - Stable Releases" and follow the guidelines as described here.

Can you post a screenshot

At the client side access is controlled by the "Peer allowed IPs", but of course a client can change these. Wireguard does not have a mechanism to restrict incoming access at the server side. A possible solution is to use iptables (firewall), but this requires manual work and won't be stored permanently. Besides, iptables is not the most user-friendly firewall configuration out there.

Congrats. You have some serious box

When the WAN IP address changes, your router needs to take care of it. WireGuard will follow automatically.

We need diagnostics to see what really happens

Connect a local monitor and keyboard to your server. From the command line type diagnostics This saves a diagnostics file in the logs folder on your USB device. Attach this file in your next post.

To give access to a specific IP address on the client side, you need to set the "Peer allowed IPs" accordingly. I.e. enter the address(es) which may be reached

Possible but not at the same time. VPN tunneled access must be used exclusively.

Looks like your Unraid server has a different IP address now, and you are trying to login to the wrong system.

No "local user" as another computer on your LAN accessing the Unraid server. Similar risks as a local computer accessing your server.

When you look at the picture included in the built-in help, you will see that "Remote tunneled access" gives you access to the server, the LAN and the Internet. WireGuard provides unrestricted access, this means that once a tunnel is set up and access is allowed to server and/or LAN, the remote user has the same access rights as a local user. Be careful with sharing WireGuard configuration information (especially the keys) if don't want unsolicited users to access your systems.

Any information about how to configure (set up) this on FreeNAS and Windows?

This is addressed in version 6.8. Passphrases are no longer stored in a keyfile.

Highly unlikely your system crashes, and the diagnostics seem to confirm that. 1. What exactly did you configure as WireGuard settings? 2. There is something going on with Docker and its virtual interface is going up and down. You can try to test with the Docker service stopped

I made another update, version 2019.11.12c