i've played around on the demo instance and could not get invite links to work. OP (and me) want it account/login-free. Maybe allow_guest_users it not enabled on the demo instance. When i open an invite link, a login dialog is presented (i simply expect the selection of a user account).
I haven't tried WG on 443/udp yet. On my last UK journey I had it on the default WG port and it was blocked a few times.
Will try 443/udp @ homelab next time. Every other advanced obfuscating solution sounds pretty complicated and I'm not sure if there will be time to handle this during a journey.
I think I will stick to wireguard on port 443/udp. Hope UDP is open in strict networks. Maybe someone hasn't heard of HTTP/3.
Everything else sounds not necessary because I don't travel to china or similar. stunnel needs termux on android in-between? This adds too many moving parts IMO.
AmneziaWG will enter wg-easy in v16 and WG Tunnel already supports it. Don't know how hard it it to configure, but the Jc, Jmin, Jmay, ... settings in WG Tunne look confusing.
it logs out stats ever 6h. The last on my VPS were: 2,7 Gb IN and 120,5 Mb OUT.
So in 30 Days it would be around 243 Gb IN and 10 Gb OUT Traffic.
And do you have any legal implication for doing that ?
i run it since years on two Hetzner VPS in Falkenstein, Germany and didn't get any compains.
The security concerns for the Snowflake proxy operator are minimal. The Snowflake client will not be able to interact with your computer in any way or observe your network traffic, and you will not be able to see their traffic. From the perspective of your ISP it will look like you are connecting to a Tor bridge, which if you are running a Snowflake proxy should be legal and unrestricted in your country. There is no more risk running a Snowflake proxy than running Tor browser.
Zero-config auto-discovery for Docker and Kubernetes. Every container is tracked the moment it starts — state changes, health checks, restart loops, log streaming with stdout/stderr demux. Compose projects are auto-grouped. Kubernetes workloads (Deployments, DaemonSets, StatefulSets) are first-class citizens.
config based on labels. sounds good for a moving selfhosting world...
i've played around on the demo instance and could not get invite links to work. OP (and me) want it account/login-free. Maybe allow_guest_users it not enabled on the demo instance. When i open an invite link, a login dialog is presented (i simply expect the selection of a user account).