The ansible-playbook command itself connected to the VPS and completed without any errors or warnings. This is on a completely fresh VPS with Ubuntu Server 22.04.
I created all directories needed in the guide, and the only file I modified was the inventory/hosts file - filling in the username/domain for SSH, domain name, contact email and adding the location of the private key for SSH.
The guide didn’t note any changes to config.hjson I needed to make, so I copied that file as requested but left it with the default content. I’m thinking if I missed something it’s most likely there.
I couldn’t access the web UI and with some investigation I found the dessalines/lemmy:0.17.4 (backend) container is continually restarting, apparently because it can’t reach the database - sudo docker container logs <id> returns the following:
thread 'main' panicked at 'Error connecting to postgres://lemmy:PasswordRedacted@postgres:5432/lemmy', crates/db_schema/src/utils.rs:161:56
I’m not sure what to do at this point, so I would be very appreciative of any help with this issue.
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:
public | __diesel_schema_migrations | table | lemmy
public | activity | table | lemmy
.
.
<more tables>
.
.
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.
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?
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
Is there a postgresql docker container running?
Yes, I posted the docker status info and logs from the container in my reply to Veraticus
suggest you check postgres is running, accepting connections and returning results on the container first:
docker exec -it lemmyname_postgres_1 /bin/bashassuming you can connect to the docker container and see a prompt, does this command put you at a sql prompt?
psql -U lemmy -d lemmyif 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?
docker exec -it lemmyname_postgres_1 /bin/bashreturns the bash prompt as expected:2ab8c789fdcd:/#psql -U lemmy -d lemmysuccessfully opens psql:ran
select name from person;from the psql shell, it does look empty (haven’t created any users yet):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
\dtif the database was installed correctly, you should see something like this:
lemmy-# \dt
Schema | Name | Type | Owner
--------±---------------------------±------±------
public | __diesel_schema_migrations | table | lemmy
public | activity | table | lemmy . .
<more tables>
. .
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 lemmyand 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.
\c lemmydoes 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.
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?
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