this post was submitted on 22 Dec 2024
37 points (97.4% liked)

Selfhosted

59939 readers
344 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] SirMaple__@lemmy.world 25 points 2 years ago

You can use any domain you like. I personally have an actual domain that I only use inside my network. This way I can get SSL certs from Let's Encrypt using the DNS challenge which doesn't require any ports being opened. You can use self signed certs but I would strongly suggest using certs from the likes of Let's Encrypt.

Here are 2 pages on this subject

https://github.com/dani-garcia/vaultwarden/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome

https://github.com/dani-garcia/vaultwarden/wiki/Enabling-HTTPS