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
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.
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??