openvpn-install VS algo

https://github.com/angristan/openvpn-install or if you want to be free from your distro's OpenSSL version: https://github.com/ix-ai/openvpn (recommended, just rebuild the container if it becomes outdated)

Buy your own cloud server and run https://github.com/angristan/openvpn-install to make it TCP over 443

Hey! I set up an OpenVPN Server on an Ubuntu Server VM inside ESXi 6.7 using this script: https://github.com/angristan/openvpn-install I need to access the local services running on the, e.g. 192.168.xxx.xxx, which works just fine. But I dont want all my network traffic being routed through the VPN Server. So if i reach out to 192.168.xxx.xxx I get the Service running on this IP in the local network where the server is in, but if I try to reach e.g. google.com the request does not get routed through the VPN. How can I achieve this? OpenVPN-Host: Ubuntu Server 22.04.3 LTS | OpenVPN 2.5.5 Connecting Client: EndeavourOS | OpenVPN 2.6.6

EDIT: I should add that the setup was done with angristan's OpenVPN installer. There's nothing particularly interesting about the conf files.

Very good, does it support https://github.com/angristan/openvpn-install ?

Pretty trivial actually. I set up my server on a VPS with https://github.com/angristan/openvpn-install, it generates the configs that I deployed to my devices, and when connected they can see each other. For resolving the domain name you'd need to set up the DNS during the wizard.

Since we're already presuming you have a functional PFSense box with Wireguard installed and a VPS stood up, now you need to get Algo installed on the VPS. I'm not going to write this part out in detail, but basically you need to follow the procedures here to get Algo installed. However, *before* running ./algo you probably want to edit some of the config.cfg settings. I disabled IPSec (which saves a bunch of package installs and prevents a bunch of failures I saw on some of my VPSs), set my reduce_mtu setting to 80 just to prevent any MTU issues down the line, turned off DNS encryption, and renamed my users to the servers in question (for example: pfsense, vps_server, etc)

Check out the command line args for Auto1111, it talks about a gradio setup that can be accessed remotely. There's a time limit on gradio links though, I think. You could also set up a vpn that will allow you to access your PC remotely, then run A1111 with the --listen command and access it that way. I've done this with an Algo VPN on Azure and a Wireguard client for Windows for Android, but any VPN that lets you access your PC remotely would work.

One way you could try to get around is building your own VPN service, like this: https://github.com/trailofbits/algo/blob/master/README.md

Things I have tried so far: Clear network cache and reset adapters - IDK it fix aprevious problem I had https://github.com/trailofbits/algo/discussions/14504

(I can simply install Algo and get the Wireguard tunnel working, easy peasy... But from there, I can never get Plex port 32400 open... so I'm just trying from scratch now...)

Maybe try running algo vpn (following the road-warrior setup) in a VM instead? It has very light requirements. https://github.com/trailofbits/algo/blob/master/docs/deploy-to-ubuntu.md