this post was submitted on 27 Nov 2023
475 points (96.7% liked)

Announcements

23360 readers
4 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
dessalines@lemmy.ml
nutomic@lemmy.ml
475
Lemmy.ml v0.19 upgrade issues and downtime. (lemmy.ml)
submitted 1 year ago by dessalines@lemmy.ml to c/announcements@lemmy.ml
204 comments fedilink hide all child comments
 

In anticipation of Lemmy's upcoming 0.19 release, and to work out any final issues, we're going to deploy a test release on lemmy.ml within the next few days.

We're doing this testing on lemmy.ml only, so that we can encounter any issues before the release, and to make sure the upgrade process is smooth for other production servers.

Some of the following will happen during the process:

  • Apps will likely break (only for lemmy.ml)
  • Lemmy.ml may experience some downtime for the upgrade to complete (ideally no more than an hour).
  • If anything goes wrong, we may have to restore from a database backup, meaning content made in between backups may be lost.

If all goes well, we'll have an official announcement for the release after this testing period.

I apologize for the difficulties this might cause. At most this will be a week of hair-pulling, but its vital that we catch any issues before telling other servers to upgrade.

you are viewing a single comment's thread
view the rest of the comments
[–] pixelscript@lemmy.ml 1 points 1 year ago (1 children)

Connect, Sync, and Boost all told me to go kick rocks.

Evidently, whatever happened, it doesn't seem to be an issue with your platform.

[–] silas@programming.dev 1 points 1 year ago (1 children)

Ok, and you’re getting a new 6-digit code from your authenticator app every time you attempt to log in?

[–] pixelscript@lemmy.ml 2 points 1 year ago

Yes.

I noticed my authenticator app (KeePassXC) offers the ability to customize the TOTP parameters (SHA function, time step, code size). But no combination of settings seems to produce a valid code.

I assume Lemmy uses the suggested defaults in the RFC 6238 standard?