Selfhosted

37723 readers

383 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

[SOLVED] Need some guidance with upgrading (self.selfhosted)

submitted 6 months ago* (last edited 6 months ago) by penguin_ex_machina to c/selfhosted

9 comments fedilink hide all child comments

Hi! I'm hoping for some guidance upgrading my instance. I'm still running on v0.17.3 because I ran into some issues upgrading to 0.18 and didn't have time to really figure it out. Now that the current release is v0.19, I have people on my instance asking to upgrade and I don't blame them. Can I simply point Docker compose at the latest release, or do I have to do incremental upgrades? What do I need to look out for with v0.18? Documentation seems to be pretty slim for whatever breaking changes happened during that release cycle and how to deal with them. Any help is appreciated!

EDIT: Thank you for all the help! I also had to update pictrs and fix some small config issues and then everything worked as expected. I'm now on 0.19.1!

all 10 comments

sorted by: hot top controversial new old

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

I would move to 0.18 and then on to 0.19, how you get there will depend on how you setup in the first place. a look at your compose file would help

[–] penguin_ex_machina 1 points 6 months ago (1 children)

I created a gist with my compose file: https://gist.github.com/osiriswrecks/26a875576d3bbcf11923d7715ac15e6e. It should be stripped of all private info. I tried changing the version from 0.17.3 to 0.18.0 and the server returns a gateway error after restarting.

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

Update lines 33 and 48 with 0.18.5, then do a docker compose pull and then docker compose up -d

Once lemmy is up and happy, then repeat for 0.19.1

[–] penguin_ex_machina 1 points 6 months ago (2 children)

Upgraded to 0.18.5, which now gives me this error:

lemmy-lemmy-ui-1  | API error: FetchError: request to http://lemmy:8536/api/v3/site?auth=AUTH_KEY failed, reason: connect ECONNREFUSED IP_ADDRESS:8536

[–] [email protected] 2 points 6 months ago (2 children)

You might need to wait for lemmy to sort it's self out before lemmt-ui is happy

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

I can second this. It took a while after an update for the domain to show properly and not give an error. I don't know exactly how long but I started it in the early morning and it wasn't working but by 11 am it was all sorted out.

[–] penguin_ex_machina 1 points 6 months ago (1 children)

Meaning I just wait a bit and retry later?

[–] [email protected] 2 points 6 months ago

Yes, I had the same issue when I updated to 0.19

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

UI doesn't come up until database migrations fully complete. Can take half an hour or more depending on how much content is indexed in your instance.