,NOTE: by reloaded - I mean I downloaded and installed as an overlay firefox from the mozilla website.

Yeah.. I'm seeing the same thing. I login and it just refreshes back to the same login page. Hmm..

Turned off uBlock Origin on the site and disabled Enhanced Tracking Protection with no luck.

I even tried a clean profile where I had never logged into the site before with the same behavior.

Ok, this time I loaded up Firefox Beta that I had installed. It's version 144. It does the same thing. Something's messed up on their site.

Yes... I too unloaded Adblock and uBlock with no affect. I have an old computer on my workbench, that still have Firefox from like 2 versions ago and mymercy loads on it. I tried mymercy on 3 computers with the latest version of FF and it returns to login screen. Yet, mymercy loads fine on those same computers with Chrome and Edge. Go figure.

Any relevant-looking messages in the Web Console?

• https://firefox-source-docs.mozilla.org/devtools-user/web_console/

You can check the Network Monitor to see if content is blocked or otherwise fails to load.

• https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/

If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.

I was able to get into it by going to about:preferences#privacy and going to the Cookies and Site Data section and clicking on Manage Data and then removing mercy.net from the list before trying to log in.

I was then able to log into it. In order to log back in after doing this, I have to do the same process to keep from going to the loop of just showing the login prompt each time.

Thanks... yea... I found I could clear everything and it would let me in one time as well... PITA to do that every time, so I just have to remember to use Chrome when I need to login to Mercy.com. Thanks for your help... Firefox changed something in their updates.. hopefully, on the next update, Mercy.com will start working again.

This might be something the site operator needs to fix, as they only know what they're storing in their session/site data.

In case it's just something they set during the login/visit, and break down later when reading that back, I'd suggest using Private Window for them — which will clean up after itself upon closing — so you'll always get a clean slate for them.