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?

  • stevecrox@kbin.socialOP
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Is there any guide on the CName stuff?

    I setup a simple hello world which could be accesseed via the dyndns addeess, bur the cname settings would error

    • nalyd@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      It would come down to the specific DNS provider you’re using and what their GUI is like. in theory CNAMEs are dead simple though.

      DNS names are just stored as text, so if you use tools like mxtoolbox you can see the DNS records for a given site. Following the standard text format, a CNAME formatted like below would create www.example.net that would use the IP address from www.example.com

      www.example.net. CNAME www.example.com.