I’m having issues connecting to my acc (beehaw.org instance) with mlem
. The web log-in is fine.
I had been able to do log in with mlem
when I first created the account. But once I changed my password (to a stronger pass), logged out of mlem
, I could not log in with mlem
again.
The error message is Could not connect with beehaw.org
.
Also tried uninstalling but didn’t work.
I can’t log into kbin.social as well. I also have a long password (keychain generated)
I am also unable to log in to lemmy.ca
For anyone else with the same problem, make sure to use your username and not your email when logging in. My password manager saved my credentials with the email address as the “username”
I’m having the same issue logging into midwest.social. It shows I’m logged in briefly then gives the red “could not connect to…” banner. It had worked successfully for me a few versions ago.
I figured it out. It shows a successful login then failure to connect when I use my email address to login. If I use my username instead of email everything works.
Glad that worked for you, but unfortunately is not doing the trick for me. I may just need to wait until the next app update to see if that fixes it. (Previous versions of the app worked.)
I just tried logging into beehaw and had no problems. What kind of characters do you have in your password? I tried a password with diacritics, quotes and slashes, and it worked fine.
I think it’s the length of the password that affects log-in from
mlem
. I changed my original password to a shorter one and I can now log in. I also did a couple rounds of changing password (1 more long and 1 more short; both only have-
, numbers and letters), and I was only able to log in with the short one. I didn’t experiment on how long the passwords can be formlem
to be able to take.Hmm, thank you for the insight. I will try it with ridiculously long passwords to see what I can do about it
FWIW, my Beehaw password is currently 15 characters, and I managed to log in ok, in this, my first try of Mlem. I’m enjoying it so far - thank you :)
I’m having the same issue with my own instance, it seems like it may be a bug with the app