2
Protect Admin panel by restricting access to only IP LAN
Source: dani-garcia/vaultwarden#2626 · opened by @MilesTEG1
Hello, With the 1.25.1 version of Vaultwarden, my script to enable websocket notifications wasn't working anymore because of some lack of proxy_set_header in my configuration file. I do some research with the wiki, and I have come to change some proxy_set_header according to the wiki. Some explanations first First I have to explain my particular configuration of Vaultwarden. I installed it in docker, on my Synology NAS. I use a domain name, with a valid certificate, so in HTTPS in order to use 2FA for login. I also use the reverse proxy of DSM to serve my services with various domain names like : • vault.mydomain.tld • dsm.mydomain.tld • photos.mydomain.tld • files.mydomain.tld • etc ... The reverse proxy is base on NGINX, but we don't have access to it easily. It needs SSH to the NAS. In order to get the WebSocket Notifications working, I have to launch a bash script searching in the server.ReverseProxy.conf the server line …
No pledges yet. Be the first to back this.
Comments
Similar requests
Move SSO_CLIENT_SECRET to the Read Only Admin Panel or Encrypt it
1 vote · 0 comments
Set different entries for the Admin panel
1 vote · 0 comments
change the port for the admin account
2 votes · 0 comments
Bitwarden Send OTP email verification protection
13 votes · 0 comments
Feature: Auto-provision new users on first SSO login (no manual admin invite required)
1 vote · 0 comments
No comments yet.