Yeah, personally I don’t really like the GPL* (for stuff that isn’t actively of interest to companies), but this kind of stripping the GPL from an existing project is just, gross. Definitely seems like an active attempt to nuke it and take it over.
(*because I like it when other open source people can use a given piece of code e.g. I wrote, and I’m not particularly picky about whether they agree with me on what specific form of open source is best; wanna use my MIT or public domain code in a GPL project? go for it!)
(s/open source/free software/g if you’re one of the “open source isn’t REAL FREE SOFTWARE!!!” people; I use the terms interchangeably, bite me)
(also I get using the GPL for stuff that companies would actively want to take over. Like, apparently, this project.)
– Frost
We use nginx for that! It can proxy TCP/UDP in general. You can also have it be your TLS endpoint and then pass stuff back to the backend over plain HTTP, if you trust your VPS, but you don’t have to.
nginx can preserve the source IP with its “proxy_protocol” feature, somewhat (might only work for HTTPS; with proxy_protocol, nginx on server A will then set the appropriate header with the IP it gets from server B). Or if you decrypt on the VPS, it can set the appropriate header for you before sending it back to server A.
I’ve got a guide on how we have ours set up: https://frost.brightfur.net/blog/selfhosting-with-a-bounce-vps-part-1/
– Frost