Selfhosted

53767 readers

384 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 posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

[–] N0x0n@lemmy.ml 2 points 4 days ago (1 children)

Time to learn how to use one :) ! I always use https for all my services in my LAN with a local certificate authority !

I can access all my services with a LAN domaine like the following: https://*.home.lab

The reverse proxy allows to listen on 80 and 443 and forward your traffic to your specific service (https://vaultwarden.home.lab/) and back without the need to fiddle arround with ports and IPs. Thus avoiding port collision if 2 services are listening on the same port !

May I suggest Traefik if you go the docker route? Nginx is also a good solution but way more complex to setup.

[–] trilobite@lemmy.ml 2 points 4 days ago

I hadn't considered the port conflict issue ... probably shows how ignorant I am on all this stuff, not just on proxies ... :-)