Selfhosted
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).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Having helped someone else through a similar update issue, I'm going to assume you're using the Ansible deploy method.
If you're using the Ansible playbook method, and don't understand every single step the playbook is doing, I recommend deploying Lemmy manually.
It sounds like your Posgres password changed in the playbook variables and got set to a new value in the lemmy config and docker-compose files. But once a Postgres DB is initialized, the env vars for the initial DB, user, and password are no longer needed/processed. Thus, your compose file, playbook, and lemmy config have a different password than what Postgres was setup with.
Try shelling into your Postgres container and re-setting the password for the Lemmy user to what's defined in the lemmy config and compose file and seeing if that gets you past the incorrect password error.
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...
My advice: drop the "easy button" stuff and deploy it manually. You'll have WAY less headaches in the long run. Either way, it sounds like your Postgres password is out of sync with what the config files have. So try updating that through a root shell in the PG container to what's documented in your other config files.
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
envfile,then restarted the upgrade process. It's running again.
The odd part is that it was running fine until the upgrade.