Mind that I am very noob into self-hosting, reverse proxies and the like

When I saw that Caddy automatically handled the HTTPS thingies I was like “this is my moment then to go into self-hosting”. Caddy seemed so simple.

Turns out… I am suddenly discovering that the connection between the caddy machine and the Home Assistant machine (both in the local network) is non-encrypted. So if another appliance in my local network went rogue… bum, all my info gets leaked… right?

This might sound weird because it might actually be super-duper complicated but… how come in 2025 we still don’t auto-encrypt local comms?

Please be kind. Lot’s of love. Hopefully I’ll dig my way to self-hosting wisdom.

  • FlowerFan@piefed.blahaj.zoneEnglish
    4·
    13 hours ago

    if you use a simple
    reverse_proxy service
    it isn’t https. It will make the connection using good old http. If you use
    reverse_proxy https://service
    or
    reverse_proxy service:443
    it will be https (443 is the port for https)

    This does not mean, that any other device can just intercept the packages. It depends on the routing; your router and switches are smart. They know on which cable a device is and only send it to that cable. If anything else is on that cable, they can intercept this message. Any devices not on that cable can’t.

    So if you’re like me and have Caddy and HomeAssistant on the same physical server as virtual machines, you realistically shouldn’t have to worry, as the traffic should never leave your server.