Error running migrations: DatabaseError(Unknown, "permission denied for schema public")

[lug-gh]

Vaultwarden Support String

x

Vaultwarden Build Version

latest

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

none

Host/Server Operating System

Linux

Operating System Version

No response

Clients

Web Vault

Client Version

No response

Steps To Reproduce

Hello, I would like to install vaultwarden with postgres and have followed the instructions below:
(https://github.com/dani-garcia/vaultwarden/wiki/Using-the-PostgreSQL-Backend)

CREATE DATABASE vaultwarden;
CREATE USER vaultwarden WITH ENCRYPTED PASSWORD 'yourpassword';
GRANT CONNECT ON DATABASE vaultwarden TO vaultwarden;
ALTER SCHEMA public OWNER TO vaultwarden;

I have of course changed the password.

When starting the container I get the following error message:

postgres     | 2025-01-14 13:38:08.901 CET [37] ERROR:  permission denied for schema public at character 28
postgres     | 2025-01-14 13:38:08.901 CET [37] STATEMENT:  CREATE TABLE IF NOT EXISTS __diesel_schema_migrations (
postgres     | 	       version VARCHAR(50) PRIMARY KEY NOT NULL,
postgres     | 	       run_on TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
postgres     | 	);
postgres     | 	
vaultwarden  | [2025-01-14 12:38:08.901][panic][ERROR] thread 'main' panicked at 'Error running migrations: DatabaseError(Unknown, "permission denied for schema public")': src/db/mod.rs:487
vaultwarden  |    0: vaultwarden::init_logging::{{closure}}
vaultwarden  |    1: std::panicking::rust_panic_with_hook
vaultwarden  |    2: std::panicking::begin_panic_handler::{{closure}}
vaultwarden  |    3: std::sys::backtrace::__rust_end_short_backtrace
vaultwarden  |    4: rust_begin_unwind
vaultwarden  |    5: core::panicking::panic_fmt
vaultwarden  |    6: core::result::unwrap_failed
vaultwarden  |    7: vaultwarden::db::DbPool::from_config
vaultwarden  |    8: vaultwarden::main::{{closure}}
vaultwarden  |    9: vaultwarden::main
vaultwarden  |   10: std::sys::backtrace::__rust_begin_short_backtrace
vaultwarden  |   11: main
vaultwarden  |   12: <unknown>
vaultwarden  |   13: __libc_start_main
vaultwarden  |   14: _start
vaultwarden  | 

I have tested postgres 15, 16 and 17.

Expected Result

x

Actual Result

x

Logs

No response

Screenshots or Videos

No response

Additional Context

No response

[lug-gh]

After I changed the owner of the database to vaultwarden it works. However, since this is not in the instructions, I am now unsure whether this is necessary or whether it is a bug.

[lug-gh]

This has nothing to do with Vaultwarden it self. This was more an issue with PostgreSQL and you probably updated the version of PostgreSQL somewhere in between which might had some changes.

No, this is about a completely new installation of vaultwarden. I have only tested the different postgres versions as I don't know which one is compatible with vaultwarden.
It's probably not a bug, but if you follow the installation instructions, it's guaranteed not to work.

[felipewnp]

I can confirm this problem as well.

Fresh install using PostgreSQL.

I've created the database on PostgreSQL using the commands below (based on the documentation):

CREATE DATABASE vaultwarden;
CREATE USER vaultwarden WITH ENCRYPTED PASSWORD 'yourpassword';
GRANT CONNECT ON DATABASE vaultwarden TO vaultwarden;
ALTER SCHEMA public OWNER TO vaultwarden;

But when the vaultwarden-server starts up, it throws this error and exits:

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.34.3                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[2025-09-18 20:18:50.139][vaultwarden::auth][INFO] Private key 'data/rsa_key.pem' created correctly
[2025-09-18 20:18:50.159][panic][ERROR] thread 'main' panicked at 'Error running migrations: DatabaseError(Unknown, "permission denied for schema public")': src/db/mod.rs:487
   0: vaultwarden::init_logging::{{closure}}
   1: std::panicking::rust_panic_with_hook
   2: std::panicking::begin_panic_handler::{{closure}}
   3: std::sys::backtrace::__rust_end_short_backtrace
   4: __rustc::rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: vaultwarden::db::DbPool::from_config
   8: vaultwarden::main::{{closure}}
   9: vaultwarden::main
  10: std::sys::backtrace::__rust_begin_short_backtrace
  11: main

The ONLY way to make Vaultwarden work with PostgreSQL was to do what @lug-gh did.

Make the Vaultwarden DB User a DB Owner.

The documentation should be:

CREATE USER vaultwarden WITH ENCRYPTED PASSWORD 'yourpassword';
CREATE DATABASE vaultwarden OWNER vaultwarden;

@BlackDex Would it help if I sent a PR to fix the documentation?

[BlackDex]

Which documentation? If it is in the Wiki, feel free to update where needed!

[felipewnp]

Done!

https://github.com/dani-garcia/vaultwarden/wiki/Using-the-PostgreSQL-Backend

[BlackDex]

Thx