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?
If it’s just a bunch of numbers, why not just use the ip address?
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.
Other than having accept a self signed certificate, what’s the problem to using the ip address? Mine hasn’t changed in years.
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.
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.
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.
You mean fork every https browser and server? With hookers and blackjack too?
It makes SSL certs insanely easy. $1 a year is worth it to me to not have to deal with self signed certs.
SSL