Wireguard Easy - Has anyone ever managed to get this to work?

Insight & Feedback
1

I’ve spent a few hours trying to get it to work—no luck.

Neither the ancient version (V13), nor the Legacy (V14), nor the latest (V15)… the documentation is a nightmare, and the link to the forum:

Added WG Easy V15 to BigBearCasaOS - BigBearCasaOS Change Log - Big Bear Community

doesn’t help either… :cry:

Let me know if anyone has managed to do this and, more importantly, how?
Thanks!

2

Yeah… you’re not alone on this one. WG Easy on ZimaOS/CasaOS has been hit-and-miss for a lot of people, especially across V13 > V15.

From what I’ve seen helping others (and testing myself), the issue usually isn’t WireGuard itself, it’s a mix of:

  • container networking (NAT / port forwarding not lining up)
  • missing kernel support or permissions on ZimaOS
  • environment variables not matching the actual network setup
  • CasaOS UI not exposing everything WG Easy expects

So people end up thinking “it doesn’t work”, when it’s more like “it’s very sensitive to setup”.

What actually works (in real-world setups)

Yes — people have got it working, but almost always when:

  • they run it via Docker CLI / compose, not just the App Store template
  • they explicitly set:
    • correct WG_HOST (your public IP or domain)
    • correct UDP port (usually 51820)
  • and most importantly:
    • router port forwarding is configured properly

Without that last one, it will never connect even if the container is perfect.

Why it feels broken on ZimaOS

ZimaOS adds a couple of quirks:

  • It’s Docker-first (no full system control like Ubuntu)
  • Kernel modules (like WireGuard) aren’t always exposed the same way
  • App templates can be outdated or incomplete (especially V13/V14)

So newer WG Easy versions (V15) can behave inconsistently depending on how they’re launched.

Honest take (so you don’t waste time)

If you’ve already spent a few hours and got nowhere:

It’s probably not you, it’s the stack.

What I’d suggest (non-destructive, realistic path)

You’ve got 2 solid options:

Option 1 — keep pushing WG Easy

  • but switch to a clean Docker Compose setup
  • ignore the CasaOS template completely

Option 2 — use something more stable on ZimaOS

  • plain WireGuard container (no UI)
  • or something like NetBird / Tailscale (way less friction)

If you want to continue with WG Easy

I can give you a known-working minimal config that’s been reliable on ZimaOS, but I’d want to confirm first:

  • are you trying to access it from outside your network?
  • and do you control your router (for port forwarding)?

That’s the key difference between “it runs” and “it actually works”.

3

thanks a lot gelbuilding for your comprehensive reply…
and glad to learn that it’s probably not always me who fails;

I tried tailscale and it works so I could live with that -
although in my “before Zima time” I used wireguard on my old NAS
and got to like its simplicity and full control idea;

so I think I’ll skip “easy”wireguard and try with plain docker CLI/compose
so 2 questions:

  • any recommendation for a docker compose?
  • I am on a Wimax network and have no control on the router/antenna, but have to ask the provider to open ports etc. - so I have an open port 51820 pointing to one of the zimblade’s ip-adresses (both ethernet ports are connected to a switch). Does it matter which one it is pointing to?
4

tried it with the linuxserver/wireguard container
just changed
SERVERURL and the volumes section

done in 10 minutes and works like charm - even produces client configs;

1 Like