For instance how can I use my *.domain.com SSL certs and NPM to route containers to a subdomain without exposing them? The main domain is exposed.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        7
        ·
        edit-2
        4 days ago

        I don’t get it. Npm is a package manager. It doesn’t handle certificates.

        You need a DNS service like route 53 (AWS) or similar where let’s encrypt connects via an API and creates the DNS token.

        • coolie4@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 days ago

          OP isn’t referring to the package manager. They’re talking about Nginx Proxy Manager

          • Possibly linux@lemmy.zip
            link
            fedilink
            English
            arrow-up
            7
            ·
            4 days ago

            Oh

            That makes sense. We need to stop making two things use the same acronym. Its like people saying HA for home assistant without realizing that HA is normally used for high availability.

      • MangoPenguin@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 days ago

        Then you’re all set, issue certs over DNS-01 challenge in NPM, and create records in your local DNS server that point to the NPM IP for each domain you want to use.