I can only log in when I change my password. I do not know why this happens or how to solve it. The log in button keeps spinning but it does nothing. There must be something I am missing but I don’t know what. I am sorry.
Hit the refresh button on your browser. I’ve been having the same issue and a refresh has solved it!
To be clear: put in your creds, let the spinny thing spin for a few seconds, THEN refresh your browser.
I am doing this but it does nothing for me :(
Most Lemmy instances are seeing a surge in activity; between their own users and activity from across the federation incoming (a lot of new posts and comments to cache, etc). So this is probably causing slow responses.
The API calls aren’t returning fast enough on already-loaded pages (so the existing page shows a spinner waiting for a response) but a fresh page load (possibly taking priority over API calls) is probably returning results to you faster.
This also seems to be what is causing crashes with some of the mobile apps (Mlem has been giving me issues) as it browses just fine but if I try to reply or upvote then it hangs for a bit then crashes (almost like a server confirmation is timing out and it’s not liking that). Not to say these apps are bad; they’re like super-early alpha version and I’m running them from iOS TestFlight.
I really hope this is the answer and that it solves by itself. But i don’t know… I have been trying since Thursday to log in and nothing yet. I’m going to give it more time then. Thank you for your answer.
I am a newbie. Same was happening to me on Firefox. Then I switched to Safari and that seems to remember my log in and lets me in. I am wondering if it is a browser issue (I have ad block on Firefox running).
It is true that I am using Firefox with adblock. But it happens in a clean Microsoft Edge too…
I also think it might be a browser thing. I use Brave with the default ad blocker and I’ve never had this issue happen to me.
Can’t identify the problem, but I feel like this is a very common issue in web design: Failing to account for negative use cases. Ideally, a failure to send a request like “Please log me in!” should remove the loading spinner, and display a generic error screen that absolves the user of blame. Even at professional companies, they sometimes forget to set that up, and so you only see constant loading even though it’s already failed.
