algo VS wireguard-install

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

Btw you can try this script..

If you want an easy setup I suggest using a script like this. Even a novice should be able to set up Wireguard in about half an hour - assuming they already have a DynDNS service set up.

Really depends on what you want to do. I run an Ubuntu server VM with Wireguard (my preferred script) , an openmediavault VM to take care or my NAS, HDDs (SATA controller is passed through) with mergerFS+Snapraid) and it also serves as my docker host, pihole VM for DNS (also allows you create your own, local DNS entries so you do not have to use the device's IP)

Yes, and no. Server security is a rather complex topic and covering it in a few sentences is impossible. Try to expose as few of your services as possible to the open web and also ensure they are well maintained - on your side (AKA update your stuff regular) and on the dev side. Seeing that the last github update was over ~6 months ago likely means there are unmitigated security risks. You can expect large projects like Plex, Nextcloud, Bitwarden(Vaultwarden), and others to be built well enough that they do not pose a significant risk. Anything else should only be accessible over a VPN. I am not talking about the commercial ones like PIA or NordVPN. These are mainly useful to circumvent geo restrictions, get better peering, and some other stuff. In terms of security, it does almost nothing despite what the ads claim. What I am talking about is running your own VPN server. Easily doable when you run a home server anyway by running a Wireguard script. By connecting to it remotely you will be able to access your home network as if you were at home although a bit bandwidth limited due to slow internet connections.

but if you don't then this is probably fine as well but I never used it https://github.com/angristan/wireguard-install

I personally use this script to setup a wireguard server. Doing it by hand is totally possible but this makes things a bit easier.

I do the same with Amazon and haven't had any issues. I run wireguard on an Amazon instance with the following script: https://github.com/angristan/wireguard-install