You are logging into lemmy ml instance which is at capacity so it's struggling. I created another account on another instance and now all is fine while previously I couldn't login either.

edit: as @[email protected] correctly mentioned, OP asked about the lemmy.click instance which is a mistake on my part. That still doesn't completely solve the issue as the Reddit exodus is putting a massive strain on all instances as more and more are getting removed from the suggestion list due to being at capacity. This along with the platform being not mature enough is going to cause issues. Best way to resolve these, is to place them in the github issues with descriptions.

I'm seeing this error too.

However the instance I've joined isn't on the list. Not sure what that means for being able to access through the app.

For me, I had to wait about a day and then it worked for me.

Issues I've heard of in the last few days:

• I've heard that Jerboa returns incorrect-login on passwords that contain a comma. Try changing your password via the web-ui if it contains one.
• I've heard that Jerboa returns incorrect-login on passwords longer than... 60 characters I think?
• Jerboa is confused. Force-stop it in application settings or restart your phone. Weird half-logged in states can happen in the face of network interruptions, and Jerboa never self-recovers. You have to kill it. It doesn't SOUND like this is happening to you, but can't hurt to restart Jerboa.
• I assume your account was working and approved, both the web ui and jerboa will return incorrect login if your account is pending admin approval (not every server requires admin approval... but the ones that do have an approval step have a delay before your account is available.