pacnpal

Thank you for the bug report, it's now fixed in the latest version. I admittedly don't use host networking with my Docker containers, so that was an unfortunate oversight on my behalf. What was happening: when wg-quick brings up a tunnel with AllowedIPs = 0.0.0.0/0 and no Table = off, it installs an ip rule that routes everything not marked with fwmark 51820 through wg0. If your tunnel was originally started some other way (custom script, manual wg setconf, container-managed) and that rule wasn't already there, the watchdog's wg-quick up would suddenly install it. Every --network host Docker container then started hairpinning through wg0. That's your symptom. The fix: bounces now use wg syncconf, which resets peer crypto state without touching ip rules, routes, or iptables. The hard wg-quick down/up is a last-resort fallback, and even then, if your conf is in the redirect-prone shape and the fwmark isn't already on the live interface, the watchdog refuses the bounce and logs why. The exact failure you hit is structurally unreachable now. Reproduced it end-to-end on a real Unraid box with the old code, confirmed zero routing diff with the new code.

WireGuard WatchdogSmall plugin that keeps your WireGuard tunnel healthy. It pings a peer through the tunnel on a schedule, and if the peer goes quiet it bounces the tunnel with wg-quick down/up. Plays nice with Unraid's built-in WireGuard support, since it never touches the interface directly, only goes through wg-quick. WhyWireGuard fails silently. A peer reboots, a NAT mapping expires, an upstream blip happens, and the tunnel still looks "up" from your end. wg show reports nothing wrong, but no traffic actually flows. The fix is always the same: bounce the tunnel. This plugin does that for you, but only after a real liveness check, not just a "is the daemon running" check. FeaturesConfigurable interface, peer IP, and check interval (down to 20s) Verbose mode logs ping latency, packet loss, handshake age, and transfer counts Test Now / View Log / Clear Log buttons in the UI flock-protected so overlapping cron runs can't step on each other Cron sticks around across reboots via update_cron Disabled by default on first install. You opt in. InstallPlugins tab, Install Plugin, paste in the .plg URL. Then go to Tools, User Utilities, WireGuard Watchdog, set Enabled to yes, and hit Apply. RequirementsUnraid 6.12+ (tested on 7.2.x) A configured WireGuard tunnel under Settings, VPN Manager A peer IP that's reachable through the tunnel when things are working SourceGitHub: https://github.com/pacnpal/wireguard-watchdog License: MIT Feedback welcome.

I see no button to add a "Disk Tray Layout" on the "Layout" tab.

The error: [1/5/2025] [2:01:58 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com Is indicating a DNS issue.

I love this container, I just wish it didn't update so often for no reason. I checked the github and it generates a new docker image on schedule every week, no matter if there was a change or not. I have quite the custom config and don't want to update unless absolutely necessary. Do you think it would be better to create my own custom image? Mine is customized to work as a universal relay for forwardemail.net, using their catch-all alias to attach the original sender as the from address, skipping the whole "relay address" thing altogether.

In Nginx Proxy Manager, edit the Unraid proxy and enable Websockets support.