I have a PC I have installed Portainer on, with various docker services (home assistant, jellyfin, etc…) with an ISP supplied router fixing various device IP addresses and reaching out to dyndns.

I really want to move everything over to HTTPS connections by supplying certificates, tls termination, etc .
The issue I have is self signed certificates mean I have to manage certificate deployment to everything in the house.

I figure I need to link a domain to the DynDNS entry and arrange certs for the domain. However I can’t make the link function and everywhere wants >£100 to generate a certificate.

How are people solving this issue?

  • Croquette@sh.itjust.works
    1·
    1 year ago

    I am new at this, but from my understanding, if you want to not expose anything to internet, you would need to create your own CA server to create your own certificates and have the necessary encryption certs for your own https on your home lab.

    • ripcord@kbin.social
      2·
      1 year ago

      That’s essentially what I ended up having to do, but keep hoping that I’ve missed something.

      I also find that people seem to ignore this route, assuming people are fine with public dns pointing at your home ip and http/https ports open.

      • wagesj45@kbin.social
        21·
        1 year ago

        Gotta live on the edge, man. Open up your router. All ports. Firewalls are for pansies. Connect your laptop directly to the modem. Enable ssh and rdp. What could go wrong?

      • Croquette@sh.itjust.works
        1·
        1 year ago

        You can setup a VPS between the internet and your home network to limit the exposition of your home network. When a client pings yourdomain.com, it sees the ip of the VPS and not the IP of your home network.

        Otherwise, a VPN + home CA server will make your home network accessible and encrypted as well