First Pre Release Of Vaultwarden

kemboielvis22 · February 18, 2026, 8:08pm

Okay Thank you for testing

kemboielvis22 · February 18, 2026, 8:16pm

Let me look into this

transocean · February 19, 2026, 3:20pm

@kemboielvis22

We can forget that. One character in the token was wrong. Sorry, my mistake.

kemboielvis22 · February 19, 2026, 4:22pm

Okay Noted

transocean · May 1, 2026, 7:41pm

@kemboielvis22

Push

kemboielvis22 · May 9, 2026, 11:45pm

Hello @transocean
Help in testing

api-cli run update-module --data '{"module_url":"ghcr.io/geniusdynamics/vaultwarden:dev","instances":["vaultwarden1"],"force":true}'

make sure updating from previous versions does not break and also backup works

transocean · May 10, 2026, 8:39am

@kemboielvis22

Tested and found to be good.

kemboielvis22 · May 10, 2026, 1:27pm

Okay Thanks for testing

dan · May 25, 2026, 7:09pm

Tried installing this today, and it isn’t working for me. A few findings:

There really should be some guidance somewhere–perhaps as a tooltip–for the “Admin token.” Is this just an admin password? Does it need to be in some particular format? Length or other complexity requirements? Etc.?
Related to this, a link somewhere to the admin portal would be good as well.
But the much bigger issue is that it just won’t start. Here’s what I see in the logs:

