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?

  • @[email protected]English
    3•19 days 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.

      • icedterminalEnglish
        4•19 days 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.

        • @[email protected]English
          1•18 days ago

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

          • icedterminalEnglish
            3•17 days ago

            Some self hosted services refuse to work if you use a self signed certificate with your public facing IP. They only allow self signed certificates when using one of the handful of private addresses.

            Some apps on mobile devices for the service you use won’t work unless a trusted certificate is used. A self signed certificate behind the scenes creates an error that isn’t handled and you can’t connect.

            You lose the ability to have a proxy in front to handle abuse so your server is spared the headache. You need a domain to do this.

            • @[email protected]English
              1•16 days ago

              That’s an ecosystem defect that you need a dns name paid subscription to use “institutionally sanctified” certificates.

              My stuff should be made to still work in the apocalypse when San Francisco and Silicon Valley are underwater radioactive craters.

              • icedterminalEnglish
                1•15 days ago

                It’s an industry security standard. Not a defect. If you don’t agree with it, fork the software and modify it to suit your needs.

      • @[email protected]English
        1•18 days ago

        It makes SSL certs insanely easy. $1 a year is worth it to me to not have to deal with self signed certs.