admin page still active after commenting out ADMIN_TOKEN in docker-compose #1176

Closed
opened 2026-02-05 00:14:12 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @degrashopper on GitHub (Dec 21, 2021).

Subject of the issue

admin page

Deployment environment

  • vaultwarden version: 1.23.1
  • Install method: docker

  • Clients used: desktop, android

  • Reverse proxy and version: traefik v2.5.4

  • MySQL/MariaDB or PostgreSQL version: SQLite

  • Other relevant details:

Steps to reproduce

comment out ADMIN_TOKEN under vaultwarden in docker-compose and restart the container.

Expected behaviour

/admin page should not exist after commenting out ADMIN_TOKEN

Actual behaviour

/admin page is still visitable

Troubleshooting data

Originally created by @degrashopper on GitHub (Dec 21, 2021). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue admin page ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.23.1 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker * Clients used: desktop, android * Reverse proxy and version: traefik v2.5.4 * MySQL/MariaDB or PostgreSQL version: SQLite * Other relevant details: ### Steps to reproduce comment out ADMIN_TOKEN under vaultwarden in docker-compose and restart the container. ### Expected behaviour /admin page should not exist after commenting out ADMIN_TOKEN ### Actual behaviour /admin page is still visitable ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Author
Owner

@BlackDex commented on GitHub (Dec 21, 2021):

You probably have saved some settings via the /admin interface before, which creates a config.json which overrules the ENV variables including the ADMIN_TOKEN.

Either delete that file, or empty that out via the /admin interface.

@BlackDex commented on GitHub (Dec 21, 2021): You probably have saved some settings via the /admin interface before, which creates a `config.json` which overrules the ENV variables including the `ADMIN_TOKEN`. Either delete that file, or empty that out via the /admin interface.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1176