manual-connections VS ZudVPN

Nope, those are here but they're clunky as heck

I don't know what to do with these PIA github files. https://github.com/pia-foss/manual-connections

WireGuard is much faster for me. See here for PIA and 3rd party scripts which can be used to create WireGuard config files.

There's a separate API you need to use after the link is up

If you're running a Linux server and want to automate it, PIA's automated connection scripts are here, and this script automatically runs those scripts, grabs the forwarded port and updates the config of your favorite client, then starts it.

I'm a bit partial to doing vpn with foss protocol and clients, without gui applications at all on mac and linux. PIA provides some nice resources to that end on their foss github page.

I set up PIA on my Ubuntu Server (which does not run 24/7) using the official Manual Connections repository, however with WireGuard, the authentication token runs out for me after a few days (since it expires when my server is turned off, then it can't get a new token when it turns back on), is there any way I can prevent this? It was working perfectly before the access token expired :p

https://github.com/pia-foss/manual-connections lists several, including mine

It's a bit of a pain in the butt, but I used the PIA manual connection script to generate a wireguard config file, and then I plugged that into gluetun and now it works great. Was easier than trying to config OpenVPN

I am creating an open source VPN application for mobile phones (iOS, Android) and a chrome extension as a proxy. I wonder what features people expect from a VPN.

My MVP is that the app will functions as a VPN launcher on user's preferred Cloud Provider like Amazon Web Services, Google Cloud Platform, Microsoft Azure, DigitalOcean, Vultr and any other major cloud provider that offers API access.

Features, I envision to add are: Ad-blocking by DNS, VPN Kill Switch, Static IP (if provider has it), IKEv2 IPSec-based VPN solution like strongSwan, and since the server belongs to the user, I plan to add a Terminal right in the app so that the user could connect and do anything they want.

Since the app is an open-source I pushed initial PR to GitHub so that anyone can scrutinize the code: https://github.com/zudvpn/zudvpn

- In your components, just call `useStore` hook and require whatever state property you need: https://github.com/zudvpn/ZudVPN/blob/master/src/screens/MainScreen/index.tsx#L13

GitHub: https://github.com/zudvpn/ZudVPN

When I first started on react native I used react-native-navigation and never looked back. I don't have any experience with react-navigation. So far I can't complain about react-native-navigation on https://github.com/zudvpn/ZudVPN

When using random VPN are you sure the risk is not owned by you? Here is the cloud config init data that is used to create the server: https://github.com/zudvpn/ZudVPN/blob/master/src/providers/DigitalOcean/cloudconfig.tsx Feel free to see if it's worth the risk or not.