Starting a couple of days ago, Voyager couldn’t read my feed from this account (piefed) but I could easily read all local posts. I’ve experienced something similar shortly after some lemmy instances start to get slow (I assume the instances were restarted and flushed the session data).

So I did what I’ve done previously and logged out… except I couldn’t log in back again. I get a red toast saying that the connection failed.

I’ve successfully logged in before with the same version of Voyager, so something else changed. Is there some useful information I can try to extract? (aeharding@vger.social ?)

    • roflo1@feddit.onlineOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      Hold down the “accounts” icon (middle one on the bottom) and then click on Edit in the popup window. Choose the red “stop”/remove icon to logout.

      • Rimu@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 months ago

        Thanks. I logged out and then logged in again fine, on piefed.social.

        I’m using voyager 2.40.1 on Android.

        Which instance, version of Voyager and OS are you using?

        • roflo1@feddit.onlineOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          Thanks! That narrows it down. I’m @feddit.online, Voyager 2.40.1 on iOS 16.7.12 (cue dramatic music)

          • Rimu@piefed.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            2 months ago

            I think I might know what’s causing it - the login is ok but immediately afterwards listing posts fails because there is a new post with a very unusual url. That post is not visible to me so everything seems fine to me.

            feddit.online is usually very good about deploying the latest fixes so I expect it’ll come right in a day or two.

  • roflo1@feddit.onlineOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    Thought I should provide update … It seems to be something else.

    My instance reports to be using PieFed v1.2.5, which should include the fix by !Rimu@piefed.social (if I read the commit logs correctly).
    No luck yet.

    I’ll try to dig somewhere else.
    Next theory to prove/disprove: maybe a character in my password is disliked by … someone.