wg-access-server VS subspace

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

Setup Subspace on a container on your EC2 & utilize wireguard to login

Or the equally simple Subspace [1] if you want to stick with self-hosting Wireguard directly.

[1] - The community fork at least. Upstream is no longer updated: https://github.com/subspacecommunity/subspace

https://github.com/subspacecommunity/subspace#setup

I have been using a $5 vps for setting a simple vpn for family. it is super easy to ru your own vpn now. Some sites dont work because they have dumb ip blocklists but most do or give hcaptcha.

Imo,

I would use WireGuard with a popular front-end and install in on a raspberry pi. At least that was my initial idea. At my work we use https://github.com/subspacecommunity/subspace.

I think it's worth knowing how simple and easy it is to set up wireguard when you don't need a web UI or any of that other fluff on there. It's right in entrypoint.sh[1] and some dockerfiles - set up firewall; set up wireguard devices, keys and configs; set up dnsmasq. Three simple steps on linux or openbsd (Not sure if FreeBSD ever got past that integration issue yet)

[1] https://github.com/subspacecommunity/subspace/blob/master/en...