• vividspecter@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    As a side note, how do people handle HTTPS with private networks (VPN or local) these days? I typically just stick to HTTP, but it would be nice to get rid of the warnings/lock (and I use HTTPS-only mode and firefox seems to require a fresh exception for every port).

    • dustojnikhummer@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Self signed certificates and import CA onto all of my devices.

      Or, public DNS with cloudflare that points to local IP, but you can’t do this with a .local domain

    • the_thunder_god@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Doing what the OP (same result, just different software) or I posted and assigning certificates to secure your local services means you can avoid the HTTPS warning that major browsers will pop up on an unsecure (HTTP) connection. Instead of going to an internal dns name without a certificate or direct to the ip…you assign a wildcard certificate to a domain name you’ve setup on your local dns. You then access that service via the HTTPS protected Domain name, with no warning.