I’ve been researching different ways to expose Docker containers to the internet. I have three services I want to expose: Jellyfin, Omnivore (Read-it-later app), and Overseerr.

I’ve come across lots of suggestions, like using Nginx with Cloudflared, but some people mention that streaming media goes against Cloudflared tunnel TOS, and instead recommend Tailscale, or Traefik, or setting up a WireGuard VPN, or using Nginx with a WireGuard VPN.

The amount of conflicting advice has left me confused. So, what would be the best approach to securely expose these containers?

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 hours ago

    A public CA (Let’s Encrypt, Komodo, GoDaddy, etc) don’t actually sign certificates with their root CA certificate. The root CA creates a subCA (Or signing CA) that actually generates the certificates and the system holding the private keys of the root certificate is shutdown to prevent access but is brought back online every so often to update the revocation list.

    You said a private CA is more secure so I am wondering how that is?

    • notfromhere@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      Because a private CA allows you to create a certificate and nobody else has the ability to create certificates unless you give them the keys or a signing CA. With Let’s Encrypt, you are trusting every major certificate authority to not create a cert on your domain; coupled with DNS poisoning means you would end up on a legit-looking but counterfeit website of yours.

      • slazer2au@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        Nothing is stopping me from making a certificate from my offline CA for your domain.

        Even if you don’t trust the certificate the traffic is still encrypted.