I am also using Nginx Proxy Manager to access the vault (without any custom settings). The vault works and I am able to access the passwords. However, my SMTP notifications were not working and on further investigation, I saw the following in the diagnostics screen:
Here's the support string (note that this was generated after adding the ADMIN_TOKEN in the container).
Your environment (Generated via diagnostics page)
Vaultwarden version: v1.23.1
Web-vault version: v2.25.0
Running within Docker: true (Base: Debian)
Environment settings overridden: true
Uses a reverse proxy: true
IP Header check: true (X-Real-IP)
Internet access: false
Internet access via a proxy: false
DNS Check: false
Time Check: true
Domain Configuration Check: false
HTTPS Check: false
Database type: SQLite
Database version: 3.35.4
Clients used:
Reverse proxy and version:
Other relevant information:
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: SIGNUPS_ALLOWED, ADMIN_TOKEN
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @arsaboo on GitHub (Jan 20, 2022).
I am running valutwarden in a docker container (on a Ubuntu machine) using the following command:
I am also using Nginx Proxy Manager to access the vault (without any custom settings). The vault works and I am able to access the passwords. However, my SMTP notifications were not working and on further investigation, I saw the following in the diagnostics screen:
Here's the support string (note that this was generated after adding the
ADMIN_TOKENin the container).Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: SIGNUPS_ALLOWED, ADMIN_TOKEN
I would appreciate any guidance....thanks a lot!