Played with it. At least I don’t have these entries on my log. But it’s information only about connection from local IP 192.168.1.99
that should be fine. Are you able to access Vaultwarden locally using http://you.ip.address:8001 now??
My Nginx setup as follow
nano /etc/nginx/sites-dietpi/vaultwarden.conf
added following
location / {
proxy_http_version 1.1;
proxy_set_header "Connection" "";
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;
proxy_pass http://you.ip.address:8001;
}
location /notifications/hub/negotiate {
proxy_http_version 1.1;
proxy_set_header "Connection" "";
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;
proxy_pass http://you.ip.address:8001;
}
location /notifications/hub {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Forwarded $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://you.ip.address:3012;
}
next, remove root locating from default config file to avoid duplicate location /
nano /etc/nginx/sites-available/default
mark lines for location / using #
# location / {
# try_files $uri $uri/ =404;
# }
Restart Nginx and you should be done
systemctl restart nginx.service