bonienl

No, it doesn’t work together with the CA auto updater

When "Remote access to server" is selected, you need to use the tunnel address "10.253.0.1" (not 10.11.1.155) to access your server from your remote client.

When you go to the Docker page and update the "vpn" container, it will automatically update all other containers which depend on it.

You need to wait for the next release of Unraid, which will include the updates.

Post a screenshot of the main page

More refinements. Now impacted containers are automatically rebuild when the Docker page is opened. No user action required.

I made an update which translates the ID to the container name, e.g. container:vpn When the vpn network no longer exists due to an update, all impacted containers are shown as "update available" and can be updated at once using "Update ALL" Some are docker restrictions, but the modifications I have made should make your life a lot easier. It will also be possible again to specify a network in the extra parameters. If present it will overrule to default assignment.

I can not reproduce your situation. I created a tunnel WG0 with a remote peer, activated it and switched autostart on. After a reboot the tunnel is active again, like it was before rebooting the system. Since you don't get any error message when manually activating the tunnel, it should work too after a reboot, which my own testing confirms. I don't know what is going wrong for you. Can you post diagnostics after rebooting your system?

Did you set "autostart" for tunnel wg0?

Autostart should work, it sounds like something got corrupted in your configuration file. Try wg-quick up wg0 And post the result. Click on the "eye" icon of the tunnel and choose download (or read the QR code)

Another easy test.... Disconnect eth1, this forces all traffic to go over eth0. Does it work now? Disconnect eth0, this forces all traffic to go over eth1. Does it work now?

Another route you may want to try. Enable UPnP on your router and Unraid server. Remove the static port forwarding entries in your router. With UPnP enabled Unraid should see (and report in the GUI) what the router is doing as port forwarding.

Too bad, it comes with pool tables 😁

Good point. This is either your external (public) IP address or a resolveable name. Make sure this is still correct, i.e. update if your router has changed its external address.

Interesting. A keypoint of WireGuard is/was its difficulty to detect ...

Very true

It was already confirmed that Wireguard is running and listening on the designated port. Just do wg show # wg show interface: wg0 public key: ********************** private key: (hidden) listening port: 51832 peer: 3xow47demgEeU2eF6zNZPJO38cY7l9WsLRqjXcKbdC4= endpoint: 192.168.2.15:52047 allowed ips: 10.253.0.2/32 latest handshake: 1 minute, 34 seconds ago transfer: 784.12 KiB received, 2.28 MiB sent

This doesn't work with WireGuard. WireGuard is designed to remain silent unless it is a true WireGuard connection set up.

You can't really test this, because WireGuard will not respond to anything on this port unless it is a WireGuard connection set up.

No, WireGuard is working fine in 6.8.2. Just made a test to confirm this.

WireGuard tunnel is up and running. What port forwarding rule did you set on your router? And what is your remote peer config look like?

Tunnel should be started according to your messages above. What is the output of wg show

You likely need to remove the offending card first and get it to boot normally, and make the changes. Enable "mirror syslog to flash", see Settings -> Syslog server A copy of the syslog information is stored on your USB device in the /logs folder. Post it here.

Please open a new topic under general support. Here is not the right place to discuss issues.