• lemmyvore@feddit.nl
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    If you mean properly signed certificates (as opposed to self-signed) you’ll need a domain name, and you’ll need your LAN DNS server to resolve a made-up subdomain like lan.domain.com. With that you can get a wildcard Let’s Encrypt certificate for *.lan.domain.com and all your https://whatever.lan.domain.com URLs will work normally in any browser (for as long as you’re on the LAN).

    • solrize@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      Right, main point of my comment is that .internal is harder to use that it immediately sounds. I don’t even know how to install a new CA root into Android Firefox. Maybe there is a way to do it, but it is pretty limited compared to the desktop version.

      • cereals@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        You can’t install a root CA in Firefox for android.

        You have to install the cert in android and set Firefox to use the android truststore.

        You have to go in Firefox settings>about Firefox and tap the Firefox logo for a few times. You then have a hidden menu where you can set Firefox to not use its internal trust store.

        You then have to live with a permanent warning in androids quick setting that your traffic might be captured because of the root ca you installed.

        It does work, but it sucks.