starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #6373] After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel. #2412

New issue

Closed

opened 2026-03-03 02:18:04 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:18:04 +03:00

Owner

Originally created by @jy00295017 on GitHub (Oct 19, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6373

Prerequisites

I have searched the existing Closed AND Open Issues AND Discussions
I have searched and read the documentation

Vaultwarden Support String

After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel.

docker run -d
--name vaultwarden
--restart=unless-stopped
-p 60854:80
-p 60855:3012
-v /Users/development/docker/vaultwarden/data:/data
-e TZ=Asia/Shanghai
-e SHOW_PASSWORD_HINT=false
-e LOGIN_RATELIMIT_MAX_BURST=10
-e LOGIN_RATELIMIT_SECONDS=60
-e ADMIN_TOKEN=$(openssl rand -base64 48)
-e ADMIN_RATELIMIT_MAX_BURST=5
-e ADMIN_RATELIMIT_SECONDS=60
-e ADMIN_SESSION_LIFETIME=20
-e SENDS_ALLOWED=true
-e EMERGENCY_ACCESS_ALLOWED=true
-e WEB_VAULT_ENABLED=true
-e EMERGENCY_ACCESS_ALLOWED=true
-e SENDS_ALLOWED=true
-e WEBSOCKET_ENABLED=true
-e SIGNUPS_ALLOWED=true
vaultwarden/server:latest

Vaultwarden Build Version

vaultwarden/server:latest

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

not used

Host/Server Operating System

Linux

Operating System Version

No response

Clients

Web Vault

Client Version

No response

Steps To Reproduce

After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel.

Expected Result

After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel.

Actual Result

After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel.

Logs

Screenshots or Videos

No response

Additional Context

No response

Originally created by @jy00295017 on GitHub (Oct 19, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6373 ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel. docker run -d \ --name vaultwarden \ --restart=unless-stopped \ -p 60854:80 \ -p 60855:3012 \ -v /Users/development/docker/vaultwarden/data:/data \ -e TZ=Asia/Shanghai \ -e SHOW_PASSWORD_HINT=false \ -e LOGIN_RATELIMIT_MAX_BURST=10 \ -e LOGIN_RATELIMIT_SECONDS=60 \ -e ADMIN_TOKEN=$(openssl rand -base64 48) \ -e ADMIN_RATELIMIT_MAX_BURST=5 \ -e ADMIN_RATELIMIT_SECONDS=60 \ -e ADMIN_SESSION_LIFETIME=20 \ -e SENDS_ALLOWED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e WEB_VAULT_ENABLED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e SENDS_ALLOWED=true \ -e WEBSOCKET_ENABLED=true \ -e SIGNUPS_ALLOWED=true \ vaultwarden/server:latest ### Vaultwarden Build Version vaultwarden/server:latest ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy not used ### Host/Server Operating System Linux ### Operating System Version _No response_ ### Clients Web Vault ### Client Version _No response_ ### Steps To Reproduce After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel. docker run -d \ --name vaultwarden \ --restart=unless-stopped \ -p 60854:80 \ -p 60855:3012 \ -v /Users/development/docker/vaultwarden/data:/data \ -e TZ=Asia/Shanghai \ -e SHOW_PASSWORD_HINT=false \ -e LOGIN_RATELIMIT_MAX_BURST=10 \ -e LOGIN_RATELIMIT_SECONDS=60 \ -e ADMIN_TOKEN=$(openssl rand -base64 48) \ -e ADMIN_RATELIMIT_MAX_BURST=5 \ -e ADMIN_RATELIMIT_SECONDS=60 \ -e ADMIN_SESSION_LIFETIME=20 \ -e SENDS_ALLOWED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e WEB_VAULT_ENABLED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e SENDS_ALLOWED=true \ -e WEBSOCKET_ENABLED=true \ -e SIGNUPS_ALLOWED=true \ vaultwarden/server:latest ### Expected Result After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel. docker run -d \ --name vaultwarden \ --restart=unless-stopped \ -p 60854:80 \ -p 60855:3012 \ -v /Users/development/docker/vaultwarden/data:/data \ -e TZ=Asia/Shanghai \ -e SHOW_PASSWORD_HINT=false \ -e LOGIN_RATELIMIT_MAX_BURST=10 \ -e LOGIN_RATELIMIT_SECONDS=60 \ -e ADMIN_TOKEN=$(openssl rand -base64 48) \ -e ADMIN_RATELIMIT_MAX_BURST=5 \ -e ADMIN_RATELIMIT_SECONDS=60 \ -e ADMIN_SESSION_LIFETIME=20 \ -e SENDS_ALLOWED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e WEB_VAULT_ENABLED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e SENDS_ALLOWED=true \ -e WEBSOCKET_ENABLED=true \ -e SIGNUPS_ALLOWED=true \ vaultwarden/server:latest ### Actual Result After deploying Vaultwarden via Docker using the following command, I cannot access the admin panel. docker run -d \ --name vaultwarden \ --restart=unless-stopped \ -p 60854:80 \ -p 60855:3012 \ -v /Users/development/docker/vaultwarden/data:/data \ -e TZ=Asia/Shanghai \ -e SHOW_PASSWORD_HINT=false \ -e LOGIN_RATELIMIT_MAX_BURST=10 \ -e LOGIN_RATELIMIT_SECONDS=60 \ -e ADMIN_TOKEN=$(openssl rand -base64 48) \ -e ADMIN_RATELIMIT_MAX_BURST=5 \ -e ADMIN_RATELIMIT_SECONDS=60 \ -e ADMIN_SESSION_LIFETIME=20 \ -e SENDS_ALLOWED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e WEB_VAULT_ENABLED=true \ -e EMERGENCY_ACCESS_ALLOWED=true \ -e SENDS_ALLOWED=true \ -e WEBSOCKET_ENABLED=true \ -e SIGNUPS_ALLOWED=true \ vaultwarden/server:latest ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_

kerem

2026-03-03 02:18:04 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 02:18:05 +03:00

Author

Owner

@stefan0xC commented on GitHub (Oct 19, 2025):

-e ADMIN_TOKEN=$(openssl rand -base64 48)

It seems that you are generating a random token each time you recreate the container. If you want to login you can check what value is set for the environment variable.

docker exec vaultwarden printenv ADMIN_TOKEN

Cf. https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page for more information.

btw: WEBSOCKET_ENABLED and port 3012 are not used anymore (since version v1.31.0!) so you are probably using an outdated tutorial.

@stefan0xC commented on GitHub (Oct 19, 2025): > -e ADMIN_TOKEN=$(openssl rand -base64 48) It seems that you are generating a random token each time you recreate the container. If you want to login you can check what value is set for the environment variable. ```bash docker exec vaultwarden printenv ADMIN_TOKEN ``` Cf. https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page for more information. btw: `WEBSOCKET_ENABLED` and port `3012` are not used anymore (since [version v1.31.0](https://github.com/dani-garcia/vaultwarden/releases/tag/1.31.0)!) so you are probably using an outdated tutorial.