wireguard-install VS wg-access-server

Btw you can try this script..

If you want an easy setup I suggest using a script like this. Even a novice should be able to set up Wireguard in about half an hour - assuming they already have a DynDNS service set up.

Really depends on what you want to do. I run an Ubuntu server VM with Wireguard (my preferred script) , an openmediavault VM to take care or my NAS, HDDs (SATA controller is passed through) with mergerFS+Snapraid) and it also serves as my docker host, pihole VM for DNS (also allows you create your own, local DNS entries so you do not have to use the device's IP)

Yes, and no. Server security is a rather complex topic and covering it in a few sentences is impossible. Try to expose as few of your services as possible to the open web and also ensure they are well maintained - on your side (AKA update your stuff regular) and on the dev side. Seeing that the last github update was over ~6 months ago likely means there are unmitigated security risks. You can expect large projects like Plex, Nextcloud, Bitwarden(Vaultwarden), and others to be built well enough that they do not pose a significant risk. Anything else should only be accessible over a VPN. I am not talking about the commercial ones like PIA or NordVPN. These are mainly useful to circumvent geo restrictions, get better peering, and some other stuff. In terms of security, it does almost nothing despite what the ads claim. What I am talking about is running your own VPN server. Easily doable when you run a home server anyway by running a Wireguard script. By connecting to it remotely you will be able to access your home network as if you were at home although a bit bandwidth limited due to slow internet connections.

but if you don't then this is probably fine as well but I never used it https://github.com/angristan/wireguard-install

I personally use this script to setup a wireguard server. Doing it by hand is totally possible but this makes things a bit easier.

I do the same with Amazon and haven't had any issues. I run wireguard on an Amazon instance with the following script: https://github.com/angristan/wireguard-install

I tried them all. I settled on wg-access-server.

Yes, at my startup we run https://github.com/Place1/wg-access-server inside our kubernetes clusters to give engineers access to local pods vs the k8s DNS (.svc.cluster.local). It works relatively well but we've had to make a couple modifications:

1. I had to deploy CoreDNS to our cluster and set up DNS query rewriting to redirect queries from .cluster.mystartup to *.svc.cluster.local because docker on OS X has issues resolving hostnames that end in .local

What is the difference from https://github.com/Place1/wg-access-server ?

Not sure why this is downvoted. I use a similar service that runs in docker just fine. https://github.com/Place1/wg-access-server