Lem453

This is for traefik but might help to understand the process and change it for caddy

You should have

Service.local.domain.com

For local only services (Vaultwarden) and

Service.domain.com

For external things (immich)

I’m your router / Pihole locally, you setup the above URLs to point to the IP of caddy

I did this using a POE switch to both power the cameras and also have that entire switch on a VLAN. On my OPNSense, that vlan only has permission to send or recieve packets to home assistant which is on my main LAN. They have no other access to anything including each other on the camera vlan.

Other than the initial setup, the only interaction I have with the cameras is via home assistant. This allows them to be completely isolated and still have remote access as per usual with home assistant.

My HA is using the all in one VM setup on Proxmox. I would highly recommend HA installed as a VM rather than Docker due to the ease if installing plugins. After that the above setup will keep your IOT devices nicely isolated.

This is traefik, but its worth watching this because local SSL and external SSL setup is amazing and highly versatile for homelab

youtu.be/liV3c9m_OX8

If anyone’s Firefox auto updated like mine you can uninstall the extension, go to the Bitwarden extension page on the Firefox website and manually install the old version. Only needed if you can’t update vaultwarden right away.

If you check the github discussion from the devs that patched the issue it doesn’t seem intentional to me (not an expert). That being said I assumed the same thing.

My browser auto updated the extension at a very inopportune time and from some reason KDE connect from my phone to computer which is usually very reliable also wouldn’t connect. Was quite annoying until I realized I can just log into the vaultwarden website directly. I don’t think I’ve done that in years

Keeping 80 open is useful so that traefik can redirect all traffic to 443 (https)