Hi

What happens when you try to access the website in Firefox for Android? Is there any error message?

Do you have any add-ons installed in Firefox for Android?

Well, the first time I logged in, there was no problem. (The site is us.whogivesacrap.org, by the way.)

The next day, it just kept taking me back to the log-in screen, no error message, in a continuous loop. I think that was when I used the internal "report broken website" feature for the first time.

I opened a private tab and tried logging in from there. It worked, I logged out when I was done, and closed the private tab. Later that day, I tried the regular page and, when that didn't work, a new private tab.

But the private tab didn't work.

Even though I knew I hadn't forgotten my password, I reset it. That seemed to work, but when I tried to get in by either kind of tab, it took me back to the log-in screen, only now it told me, regardless of which password I used, that the e-mail address and the password didn't match.

Site support tried reactivating my account. I clicked the link that they sent me by e-mail and at that page, asked it to send me a link. That message never came.

Desperate to not run out of toilet paper, I tried DuckDuckGo. I hate it, but it did let me get into my account. The toilet paper is now on its way.

I really do not want to have to switch to DuckDuckGo, but I didn't want to stop using Thunderbird either. Absolutely ignored by that support group even though the problem is a complete inability to send, I had to do something, and FairEmail does send my messages.

On edit: Sorry, re add-ons: AdGuard AdBlocker Dark Reader Privacy Badger UDL Helper

But I have made no changes since the time it worked.

Second edit: I am having similar trouble with chase.com.

Sometimes it lets me in, but when it does, nothing displays correctly. Sometimes right away, sometimes after a few pokes, I get:

"This part of our site doesn't seem to be working right now. Please try again later."

Again, not a blip with DuckDuckGo.

Again, I had signed in with Firefox without trouble before, but it had been more than once before. Could it be just the latest iteration or so of Firefox that is doing it? With auto-updates (something I don't do on my Mac), it's hard to be sure when those happen in relation to the problems.