Submitted 5 months ago by scrubbles@poptalk.scrubbles.tech to fediverse@lemmy.world
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.
Also, check if your instance has a Status page and bookmark it.
Jerboa v54 or later works on v17 Lemmy for me. You may need to clear data, logout and login for it to work.
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.
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.
Anybody know how to use the weighted subscribed communities now?
Liftoff won’t work with 0.19.
The Dev hasn’t patched it to work with the breaking changes of 0.19
Being a new parent of twins is time consuming and I wish him the best.
Oof. Being a parent of two non-twins is time consuming enough.
Hijacking this to add: most Lemmy apps don’t have any new feature yet. The “scaled” sorting (=weighted subscribed communities) will probably make it’s way into the first apps around New Years, I’d guess.
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.
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
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.
Did it in a similar way. I used:
sudo cp -rp
to keep permissions also. Worked like a charm.
Took me a minute to figure out that you weren’t trying to communicate that v0.19 was recalled and to expect downtime due to downgrades. May want to use the word “released” rather than “dropped”. Unless there’s also some phat beats in the release, in which case, carry on.
0x4E4F@sh.itjust.works 5 months ago
Instance admins be like: Please, please make it through without errors 😬 😭!
Ech@lemmy.world 5 months ago
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 5 months ago
It’s even worse for me. I’m a poor clueless volunteer admin and the only user on my instance.
kate@lemmy.uhhoh.com 5 months ago
Can confirm!
0x4E4F@sh.itjust.works 4 months ago
ANd then… no errors! YESSSSS 🥳!
Next, log in… instance not found… 😭😭😭😭