unbound-docker-rpi VS wg-easy

- Unbound

In Pi-Hole, all the queries are sent to and answered by the Unbound docker container, as confirmed by the Pi-Hole logs. I am not seeing any query in Pi-Hole going outside my network for resolution, so I am stumped as to what the cause of this is. The best guess that I could come up with is that somehow Unbound got configured in forwarding mode instead of a recursive resolver. I am not an expert on networking or Unbound, so I am looking for anyone who has an idea as to how to solve this. If it helps, I used https://github.com/MatthewVance/unbound-docker-rpi as the docker image to set up unbound.

If your using a pi, you need to use the pi image. Also I remember that I created these files before deploying the container: config files for unbound * a-records.conf ```

mvance/unbound-rpi is a image that is updated regularly and used by many. The code he uses to create the image is here.

After browsing through, I've noticed that three options seem to be gaining traction: Netmaker, wg-easy, and headscale. I'm curious to know if these solutions are interchangeable, and if there are specific reasons to choose one over the others. I'd also like to understand if they are complete stacks, meaning, once set up, could I easily replace one admin GUI with another, or would I need to tear down and rebuild the VPN?

WireGuard is the solution to everything! It has an app and they can easily login via a QR code that you send them. For the server I would recommend wg-easy, there you can manage all user accounts in a web interface.

I use this, https://github.com/WeeJeWel/wg-easy

Dashboard with access to the QR and config files for clients as well as bandwidth data. Even something as simple as wg-easy would be great.

I run wg-easy https://github.com/WeeJeWel/wg-easy for this sort of thing. I use the docker container, and it's great. "Just works".

Also, unrelated, I just decided I don't like the sentiment of "PiMyProjectName" branding. I know most projects don't just run on a Pi, and that the intent is to say "you can self-host thing", but at this point if you want to run a home server sort of thing, just buy some cheap 100-200 dollar minipc thing. That's how much you'd pay for a Pi now anyway, and it comes with such great features as:

* just establishing an ssh connection doesn't take multiple seconds

* the ethernet doesn't go over a usb hub

* it doesn't run on an sd card that is going to fail within a year

I'm pretty dismissive of ARM chips for homelab stuff at this point. There's super cheap minipcs with "real" processors that will just destroy even an expensive ARM board.

Pi's shine with their ability to run both a real/full Linux and also do gpio type stuff that otherwise is usually an arduino board. I don't have anything against low-level programming but damn is it just a lot more fun to do in python. I love the Rpi zero w 2 products for this, just enough juice to run wifi and a python loop, plus the gpio pins. Too bad they've been sold out for literally years.

J'ai installé Wireguard Server sur un VPS en utilisant [https://github.com/weejewel/wg-easy Peer to Peer Ping, mais je ne peux pas ping-ping à des pairs du serveur.

To expand: I'd recommend wireguard it's super easy to run with docker, openvpn is way more annoying to setup The Github page for wg-easy docker image

for wireguard im using wg-easy