Selfhosted

39250 readers

191 users here now

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Help with Postgres (lemmy.world)

submitted 11 months ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [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.