Ok so I ran a clean install and confirmed that the database objects exist. So that's definitely the problem. Your database is munted. An interesting thing happened when I re-ran the playbook - I noticed it didn't rebuild the postgres container. Very suspicious! Let's try blowing it away completely and re-running your script:
docker stop lemmyname_postgres_1
docker rm lemmyname_postgres_1
now re run the ansible playbook and let's see if that works.
ok thanks - I'm not very familiar with the lemmy installation process so I will need to check if possibly the schema objects in the database aren't created until the admin user is first set up, which is another possibility, but they definitely aren't there right now - I'll set up a fresh install to check in a few minutes.
Switching gears a bit - when you say you can't access the web UI, can you elaborate on that? The web server should be running. You are going to https://your.url, presumably and then what do you actually see in the browser? It should show an initial setup screen - do you not see anything or is there some kind of error message? When the ansible script runs to create the instance does it throw any errors at all or everything looks happy in the output, including creation of your ssl certs?
it should return an empty set. It looks like the database is running but the lemmy database tables were not installed. Can you get back to the sql prompt and try
\dt
if the database was installed correctly, you should see something like this:
lemmy-# \dt
List of relations
Schema | Name | Type | Owner
--------+----------------------------+-------+-------
public | __diesel_schema_migrations | table | lemmy
public | activity | table | lemmy . .
. .
public | person | table | lemmy
. . .
can you check that the tables are actually there? My guess is that the tables in the database weren't created. assuming you don't see any tables when you do this, again at the sql prompt, please try
\c lemmy
and see if it connects? if it does, it will say You are now connected to database "lemmy" as user "lemmy".
Let me know what the result of that is and we'll try to figure out what's gone wrong with the database setup because it looks like that's your problem - the database was not populated when it was created.
suggest you check postgres is running, accepting connections and returning results on the container first:
docker exec -it lemmyname_postgres_1 /bin/bash
assuming you can connect to the docker container and see a prompt, does this command put you at a sql prompt?
psql -U lemmy -d lemmy
if so, let's confirm that a sql command works.
select name from person; (will likely be an empty set if you haven't set up an admin user yet).
Does all this work OK?
oh the irony...
okay you actually made me laugh. that's not easy - take an upvote.
Thanks! Peertube looks like the perfect foundation, at least for the current scale. You can post peertube urls in Mastodon or Lemmy and share the comment stream over the fediverse. We are in the earliest days right now, but it is on!
sounds like Lemmy.
well, he also believes he's a natural leader - clearly, the delusion runs deep.
it should - I think (I am not familiar with netplan) - but from what I can tell it it's a utility that simplifies the local config tasks, when you apply it, I think it should be putting the nameservers in /etc/resolv.conf - but before you go down this rabbit hole, check whether 8.8.8.8 or 1.1.1.1 respond to a ping when pings to named servers don't - if so, it's definitely name resolution (which would be my first guess).
weird. it's like it failed to install the postgres public schema properly. I am not at all familiar with ansible but I see you can set verbosity. Do you think it would be worth trying that?
According to link below you can preface your playbook command with ANSIBLE_DEBUG=true ANSIBLE_VERBOSITY=4
https://www.shellhacks.com/ansible-enable-debug-increase-verbosity/