I’ll be restarting AZ today for an update to lemmy 0.19.

Upgrade complete.

This is a major upgrade, so I expect there to be some issues. Strap in, enjoy the ride.

Expect:

  • further restarts
  • bugs
  • slowdowns
  • logouts
  • 2FA being disabled
  • possibly issues with images, upgrading pictrs to 0.4 at the same time
  • Lodion 🇦🇺@aussie.zoneOPM
    4·
    11 months ago

    This was deliberate on the part of the devs. Old 2FA enrollment was finicky and error prone, locking many users out. So they’ve disabled it for everyone, forcing re-enrollment to enable it.

      • Lodion 🇦🇺@aussie.zoneOPM
        2·
        11 months ago

        You’ve got a good memory. Yes, the new process is slightly different so the old guide isn’t relevant. Also its not as important anyway, enrolling no longer enables 2FA before you have a device capable of generating TOTP codes.

        • maniacalmanicmania@aussie.zoneEnglish
          2·
          11 months ago

          I see. I didn’t really understand the complication last time but appreciated the guide. Re-enrolling was a cinch. I best do the bot account. Anything about bot accounts we should know about after this upgrade?

            • maniacalmanicmania@aussie.zoneEnglish
              2·
              11 months ago

              Done. I don’t know if this counts as an issue but on Chrome after setting up 2FA, logging out and logging in to test if the 2FA prompt came up there was briefly a little red error pop up on the bottom left of the browser that said ‘Error: mising_totp_token’. Seems like something that should only come up after submitting a blank value not when the 2FA popup first appears. Probably something for the lemmy devs but sharing with you in case it’s config or other. No other issues to report so far. Thanks again.

                • maniacalmanicmania@aussie.zoneEnglish
                  2·
                  11 months ago

                  There is a similar Error message issue for anonymous users (at least on desktop Firefox). The message is ‘Error: incorrect_login’. If it happened once per session I wouldn’t bring it up but I noticed that it happens for every page visit and sometimes while scrolling through comments, even after it has already popped up on the same page. Dunno if anonymous user traffic/experience warrants any concern though. Cheers.