I can’t login to my account. It works both on browser, and on Jerboa v0.34 (latest Jerboa - v.35 has a lot of problems).

  • zachatrocity@lemmy.worldMEnglish
    0·
    2 years ago

    Yeah password is too long probably. I think Lemmy backend limits to 30 chars or something. So you’re sending a longer password in our app and it’s failing

    • PicklesBurgh@lemmy.worldEnglish
      0·
      2 years ago

      I’ve lowered my password to 15 characters and even removed special characters but it still just spins when connecting to lemmy.world

      • zachatrocity@lemmy.worldMEnglish
        1·
        2 years ago

        Are you able to log in with jerboa?

        Not sure what’s going on with your account… most of our app users are on Lemmy.world.

        • PicklesBurgh@lemmy.worldEnglish
          1·
          2 years ago

          Yes, I’m able to log into the same lemmy.world account with both Jerboa and Thunder. I also have a beehaw account, and like V4uban, I am able to log into it using Liftoff.

        • V4uban@lemmy.worldEnglish
          0·
          2 years ago

          Same situation as the person above. Shortened my password to 12 characters, still cannot connect.

          I can connect fine to lemmy.ml and beehaw using Lift off, and I can use that account on lemmy.world on every other Lemmy app (Jerboa, Thunder, Summit, etc )

          • PicklesBurgh@lemmy.worldEnglish
            1·
            2 years ago

            Trying to think of what might be different for us. I know that I created my account before lemmy.world required email verification and I still have not verified. Did you happen to create your lemmy.world account before email verification was required?

          • Galaxy@lemm.eeEnglish
            0·
            2 years ago

            I am having the same issue using this account with liftoff as well it signs into lemm.ee just fine and is signed in fine to Jerboa

            I can also get my sh.itjust.works account to login on liftoff but not this one

            Is there a chance it is to do with the server version being on 17.x instead of 18.x?