MarsAgainstVenus

joined 1 year ago
[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

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.

[–] [email protected] 1 points 11 months ago

The odd part is that it was running fine until the upgrade.

[–] [email protected] 1 points 11 months ago (3 children)

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 went to upgrade Lemmy from 18.4 to 18.5 but in the process it failed with an incorrect Postgres password error. I'm trying to create a new docker container and mount the postgres volume in order to reset the "lemmy" user password but can't figure out how to get it running without knowing the password.

Could anyone point me in the right direction, please?