Thx! I´ve done it. Now Nginx is working
let’s verify LISTEN ports
ss -tulpn | grep LISTEN
tcp LISTEN 0 32 0.0.0.0:53 0.0.0.0:* users:(("pihole-FTL",pid=493,fd=5))
tcp LISTEN 0 1000 0.0.0.0:22 0.0.0.0:* users:(("dropbear",pid=313,fd=4))
tcp LISTEN 0 256 127.0.0.1:5335 0.0.0.0:* users:(("unbound",pid=498,fd=4))
tcp LISTEN 0 256 127.0.0.1:8953 0.0.0.0:* users:(("unbound",pid=498,fd=6))
tcp LISTEN 0 511 0.0.0.0:443 0.0.0.0:* users:(("nginx",pid=579,fd=8),("nginx",pid=578,fd=8),("nginx",pid=577,fd=8),("nginx",pid=576,fd=8),("nginx",pid=575,fd=8))
tcp LISTEN 0 1024 127.0.0.1:8000 0.0.0.0:* users:(("vaultwarden",pid=582,fd=34))
tcp LISTEN 0 5 127.0.0.1:4711 0.0.0.0:* users:(("pihole-FTL",pid=493,fd=10))
tcp LISTEN 0 4096 0.0.0.0:9002 0.0.0.0:* users:(("docker-proxy",pid=828,fd=4))
tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=579,fd=5),("nginx",pid=578,fd=5),("nginx",pid=577,fd=5),("nginx",pid=576,fd=5),("nginx",pid=575,fd=5))
tcp LISTEN 0 32 [::]:53 [::]:* users:(("pihole-FTL",pid=493,fd=7))
tcp LISTEN 0 1000 [::]:22 [::]:* users:(("dropbear",pid=313,fd=5))
tcp LISTEN 0 256 [::1]:8953 [::]:* users:(("unbound",pid=498,fd=5))
tcp LISTEN 0 511 [::]:443 [::]:* users:(("nginx",pid=579,fd=7),("nginx",pid=578,fd=7),("nginx",pid=577,fd=7),("nginx",pid=576,fd=7),("nginx",pid=575,fd=7))
tcp LISTEN 0 5 [::1]:4711 [::]:* users:(("pihole-FTL",pid=493,fd=15))
tcp LISTEN 0 4096 [::]:9002 [::]:* users:(("docker-proxy",pid=835,fd=4))
tcp LISTEN 0 511 [::]:80 [::]:* users:(("nginx",pid=579,fd=6),("nginx",pid=578,fd=6),("nginx",pid=577,fd=6),("nginx",pid=576,fd=6),("nginx",pid=575,fd=6))
Yes i´m able to reach it.
I did follow the steps, but Vaultwarden isn’t available from inside
How are you trying to reach Vaulwarden now? Can you check logs
journalctl -u vaultwarden.service
-- Journal begins at Sat 2023-02-25 01:10:41 CET, ends at Sat 2023-02-25 23:10:3 2 CET. --
Feb 25 01:11:23 DietPi systemd[1]: Started vaultwarden (DietPi).
Feb 25 01:11:23 DietPi vaultwarden[599]: /-------------------------------------- ------------------------------\
Feb 25 01:11:23 DietPi vaultwarden[599]: | Starting Vault warden |
Feb 25 01:11:23 DietPi vaultwarden[599]: |-------------------------------------- ------------------------------|
Feb 25 01:11:23 DietPi vaultwarden[599]: | This is an *unofficial* Bitwarden imp lementation, DO NOT use the |
Feb 25 01:11:23 DietPi vaultwarden[599]: | official channels to report bugs/feat ures, regardless of client. |
Feb 25 01:11:23 DietPi vaultwarden[599]: | Send usage/configuration questions or feature requests to: |
Feb 25 01:11:23 DietPi vaultwarden[599]: | https://vaultwarden.discourse.group / |
Feb 25 01:11:23 DietPi vaultwarden[599]: | Report suspected bugs/issues in the s oftware itself at: |
Feb 25 01:11:23 DietPi vaultwarden[599]: | https://github.com/dani-garcia/vaul twarden/issues/new |
Feb 25 01:11:23 DietPi vaultwarden[599]: \-------------------------------------- ------------------------------/
Feb 25 01:11:23 DietPi vaultwarden[599]: [INFO] No .env file found.
Feb 25 01:11:24 DietPi vaultwarden[599]: [2023-02-25 01:11:24.034][vaultwarden:: api::notifications][INFO] Starting WebSockets server on 0.0.0.0:3012
Feb 25 01:11:24 DietPi vaultwarden[599]: [2023-02-25 01:11:24.060][start][INFO] Rocket has launched from http://127.0.0.1:8000
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.149][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57605
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.168][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57606
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.177][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57607
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.187][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57608
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.197][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57609
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.206][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57610
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.214][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57611
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.221][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57612
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.230][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57613
Feb 25 01:15:18 DietPi vaultwarden[599]: [2023-02-25 01:15:18.241][vaultwarden:: api::notifications][INFO] Accepting WS connection from 192.168.178.38:57614
Feb 25 01:16:07 DietPi vaultwarden[599]: [2023-02-25 01:16:07.957][rocket::serve r][WARN] Received SIGTERM. Requesting shutdown.
Feb 25 01:16:07 DietPi systemd[1]: Stopping vaultwarden (DietPi)...
Feb 25 01:16:07 DietPi vaultwarden[599]: [2023-02-25 01:16:07.958][vaultwarden][ INFO] Vaultwarden process exited!
Feb 25 01:16:07 DietPi systemd[1]: vaultwarden.service: Succeeded.
Feb 25 01:16:07 DietPi systemd[1]: Stopped vaultwarden (DietPi).
Feb 25 01:16:07 DietPi systemd[1]: Started vaultwarden (DietPi).
Feb 25 01:16:08 DietPi vaultwarden[1865]: /------------------------------------- -------------------------------\
Feb 25 01:16:08 DietPi vaultwarden[1865]: | Starting Vaul twarden |
Feb 25 01:16:08 DietPi vaultwarden[1865]: |------------------------------------- -------------------------------|
Feb 25 01:16:08 DietPi vaultwarden[1865]: | This is an *unofficial* Bitwarden im plementation, DO NOT use the |
Feb 25 01:16:08 DietPi vaultwarden[1865]: | official channels to report bugs/fea tures, regardless of client. |
Feb 25 01:16:08 DietPi vaultwarden[1865]: | Send usage/configuration questions o r feature requests to: |
Feb 25 01:16:08 DietPi vaultwarden[1865]: | https://vaultwarden.discourse.grou p/ |
Feb 25 01:16:08 DietPi vaultwarden[1865]: | Report suspected bugs/issues in the software itself at: |
Feb 25 01:16:08 DietPi vaultwarden[1865]: | https://github.com/dani-garcia/vau ltwarden/issues/new |
Feb 25 01:16:08 DietPi vaultwarden[1865]: \------------------------------------- -------------------------------/
Feb 25 01:16:08 DietPi vaultwarden[1865]: [INFO] No .env file found.
Feb 25 01:16:08 DietPi vaultwarden[1865]: [2023-02-25 01:16:08.113][vaultwarden: :api::notifications][INFO] Starting WebSockets server on 0.0.0.0:3012
Feb 25 01:16:08 DietPi vaultwarden[1865]: [2023-02-25 01:16:08.119][start][INFO] Rocket has launched from http://127.0.0.1:8000
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.532][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57666
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.541][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57667
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.549][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57668
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.555][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57669
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.562][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57670
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.571][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57671
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.577][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57672
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.586][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57673
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.592][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57674
Feb 25 01:18:02 DietPi vaultwarden[1865]: [2023-02-25 01:18:02.601][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57675
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.390][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57714
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.397][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57715
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.405][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57716
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.413][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57717
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.422][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57718
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.430][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57719
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.438][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57720
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.445][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57721
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.453][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57722
Feb 25 01:19:54 DietPi vaultwarden[1865]: [2023-02-25 01:19:54.460][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.38:57723
Feb 25 01:46:30 DietPi vaultwarden[1865]: [2023-02-25 01:46:30.349][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:60740
Feb 25 01:46:30 DietPi vaultwarden[1865]: [2023-02-25 01:46:30.362][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:60752
Feb 25 01:46:30 DietPi vaultwarden[1865]: [2023-02-25 01:46:30.381][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:60762
Feb 25 01:46:31 DietPi vaultwarden[1865]: [2023-02-25 01:46:31.489][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:60770
Feb 25 01:46:31 DietPi vaultwarden[1865]: [2023-02-25 01:46:31.489][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:60772
Feb 25 01:46:36 DietPi vaultwarden[1865]: [2023-02-25 01:46:36.536][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:43240
Feb 25 01:46:36 DietPi vaultwarden[1865]: [2023-02-25 01:46:36.558][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:43252
Feb 25 20:11:28 DietPi vaultwarden[1865]: [2023-02-25 20:11:28.658][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:36654
Feb 25 20:11:28 DietPi vaultwarden[1865]: [2023-02-25 20:11:28.662][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:36668
Feb 25 20:11:29 DietPi vaultwarden[1865]: [2023-02-25 20:11:29.895][vaultwarden: :api::notifications][INFO] Accepting WS connection from 192.168.178.30:36670
Are you sure you did nothing in addition to steps 5-9? Because Vaultwarden has been adjusted to listen to localhost 127.0.0.1 only and not to local network anymore. Therefore you are not able to each it actually.
Which btw, is perfect for the configuration of a revers proxy 
Next step would be to create /etc/nginx/sites-dietpi/vaultwarden.conf and to adjust /etc/nginx/sites-available/default as describe on How to setup vaultwarden - #19 by Joulinar
1 Like
That would be my perfect setup!
So i did that! So inserted that config into the file with my IP adress and uncommented /etc/nginx/sites-available/default
usually, you would need to use 127.0.0.1 if both Nginx as well as Vaultwarden running on same system. Because Vaultwarden is listen to that IP only.
Okay! Thanks for your help! 
I’m not an expert programmer. I configured nginx as a reverse proxy for adguard home, phpmyadmin, nextcloud and vaultwarden, following your precious advice. After uploading the vaultwarden configuration, I can no longer host a website. the web page gives me a 404 error.
If I uncomment the default file at the location / lines of the default file in the sites enabled folder, as suggested for the configuration for vaultwarden, the website is reachable but not the vaultwarden login page.
Sorry for my English.
Maybe you can share the configuration you are using. That would be helpful.
I use the configuration proposed by anarchy wisely.
this step disable host of web site .
This is going to remove configuration for root directory. Do you like to use a sub path or sub domain or how should the URL looks like for Vaultwarden??
How can I reach both the website and the vaultwarden login page?