The odd part is that it was running fine until the upgrade.
The odd part is that it was running fine until the upgrade.
I used the Lemmy-Easy-Deploy method but the catch is that I migrated from Google Cloud Free Tier to a paid server with another host. I have the backups so I can always restore from that if I really have to. I have an env file with the password that it should be using but I’m not sure how it was changed…
I’ve been doing the same. I have all 4 but most of my time is spent on Memmy but Mlem is quickly catching up.
Wow, it hadn’t even crossed my mind that people ALREADY might not recognize it.
I blocked them this morning. Didn’t want to but it was overwhelming.
I’m on lemmy.world and I can see the time and date your comment was posted and same for edited.
I couldn’t get my container started with postgress running but I had an idea:
I started the upgrade process with Lemmy-Easy-Deploy,
canceled out of it before it removed the containers,
ran
sudo docker exec -i lemmy-easy-deploy-postgres-1 psql -U lemmy -c "alter user lemmy with password 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'"
with the password set in my
env
file,then restarted the upgrade process. It’s running again.