That was the route I always thought I had to go, but it’s quite a bit more work/config. One day!

There was actually, cloudflare seemed to not like 2nd level subdomains. So using a wildcard cert for *.foo.bar.com didn’t work for the setup as described in the video, but *.bar.com did.

The other thing was just specific to some of the services I use, like proxmox needed specific NGINX config that I mentioned in this comment. That was it really! DNS and NGINX isn’t that foreign to me so I was comfortable, but it was pretty simple IMO. Give it a shot!

Yup, it’s through Let’s Encrypt. It was a relatively painless setup. I’m quite pleased.

I use a single wildcard cert from CF

Same with this setup, makes it super easy. I don’t use pfSense but someone else in here said they had a similar setup as well. Sounds cool!

the custom domains are very nice! I use homer as a dashboard so I never really needed to memorize the IPs (though I still do), but now it’s even easier

Make sure you enable websockets, I had to do that for a few services like HomeAssistant. Also some things like Proxmox required custom NGINX config for shell consoles to work

proxy_buffers 8 16k;
proxy_buffer_size 32k;

# Make sure not to redirect traffic to a port 4443
port_in_redirect off;

location / {
    proxy_pass          $forward_scheme://$server:$port;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_http_version 1.1;
}