2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden1] 53734cf1a623f6baafbdd716aab92003cd80daf8510e6224ced61a1b8f17ac9a
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] /--------------------------------------------------------------------\
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] |                        Starting Vaultwarden                        |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] |                           Version 1.36.0                           |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] |--------------------------------------------------------------------|
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] | official channels to report bugs/features, regardless of client.   |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] | Send usage/configuration questions or feature requests to:         |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] |   https://github.com/dani-garcia/vaultwarden/discussions or        |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] |   https://vaultwarden.discourse.group/                             |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] | Report suspected bugs/issues in the software itself at:            |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] |   https://github.com/dani-garcia/vaultwarden/issues/new            |
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] \--------------------------------------------------------------------/
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app]
2026-05-25T15:05:18-04:00 [1:vaultwarden1:systemd] Started Podman vaultwarden-app.service.
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app] Error loading config:
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app]   Both `SMTP_HOST` and `SMTP_FROM` need to be set for email support without `USE_SENDMAIL`
2026-05-25T15:05:18-04:00 [1:vaultwarden1:vaultwarden-app]
2026-05-25T15:05:18-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:18.491918462 -0400 EDT m=+0.282415496 container died 53734cf1a623f6baafbdd716aab92003cd80daf8510e6224ced61a1b8f17ac9a (image=docker.io/vaultwarden/server:1.36.0, name=vaultwarden-app, org.opencontainers.image.revision=f21a3adae2fbb8582b60b121783c597fe6895ff4, org.opencontainers.image.source=https://github.com/dani-garcia/vaultwarden, org.opencontainers.image.url=https://github.com/dani-garcia/vaultwarden, org.opencontainers.image.description=Unofficial Bitwarden compatible server written in Rust - 1.36.0, org.opencontainers.image.documentation=https://github.com/dani-garcia/vaultwarden/wiki, org.opencontainers.image.version=1.36.0, org.opencontainers.image.licenses=AGPL-3.0-only, org.opencontainers.image.created=2026-05-03T12:23:03+00:00, PODMAN_SYSTEMD_UNIT=vaultwarden-app.service)
2026-05-25T15:05:18-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:18.645172174 -0400 EDT m=+0.435669198 container cleanup 53734cf1a623f6baafbdd716aab92003cd80daf8510e6224ced61a1b8f17ac9a (image=docker.io/vaultwarden/server:1.36.0, name=vaultwarden-app, pod_id=62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721, org.opencontainers.image.documentation=https://github.com/dani-garcia/vaultwarden/wiki, PODMAN_SYSTEMD_UNIT=vaultwarden-app.service, org.opencontainers.image.revision=f21a3adae2fbb8582b60b121783c597fe6895ff4, org.opencontainers.image.created=2026-05-03T12:23:03+00:00, org.opencontainers.image.description=Unofficial Bitwarden compatible server written in Rust - 1.36.0, org.opencontainers.image.version=1.36.0, org.opencontainers.image.licenses=AGPL-3.0-only, org.opencontainers.image.source=https://github.com/dani-garcia/vaultwarden, org.opencontainers.image.url=https://github.com/dani-garcia/vaultwarden)
2026-05-25T15:05:18-04:00 [1:vaultwarden1:systemd] vaultwarden-app.service: Main process exited, code=exited, status=12/n/a
2026-05-25T15:05:19-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:19.02034396 -0400 EDT m=+0.274093403 container remove 53734cf1a623f6baafbdd716aab92003cd80daf8510e6224ced61a1b8f17ac9a (image=docker.io/vaultwarden/server:1.36.0, name=vaultwarden-app, pod_id=62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721, org.opencontainers.image.documentation=https://github.com/dani-garcia/vaultwarden/wiki, org.opencontainers.image.licenses=AGPL-3.0-only, org.opencontainers.image.revision=f21a3adae2fbb8582b60b121783c597fe6895ff4, org.opencontainers.image.version=1.36.0, org.opencontainers.image.url=https://github.com/dani-garcia/vaultwarden, org.opencontainers.image.created=2026-05-03T12:23:03+00:00, org.opencontainers.image.source=https://github.com/dani-garcia/vaultwarden, PODMAN_SYSTEMD_UNIT=vaultwarden-app.service, org.opencontainers.image.description=Unofficial Bitwarden compatible server written in Rust - 1.36.0)
2026-05-25T15:05:19-04:00 [1:vaultwarden1:vaultwarden1] 53734cf1a623f6baafbdd716aab92003cd80daf8510e6224ced61a1b8f17ac9a
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] vaultwarden-app.service: Failed with result 'exit-code'.
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] vaultwarden-app.service: Consumed 2.710s CPU time.
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] vaultwarden-app.service: Scheduled restart job, restart counter is at 23.
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] Stopped Podman vaultwarden-app.service.
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] vaultwarden-app.service: Consumed 2.710s CPU time.
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] Stopping Podman vaultwarden.service...
2026-05-25T15:05:19-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:19.478755427 -0400 EDT m=+0.168762130 pod stop 62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721 (image=, name=vaultwarden)
2026-05-25T15:05:19-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:19.521922515 -0400 EDT m=+0.211929448 container died 96b5abbb0bb6f781c9ef9fdd185d0c3862c029b25d0256f43ff446f582b39053 (image=, name=62cecac044b8-infra, PODMAN_SYSTEMD_UNIT=vaultwarden.service)
2026-05-25T15:05:19-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:19.662831302 -0400 EDT m=+0.352837985 container cleanup 96b5abbb0bb6f781c9ef9fdd185d0c3862c029b25d0256f43ff446f582b39053 (image=, name=62cecac044b8-infra, pod_id=62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721, PODMAN_SYSTEMD_UNIT=vaultwarden.service)
2026-05-25T15:05:19-04:00 [1:vaultwarden1:systemd] Removed slice cgroup user-libpod_pod_62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721.slice.
2026-05-25T15:05:19-04:00 [1:vaultwarden1:podman] vaultwarden
2026-05-25T15:05:20-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:20.009732873 -0400 EDT m=+0.169398411 container remove 96b5abbb0bb6f781c9ef9fdd185d0c3862c029b25d0256f43ff446f582b39053 (image=, name=62cecac044b8-infra, pod_id=62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721, PODMAN_SYSTEMD_UNIT=vaultwarden.service)
2026-05-25T15:05:20-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:20.046855216 -0400 EDT m=+0.206520754 pod remove 62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721 (image=, name=vaultwarden)
2026-05-25T15:05:20-04:00 [1:vaultwarden1:podman] 62cecac044b87c51dbadb358263ace2a0cfb74c25b605e045b03f082f7b25721
2026-05-25T15:05:20-04:00 [1:vaultwarden1:systemd] Stopped Podman vaultwarden.service.
2026-05-25T15:05:20-04:00 [1:vaultwarden1:systemd] vaultwarden.service: Consumed 1.450s CPU time.
2026-05-25T15:05:20-04:00 [1:vaultwarden1:systemd] Starting Podman vaultwarden.service...
2026-05-25T15:05:20-04:00 [1:vaultwarden1:systemd] Created slice cgroup user-libpod_pod_5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3.slice.
2026-05-25T15:05:20-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:20.724152839 -0400 EDT m=+0.487974324 container create cf5cffc2f8e2247a0a51e7b1f0d3398766388d766d0366510694640351e0f887 (image=, name=5b10570b7b7c-infra, pod_id=5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3, PODMAN_SYSTEMD_UNIT=vaultwarden.service)
2026-05-25T15:05:20-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:20.735932322 -0400 EDT m=+0.499753807 pod create 5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3 (image=, name=vaultwarden)
2026-05-25T15:05:20-04:00 [1:vaultwarden1:podman] 5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3
2026-05-25T15:05:21-04:00 [1:vaultwarden1:systemd] Started libcrun container.
2026-05-25T15:05:21-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:21.358062432 -0400 EDT m=+0.502168471 container init cf5cffc2f8e2247a0a51e7b1f0d3398766388d766d0366510694640351e0f887 (image=, name=5b10570b7b7c-infra, pod_id=5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3, PODMAN_SYSTEMD_UNIT=vaultwarden.service)
2026-05-25T15:05:21-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:21.386413087 -0400 EDT m=+0.530519136 container start cf5cffc2f8e2247a0a51e7b1f0d3398766388d766d0366510694640351e0f887 (image=, name=5b10570b7b7c-infra, pod_id=5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3, PODMAN_SYSTEMD_UNIT=vaultwarden.service)
2026-05-25T15:05:21-04:00 [1:vaultwarden1:podman] 2026-05-25 15:05:21.402407307 -0400 EDT m=+0.546513326 pod start 5b10570b7b7c4889c0694c54fe1c01f331c497212ffb48df033da41bcfc444c3 (image=, name=vaultwarden)
2026-05-25T15:05:21-04:00 [1:vaultwarden1:podman] vaultwarden
2026-05-25T15:05:21-04:00 [1:vaultwarden1:systemd] Started Podman vaultwarden.service.
2026-05-25T15:05:21-04:00 [1:vaultwarden1:systemd] Starting Podman vaultwarden-app.service...

