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.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Seconding a reverse proxy. Once you have it set up, it's trivial to add a subdomain, forward it to your internal port that your container is exposing, then use certbot or whatever to get a new certificate for that subdomain.
I just use apache because I heavily use it for work, so I already know it well. But lots of people swear by nginx as well. There are lots of other options as well.
No need to get a certificate for ever subdomain, you can get a wildcard cert for *.your. domain.
True. I did that for one of my domains, but it was really quite annoying to do with certbot, as you needed some sort of plugin.
It's fine with Let'sEncrypt via the DNS01 challenge; my lab typically only uses one wildcard certificate for all the services there unless I have a specific need to generate an indovidual cert for a service.
Thirding a reverse proxy. Probably Nginx Proxy Manager (NPM) is the easiest reverse proxy to get started with, if you don't want to deal with plain nginx config files
Here's the secret to stuff like this:
Run a single reverse proxy / edge router for all of your containerised services.
I recommend Traefik - https://gitlab.com/Matt.Jolly/traefik-grafana-prometheus-docker
You can configure services with labels attached to the container and (almost) never expose ports directly. It also lets you host an arbitrary number of services listening on 80/443.
An example config might look like this:
# docker-compose.yml
version: '3.9'
services:
bitwarden:
image: vaultwarden/server:latest
restart: always
volumes:
- /data/vaultwarden/:/data
environment:
# - ADMIN_TOKEN=
- WEBSOCKET_ENABLED=true
networks:
- proxy
labels:
- traefik.enable=true
- traefik.http.routers.bitwarden-ui-https.tls.certresolver=letsencrypt
- traefik.http.middlewares.redirect-https.redirectScheme.scheme=https
- traefik.http.middlewares.redirect-https.redirectScheme.permanent=true
- traefik.http.routers.bitwarden-ui-https.rule=Host(`my.domain.com`)
- traefik.http.routers.bitwarden-ui-https.entrypoints=websecure
- traefik.http.routers.bitwarden-ui-https.tls=true
- traefik.http.routers.bitwarden-ui-https.service=bitwarden-ui
- traefik.http.routers.bitwarden-ui-http.rule=Host(`my.domain.com`)
- traefik.http.routers.bitwarden-ui-http.entrypoints=web
- traefik.http.routers.bitwarden-ui-http.middlewares=redirect-https
- traefik.http.routers.bitwarden-ui-http.service=bitwarden-ui
- traefik.http.services.bitwarden-ui.loadbalancer.server.port=80
- traefik.http.routers.bitwarden-websocket-https.rule=Host(`my.domain.com) && Path(`/notifications/hub`)
- traefik.http.routers.bitwarden-websocket-https.entrypoints=websecure
- traefik.http.routers.bitwarden-websocket-https.tls=true
- traefik.http.routers.bitwarden-websocket-https.service=bitwarden-websocket
- traefik.http.routers.bitwarden-websocket-http.rule=Host(`my.domain.com`) && Path(`/notifications/hub`)
- traefik.http.routers.bitwarden-websocket-http.entrypoints=web
- traefik.http.routers.bitwarden-websocket-http.middlewares=redirect-https
- traefik.http.routers.bitwarden-websocket-http.service=bitwarden-websocket
- traefik.http.services.bitwarden-websocket.loadbalancer.server.port=3012
Using traefik as your first reverse proxy might be a bit daunting. Caddy or "nginx reverse proxy" are much easier to configure.
If you want it beginner friendly, I can recommend nginx proxy Manager, which is basically a web ui frontend for nginx. This has its own drawbacks, but makes setup very uncomplicated.
I agree, very beginner friendly. But also, it's what most people are gonna need.
I actually started with Traefik because I didn't know any better, and I kinda wanna go back to be honest because with Traefik I was able to configure a Minecraft server, without having to expose the port. But not with NGINX Proxy Manager.l, since it only does http and shit. But I REALLY like being able to do everything via a webUI since I only have a phone to manage my server .
So, I find myself stuck between functionality and ease of use. :(
You should look into NPM Streams, they're built exactly for this purpose. It's included by default, just another type of host.
I've tried, but I wasn't able to get it working. I'll look into it again though, cuz I'd love to do it all through NPM.
At the end of the day Traefik isn't that hard, especially if you know the core concepts; if you know both and have a need for Traefik I'd just use that everywhere.
Nginx Proxy Manager can do stream hosts, which are encrypted tunnels where you can put any kind of traffic not just HTTP.
I've tried, but I wasn't able to get it working. I'll look into it again though, cuz I'd love to do it all through NPM.
I use Nginx Proxy Manager to reverse proxy all my services including Vaultwarden -
Setup in NPM -
Open Nginx Proxy Manager Admin Portal
Click Proxy Hosts
Click Add Proxy Host
Fill in the details
Details tab
Domain Names - vault.your.domain
Scheme - http
Forward Hostname/IP - vaultwarden (this should be the name of your vw container)
Forward Port - 80
Tick Block Common Exploits
Tick Websockets Support
Access List - Publicly Accessible
Custom locations tab
Add the following locations
location 1
location - /notifications/hub
Scheme - http
Forward Hostname/IP - vaultwarden
Forward Port - 3012
Click the cog symbol and add the following to the textbox that appears
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
location 2
location - /notifications/hub/negotiate
Scheme - http
Forward Hostname/IP - vaultwarden
Forward Port - 80
Click the cog symbol and add the following to the textbox that appears
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
location 3
location - /
Scheme - http
Forward Hostname/IP - vaultwarden
Forward Port - 80
Click the cog symbol and add the following to the textbox that appears
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
SSL tab
SSL Certificate - Request a new SSL Certificate
tick Use a DNS Challenge (or just expose port 80 if you accept the risk)
DNS Provider - Dynu (this is my dyndns provider)
Credentials File Content - replace YOUR_DYNU_AUTH_TOKEN with the API key from https://www.dynu.com/en-US/ControlPanel/APICredentials
Email Address for Let's Encrypt - your email
Tick I Agree to the Let's Encrypt Terms of Service
Click Save
Vaultwarden should now be accessible via https://vault.your.domain
Can I send you a pm regarding my progress so far? I'm kind off stuck at configuring everything:/
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| IP | Internet Protocol |
| SSL | Secure Sockets Layer, for transparent encryption |
| nginx | Popular HTTP server |
5 acronyms in this thread; the most compressed thread commented on today has 13 acronyms.
[Thread #129 for this sub, first seen 11th Sep 2023, 03:25] [FAQ] [Full list] [Contact] [Source code]