Selfhosted

59939 readers

313 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How to host vaultwarden internally (feddit.org)

submitted 2 years ago* (last edited 2 years ago) by Linsensuppe@feddit.org to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

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

[–] prenatal_confusion@feddit.org 3 points 2 years ago (1 children)

I am hosting vaultwarden locally (docker) and just don't use the Webinterface. The Firefox addon and the bitwarden desktop tool work just fine. Also the android app syncs.

[–] tuhriel@infosec.pub 1 points 1 year ago (1 children)

Interesting, for me the apps required to have a valid tls cert.

[–] prenatal_confusion@feddit.org 1 points 1 year ago

That's strange. It's working with the IP and port and explicitly removing the s from https im the setup screen. It is sneaky about the s.