this post was submitted on 14 Dec 2025
25 points (96.3% liked)

Selfhosted

53786 readers
469 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 posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
25
Getting the right setup for Vaultwarden compose.yaml (lemmy.ml)
submitted 6 days ago by trilobite@lemmy.ml to c/selfhosted@lemmy.world
10 comments fedilink hide all child comments
 

I thought that Vaultwarden install was going to be a little simpler but after having consulted a few guides here and there its maybe less straightforward than I thought.

My use-case is to use it on may internal LAN only with not access from outside whatsoever. In theory, http should be fine, but as this tool will contain quite a bit of sensitive data, I can see why it may be a good idea to go https. Are most of you internal users only setting up https?

My network is behind a pfSense setup that uses unbound to resolve all DNS. Locally, all my DNS requests are being forwarded on the subnet I will have Vaultwarden installed.

  • First question is whether for internal network use only, I need to go https.
  • Second question is whether I need to follow this guide?
you are viewing a single comment's thread
view the rest of the comments
[–] trilobite@lemmy.ml 2 points 4 days ago* (last edited 4 days ago)

I'm picking up on this because I'm getting a bit confused. I've run this through docker compose using the below yaml. I've done it as normal user, "Fred" (added to docker group) rather than root (using sudo although it make no difference as I get the same outcome). I normally have a "docker" folder in my /home/fred/ folder so is /home/fred/docker/vaultwarden in this instance (i.e. my data folder is in here).

I get the same issue highlighted here which is all about the SSL_ERROR_RX_RECORD_TOO_LONG when trying to connect via https, whereas when I try to connect via http, I get a white page with Vaultwarden logo in top left corner and the spinning wheel in the center. I've got no proxy enabled and I'm still not clear why I need one if I'm only accessing this via LAN. Is this something on the lines of "you must yse this through a proxy or it won't work" thing? Although that not why I understood the from the guidance. I'm clearly missing something although not sure what exactly it is ....

services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    restart: always
    environment:
      # DOMAIN: "https://vw.home.home/"
      SIGNUPS_ALLOWED: "true"
    volumes:
      - ./vw-data/:/data/
    ports:
      - 11001:80