Wiped the VPS clean, new 22.04 server install.

Deployed using that installer.

Exact same issue. The lemmy container cannot reach the database and continually restarts. I’ll post some logs, but they’re practically identical to what I posted before:

lemmy container logs:

`thread 'main' panicked at 'Error connecting to postgres://lemmy:PasswordRedacted@postgres:5432/lemmy', crates/db_schema/src/utils.rs:161:56

sudo docker ps output:

CONTAINER ID   IMAGE                        COMMAND                  CREATED          STATUS
 PORTS                                                                                         NAMES
9eaa62ea6f99   caddy:latest                 "caddy run --config …"   12 minutes ago   Up 12 minutes
 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 443/udp, 2019/tcp   lemmy-easy-deploy-proxy-1
a10009ed128d   dessalines/lemmy-ui:0.17.4   "docker-entrypoint.s…"   12 minutes ago   Up 12 minutes
                                                                                               lemmy-easy-deploy-lemmy-ui-1
a166b1486d51   dessalines/lemmy:0.17.4      "/app/lemmy"             12 minutes ago   Restarting (101) 41 seconds ago                                                                                                 lemmy-easy-deploy-lemmy-1
08329653260b   asonix/pictrs:0.3.1          "/sbin/tini -- /usr/…"   12 minutes ago   Up 12 minutes
 6669/tcp, 8080/tcp                                                                            lemmy-easy-deploy-pictrs-1
51af8f312511   postgres:15-alpine           "docker-entrypoint.s…"   12 minutes ago   Up 12 minutes
lemmy-easy-deploy-postgres-1

Ran those commands successfully, then the playbook again. Playbook has zero errors or warnings.

The postgres container was remade… with the same broken database. Went into it with psql like before, did \c lemmy, then \dt - same error - did not find any relations.

No errors of any kind in the ansible script. nginx is running, and it’s at https://lemmy.name - I get some gateway timeout errors once in a while, but that’s all. When I do get error pages, they are served via https at least, so I don’t think there’s anything wrong with that part.

I assume this is because the lemmy backend container is continually restarting (as I detailed more in my original post and other replies here) due to database connection errors

\c lemmy does return “You are now connected to database “lemmy” as user “lemmy””

Running \dt after connecting returns “Did not find any relations”, so it looks like you were right and the database didn’t get populated.

docker exec -it lemmyname_postgres_1 /bin/bash returns the bash prompt as expected: 2ab8c789fdcd:/#

psql -U lemmy -d lemmy successfully opens psql:

psql (15.3)
Type "help" for help.

lemmy=# 

ran select name from person; from the psql shell, it does look empty (haven’t created any users yet):

ERROR:  relation "person" does not exist
LINE 1: select name from person;

Yes, I posted the docker status info and logs from the container in my reply to Veraticus