I want to host a Vaultwarden (or Bitwarden if necessary) instance, but it keeps asking for a domain and a SSL certificate. I dont own a domain and dont want to enable port forwarding on my router to expose it to the outside.

Is it possible to host a instance only internally and access it via the IP or a domain set on my local DNS? How about SSL is it possible and/or necessary?

  • superglue@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 day ago

    Buy an xyz domain for like $1. If you choose a domain that just 9 random numbers its super cheap.

    So something like 123456789.xyz

    Then setup a SWAG container with DNS challenge. Join vaultwarden into the same docker network as SWAG, then add an entry to your router to point to vaultwarden using a subdomain.

      • icedterminal@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        17 hours ago

        TLS.

        While technically you can use TLS with a self signed certificate, it creates additional problems with a public facing service. Only recommended for internal services.

        • interdimensionalmeme
          link
          fedilink
          English
          arrow-up
          1
          ·
          12 hours ago

          Other than having accept a self signed certificate, what’s the problem to using the ip address? Mine hasn’t changed in years.