Both FireFox on PC and Connect on Android keep signing me out, throwing general “error” messages, and refusing to load the next page.

Liftoff on iOS can’t even find lemmy.today in order to add it as an instance!

I’m not seeing any discussion of these kinds of problems elsewhere but they’ve been consistent since the .19 upgrade and they’ve persisted after the .19.1 update.

  • mrmanager@lemmy.todayM
    3·
    11 months ago

    Yes.

    I think this update has been very problematic in many areas, and in hindsight, we should have waited a few more weeks to update.

    Previous updates have not had major problems, but we knew this was a very big update with a big rewrite of how several things work (like federation), so it would have been smarter to wait longer than a week to update.

    Unfortunantly there is no way to go back to previous version now, since the 0.18.5 to 0.19.0 update upgraded the database schema as well.

    The developers of Lemmy are working on fixes. I know they reopened github tickets where federation was supposed to be fixed. And there are many other issues as well: https://github.com/LemmyNet/lemmy/issues

    You can search there and see if anyone else has reported simular issues, and otherwise create a new issue and report the problems.

    Next time we will wait longer to install major updates from 19 to 20 and so on.

    Edit: Im also getting “Incorrect logon” messages while using the web interface, but it doesnt seem to have any effect. I dont get logged out. But another bug somewhere.

  • Allero@lemmy.today
    1·
    11 months ago

    Can confirm, had issues loading content in Eternity client (Android).

    Web version works well.

  • Rivalarrival@lemmy.today
    1·
    11 months ago

    I can confirm that I’ve been having problems for the past two or three days.

    I suspect (but can’t confirm) that it’s an intermittent problem with this particular instance. It seems like I lose connectivity with lemmy.today, and it takes awhile for the client to timeout.

    Sometimes, signing out and signing back in immediately corrects the issue, but not always.

  • tal@lemmy.today
    1·
    11 months ago

    Yeah, I’ve seen some kind of auth error in jerboa. I needed to reauthenticate. I think that that may have been a one-off on the upgrade.

    I saw some sort of temporary errors in jerboa later, but I didn’t need to reauthenticate and they seem to have resolved themselves. I also saw a few errors in the Web UI. That may, though, be related to @mrmanager working on the server in an attempt to work on another upgrade-related issue (messages not propagating to other instances, which has persisted).