Please, before posting, we've seen a lot of these post saying X instance is down right now, or "is X instance down?". The answer is probably, but it's probably because Lemmy v0.19 dropped and it includes some downtime, upwards of an hour for all the migrations to finish.

Please, hold off on asking/posting for an hour or so. Your sysadmins are waiting for it to come back online.

all 18 comments

sorted by: hot top controversial new old

[–] 0x4E4F@sh.itjust.works 39 points 10 months ago (2 children)

Instance admins be like: Please, please make it through without errors 😬 😭!

[–] Ech@lemmy.world 21 points 10 months ago (1 children)

I pitty the poor, volunteer admins facing clueless users dealing with downtime. "You said it'd only be an hour! WHAT'S GOING ON!?!?"

[–] bjoern_tantau@swg-empire.de 15 points 10 months ago (2 children)

It's even worse for me. I'm a poor clueless volunteer admin and the only user on my instance.

[–] 0x4E4F@sh.itjust.works 3 points 10 months ago

Bipolarity runs deep in this one.

[–] amju_wolf@pawb.social 2 points 10 months ago

At least if you break something it's just you who you have to deal with.

[–] kate@lemmy.uhhoh.com 5 points 10 months ago (1 children)

Can confirm!

[–] 0x4E4F@sh.itjust.works 3 points 10 months ago* (last edited 10 months ago)

And it's done! No errors! YESSSSS 🥳!

Next, log in... instance not found... 😭😭😭

[–] Mereo@lemmy.ca 37 points 10 months ago

Also, check if your instance has a Status page and bookmark it.

[–] Rentlar@lemmy.ca 6 points 10 months ago* (last edited 10 months ago) (1 children)

Jerboa v54 or later works on v17 Lemmy for me. You may need to clear data, logout and login for it to work. For other apps the process is likely similar.

[–] OldWoodFrame@lemm.ee 3 points 10 months ago (1 children)

Liftoff stopped working for Lemm.ee for me but not Lemmy.world so it must have been upgrade related. I couldn't figure out how to fix it so I'm just switching to Connect, ha.

[–] Nath@aussie.zone 1 points 10 months ago (1 children)

I've heard reports from our users that liftoff stopped working when we upgraded on Sunday also. It apparently doesn't work with the new version and they said the dev ran off to start a family.

[–] slazer2au@lemmy.world 2 points 10 months ago

He had twins. Lemmy apps are passion projects. Something has to give.

[–] Toribor@corndog.social 3 points 10 months ago (2 children)

I manage my own tiny insurance and it took long enough that I thought I broke something. I must need to turn up logging because the back end was completely silent except for "0.19.0" and I only knew something was happening because the database was busy.

[–] scrubbles@poptalk.scrubbles.tech 1 points 10 months ago

Same happened to me, I learned on other releases that no news is good news usually in updates, if you see things busy it's probably doing stuff - but this was a nail biter for sure. Very glad I skipped all the RCs.

[–] nimmo@lem.nimmog.uk 1 points 10 months ago (2 children)

I chose to take down my production instance of lemmyz do a cp -r of it, update the docker compose file to specify the new version numbers for Lemmy and lemmy-ui plus change the port that the stack exposes and do a docker-compose pull && docker-compose up -d on that stack to check to see if it could all work. Thankfully it did, so I updated the production compose file and tada! I'm on 19.0 safely

[–] OptimusPrime@lemmy.moonling.nl 1 points 10 months ago

Did it in a similar way. I used:

sudo cp -rp

to keep permissions also. Worked like a charm.

[–] Toribor@corndog.social 1 points 10 months ago

Are you using disk storage or object storage for pict-rs? I need a better way to test updates but I'm trying to avoid having to duplicate my storage or risk breaking prod by pointing to my live object storage from a second instance.