My setup is similar. My main “desktop” is a Slackware VM through VNC/guacamole.

Cloudflare zero trust tunnel might be up your alley. Look into that. It’s free but has privacy concerns so do your homework.

It was me. Guess what I’ll be doing today.

This is the way.

Forgive my stupidity, but couldn’t you just use split-horizon DNS and have your internal DNS resolve to your homelab instead of the VPS? Personally, that’s what I’ve done. So external lookups for sub.domain.tld go one way and internal lookups go to 10.10.10.x.

So, docker networking uses it’s own internal DNS. Keep that in mind. You can create (and should) docker networks for your containers. My personal design is to have only nginx exposing port 443 and have it proxy for all the other containers inside those docker networks. I don’t have to expose anything. I also find nginx proper to be much easier to deal with than using NPM or traefik or caddy.

Why did you register two separate domains instead of using a wildcard cert from LE and just using subdomains?

Unfortunately, I couldn’t get ChatGPT to write correct Python code for my ESP32 project. I got no problem just writing a bash script to email me.

This is what I ended up going with. I’ll just have to keep an eye on disk space.

I’ll have to check this out. Have you run this in a container or just a native app?

And just like other posters, don’t keep anything you can’t lose on it. I keep my matrix homeserver there but have a backup and some other containers that if they get lost, no biggie. I’ve only had mine for ~6mos or so but haven’t had any issues.

Kind of. I’m thinking something along the lines of sonarr/radarr/etc but with the ability to play/stream the podcast instead of downloading it. I tend to use web interfaces of stuff like that at work and can’t really use my phone. Maybe I’ll have to look into a roll-your-own solution using some existing stuff. Was hoping I wouldn’t have to.

Having your ISP do your port forwarding seems alien to me as that’s not the norm where I am. Since it seems like a standard thing where you are, you may run the risk of another ISP doing the same thing. Personally, if the price is right, I’d take the latency hit and get a VPS and route all inbound traffic through that via wireguard.