bonienl

More updates... version 2019.12.26b 2019.12.26c 2019.12.26d VPN tunneled access was broken.

I made an update available with the fix. Version: 2019.12.26d Regarding local endpoint, this could happen due to a mistake in one of the earlier versions. You need to enter it again and it should work from now on. Perhaps it is a good idea to re-apply the settings (just make a change and undo the change to activate Apply). This will generate a new and proper settings file for both server and peer(s).

Select Advanced mode and check if a mandatory field is missing A bug in the latest version, need to correct that.... DONE

Good news. An update of the Dynamix WireGuard plugin is available. This version supports mixed IPv4 and IPv6 tunnels. It has quite extensive updates and corrections and users are encouraged to update. Give it a try ...

WireGuard doesn't really report a connection status. It is silent by design and doesn't have a mechanism to keep a connection in a 'connected' status.

Right now you need to set up two separate tunnels, one for IPv4 and the other for IPv6. I will look into a future update to combine IPv4 and IPv6 over the same tunnel.

Some general advice 1. In network configuration you need to enable both IPv4 and IPv6 for the interface(s). This will allow docker to use IPv6 as well. 2. In the docker configuration you need to define IPv6 custom network(s), which includes the IPv6 subnet and gateway 3. In pi-hole you need to define the ServerIPv6 (=IPv6) DNS address 4. In pi-hole you need to set the IPv6 upstream DNS servers 5. You need to configure your router to hand-out the appropriate IPv4 and IPv6 DNS addresses in DHCP (or set fixed DNS in your LAN clients)

You selected "bridge" network. This is shared with your server network. Hence port 80 (HTTP) is already in use by the GUI and not available to pi-hole. You'll need to set a custom network to give pi-hole its own IP address.

You are responding to a two year old topic and it is unclear to what problem you are referring to (if any at all). If you have an issue open a new topic. People in this forum generally respond helpful and quick.

Sure, but better to report issues in the relevant topic Anyway, I made an update which validates FQDN input against all the top level domains (TLD) defined by IANA as of December 21, 2019. Go to plugins and update the Dynamix Wireguard plugin.

Unraid 6.8 supports WireGuard, which allows remote VPN access independent of the array status.

See this guide

Below an example configuration It is mandatory to define a local endpoint (main server) and a peer endpoint (backup server). These endpoints can be a URL or a (public) IP address of the server. When the main server is behind a NAT router then port forwarding must be set on the router. The same is true for a NAT router used at the backup server (peer) side.

Some mobiles go into standby mode to save energy, usually sometime during the night. This may interrupt communications. Does your mobile phone have specific settings to save battery?

Maybe this drawing helps ...

Different peers can share the same tunnel, there is no need to create a new tunnel for each peer, unless you want to create a tunnel with other characteristics, e.g. a tunnel running over a different interface. Yes, a typo.

WireGuard runs on any port. You can use the automatic port assignment of the GUI or choose your own port number.

You can add your backup router as a second peer to the existing tunnel, next to your phone. Like your phone set the backup router as "remote access to server (or LAN)". This allows the backup server to initiate the connection. For example a scheduled script can make contact and initiate the connection. A server to server connection is intended to let both sides intiatie the connection setup, it doesn't matter which side does it. This is convenient if you want either side to be active in setting up the communication.

If it works with openVPN, it should work with WireGuard too ...

Did you add those subnets to the list of allowed IPs for the client?

Something is eating your memory, causing resource issues. Most common reason is a misconfigured docker container, which results in storing everything in memory rather than disk.

Attachments are not possible, but you can include messages (-m option). notify [-e "event"] [-s "subject"] [-d "description"] [-i "normal|warning|alert"] [-m "message"] [-x] [-t] [add] create a notification use -e to specify the event use -s to specify a subject use -d to specify a short description use -i to specify the severity use -m to specify a message (long description) use -x to create a single notification ticket use -r to specify recipients and not use default use -t to force send email only (for testing) all options are optional notify init Initialize the notification subsystem. notify smtp-init Initialize sendmail configuration (ssmtp in our case). notify get Output a json-encoded list of all the unread notifications. notify archive file Move file from 'unread' state to 'archive' state.

Pages are not displayed because of a missing csrf token. This is a browser issue, clear the cache of your browser or try a different browser.

Make sure the local endpoint and peer endpoint are correctly set. This maybe a URL name which can be resolved or the public IP address of the server. If there are any routers/firewalls at either side, they need to do port forwarding to make outside access possible.

Can you please open a topic under general support and close this report. Your issue more likely something specific to your set up and not a bug.