Problems while migrating from sqlite to postgres

[NxckyBear]

Hello, I am trying to migrate vaultwardens backend from sqlite to pgsql prior a major change im doing. However I cannot do that as I get an error while running the so called bitwarden.load from the guide how to migrate from sqlite to pgsql
the process should throw some warnings, yes. However it does not give me a success message but gives me the following message:
pgloader failed to find anything in schema "public" in target catalog.

[stefan0xC]

Someone recently changed the grant rights for postgres 15+
So maybe that's why? Can you test with more privileges?

[NxckyBear]

How exactly do I need to configure it? I have already at first to check if it works, and as it did, I wanted to change to pgsql

[stefan0xC]

You have to change the DATABASE_URL=postgres://postgres:${POSTGRES_PASSWORD}@postgres:5432/postgres and start vaultwarden.

[NxckyBear]

I did that with the vaultwarden credentials... I still get the same error whatsoever...

[tessus]

The order of commands is off. First create the vaultwarden user, then create the db. Create the database as follows:

CREATE DATABASE vaultwarden WITH OWNER = vaultwarden;

Postgres has changed how the public schema is handled (in version 15 or 16). Unfortunately schema handling in poatgres was always a bit strange. If you connect with a user to postgres and create a table without a schema, this table is automatically put into the public schema. e.g. I would have expected that such a table is created under the schema of the user (same name as the user). Well, not so in Postgres.

Anyway I believe I had a similar issue with another server app and the above fixed my problem back then. Maybe it works for vw as well.

[NxckyBear]

~~Ok I think I found the root issue... Vaultwarden cannot even connect to the pgsql server for some reason... I am using Caddy as the reverse proxy... I cannot tell why vaultwarden cannot connect to the server
both are containers and as port 80 is blocked by caddy I needed to use another port, so I use port 280, and so i do for the container... pgsql is also running on a container Fixable through opening both ports in ufw, however I now get the error of the pgsql server unexpectedly closing the connection, At the same time, I get the error on the pgsql server that the postgres user doesnt exist (yes i may have used root as the postgres user, unsure if this is the mistake here) that the authentification for the user "postgres" has failed even tho I used vaultwarden as login credentials...
Edit: it only works with postgres credentials... Well not even then it does work... Now I get "Permission denied for table __diesel_migration_schemes" even tho it has permission on every table in the schema public
the pgsql server throws this error:
2025-01-27 13:04:59.302 UTC [6273] FATAL: password authentication failed for user "postgres"
2025-01-27 13:04:59.302 UTC [6273] DETAIL: Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
also the container itself returns "curl: (7) Failed to connect to localhost port 80 after 0 ms: Couldn't connect to server" therefore it si marked as unhealthy and I do not have any Idea how to fix this one with caddy as reverse proxy I configured rocket wrong, now its marked as healthy

edit2: the pgsql error seems to be unfixable, I finally got it working. Thanks to all who helped