Try to get a bash prompt inside the dB container, then you can run CLI postgres commands from inside the container.
this post was submitted on 20 Aug 2023
18 points (95.0% liked)
Lemmy Support
4651 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
How exactly? The recommendations of other people here didn't work.
EDIT: Found a solution. Check other posts to see how it works.
You might be able to just run docker-compose exec postgres psql to drop into a shell (you may still need to define the user with -U lemmy)
If you're trying to connect with ane external tool though, you'll need to expose the ports temporarily, which I'm not sure if you can do without restarting the container (after adding the exposed ports to the docket compose file, like 127.0.0.1:5432:5432)
After executing docker exec -it lemmymydomain_postgres_1 psql
I've got the error:
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist
Oh yeah, try specifying the hostname as localhost (I think it's -h, but --help will confirm it). Psql tries by default to connect to that socket, but in docker it does use it.
Basically, you'll need to specify the hostname and user (and if port, which should just be default, then -p 5432)
It should be
docker exec -it lemmymydomain_postgres_1 psql -h localhost -U lemmy (dbname)
Keeping in mind that you'll need to have the right user and database name, assuming (based on your original comment) lemmy being the username and the db name might also be lemmy
Edit: this should btw just get you into the db, I have no idea of its a good idea or not to delete a user directly from the db, it might cause issues, but I don't have experience with it, but just generally use postgres in docker with other projects
I found a solution here
A warning to people who have the same problem:
On the website there is a command, which will purge all unverified account. If your admin account wasn't verified, it will be purged, too.
Thanks a lot for your help :)
Glad you solved it! Definitely sounds like a better solution than playing around in the db
Well, it is playing around with the db 😀 ... and it could even destroy the whole instance if people don't see the warning I've posted there.
I hope the Lemmy devs sort out email verification soon. We had so many problems we switched it off at futurology.today & went with limiting new sign-ups to a set amount per hour to combat bots instead.
What exactly was the issue with your verification system?
Currently the emails get out. At least I can see people creating accounts and posting stuff.
What exactly was the issue with your verification system?
Numerous issues the site dev couldn't fully understand after hours of investigating. We've switched off email verification until the Lemmy devs fix this in an update. Additionally 2FA is often broken too & awaiting a fix.
What a big no-go, if you could lock out yourself as an admin.
That's such a sloppy craftsmanship.