From what I see up-thread, that makes it look like SMTP isn’t configured–but it should be:

transocean · May 25, 2026, 7:30pm

Hi @dan

If I’m not entirely mistaken, you still need to configure the SMTP settings within the app itself. To do this, you’ll need to log in to VW as an admin.

dan · May 25, 2026, 7:40pm

…which I do how? I’m getting 502 when I go to vault.mydomain.

transocean · May 25, 2026, 7:42pm

Normally under https://vaultwarden.yourdomain.com/admin

dan · May 25, 2026, 7:43pm

As expected (because vaultwarden-app isn’t running), that’s still giving 502.

transocean · May 25, 2026, 7:44pm

Maybe @kemboielvis22 can help.

transocean · May 26, 2026, 8:52am

Good morning @kemboielvis22

I have now noticed that I can no longer log in as an admin using the stored password.

The command runagent -m vaultwarden1 cat vaultwarden.env displays the correct password. However, I am unable to log in as an admin via the web console.

oneitonitram · May 26, 2026, 5:53pm

Unless you changed the password and forgot about it, there is Def Nothing you can do to recover that key.
I once made a similar mistake. every method to try and retrieve failed miserably, i only had to reinstall vaultwarden, anc copy passwords into the new instance, then delete the previous installation, at least this time around making sure i dont forget my key.

transocean · May 26, 2026, 6:06pm

I’ve changed my password. Does that still apply?

kemboielvis22 · May 26, 2026, 8:53pm

Hello Can you check the vaultwarden.env if the smtp credentials have been set

kemboielvis22 · May 26, 2026, 8:53pm

Did you change the admin token

Did you install from version 1 and upgrade to v2 or

dan · May 26, 2026, 9:04pm

[root@ns8 ~]# runagent -m vaultwarden1 cat vaultwarden.env
ADMIN_RATELIMIT_MAX_BURST=10
ADMIN_RATELIMIT_SECONDS=60
ADMIN_TOKEN=(redacted)
ADMIN_TOKEN_UNHASHED=(redacted)
DOMAIN=https://vault.db5.us
EMERGENCY_ACCESS_ALLOWED=
INVITATIONS_ALLOWED=False
LOGIN_RATELIMIT_MAX_BURST=10
LOGIN_RATELIMIT_SECONDS=60
PUSH_ENABLED=
PUSH_IDENTITY_URI=
PUSH_INSTALLATION_ID=
PUSH_INSTALLATION_KEY=
PUSH_RELAY_URI=
SENDS_ALLOWED=
SHOW_PASSWORD_HINT=
SIGNUPS_ALLOWED=False
SIGNUPS_DOMAINS_WHITELIST=
SIGNUPS_VERIFY=
SIGNUPS_VERIFY_RESEND_LIMIT=
SIGNUPS_VERIFY_RESEND_TIME=
SMTP_ENCRYPTION=none
SMTP_FROM=
SMTP_HOST=10.5.4.1
SMTP_PASSWORD=
SMTP_PORT=25
SMTP_USERNAME=
WEB_VAULT_ENABLED=