jeff/portioner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

config: Change Vaultwarden port to 8020 to avoid conflicts

Browse Source
This commit is contained in:
Jeff Cheng
2026-02-22 15:47:35 -05:00
parent 880cc24bde
commit e6cbe70836
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
vaultwarden/SETUP.md
View File

@@ -36,7 +36,7 @@ Vaultwarden is a lightweight, community-driven server implementation of the Bitw
### Deploy Stack ### Deploy Stack
- [ ] **Action**: Create a new stack named `vaultwarden-stack`. - [ ] **Action**: Create a new stack named `vaultwarden-stack`.
- [ ] **Action**: Paste the content of `docker-compose.portainer.yml` and deploy. - [ ] **Action**: Paste the content of `docker-compose.portainer.yml` and deploy.
- [ ] **Verification**: Access the Vaultwarden Web UI at `http://[NAS_IP]:8080`. - [ ] **Verification**: Access the Vaultwarden Web UI at `http://[NAS_IP]:8020`.
## 4. Post-Setup Security (Crucial) ## 4. Post-Setup Security (Crucial)
1. **Create your account**: Navigate to the Web UI, click "Create Account", and register your master email and password. 1. **Create your account**: Navigate to the Web UI, click "Create Account", and register your master email and password.

2
vaultwarden/docker-compose.portainer.yml
View File

@@ -24,6 +24,6 @@ services:
volumes: volumes:
- /volume1/docker/vaultwarden/data:/data:rw - /volume1/docker/vaultwarden/data:/data:rw
ports: ports:
- "8080:80" # Web UI - "8020:80" # Web UI
# Note: Vaultwarden integrates the WebSocket server into the main process in recent versions, # Note: Vaultwarden integrates the WebSocket server into the main process in recent versions,
# so exposing port 3012 is no longer required for typical setups unless using reverse proxy splitting. # so exposing port 3012 is no longer required for typical setups unless using reverse proxy splitting.