Firefox version 76.0.1 (64-bit) will no long log into https://workforcenow.adp.com
I have been using Firefox to log into the ADP site ever since my company changed to them.
Firefox version 76.0.1 (64-bit) will no long log into https://workforcenow.adp.com
Not sure if this was after an update or not. It has worked until a few days ago. Chrome and IE works, but not FF.
ADP gives no errors, just comes back to the same login screen.
Curt
Alle antwurden (5)
Please explain the problem in detail. What happens? What is/are the exact error message(s) ?
I had no problem using v54
Many site issues can be caused by corrupt cookies or cache.
Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.
- How to clear the Firefox cache {web link}
If there is still a problem, Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh). Did this help?
While you are in safe mode;
Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches.
How to disable Hardware Acceleration {web link}
Why are you using this old no longer supported Firefox 76.0.1 version ?
Did you try the current Firefox 82.0 release on possibly a supported Firefox 78.4.0 ESR ?
You can check the Web Console for possible related messages ?
- "3-bar" menu button or Tools -> Web Developer
- https://developer.mozilla.org/en-US/Tools/Web_Console
I have Firefox setup to automatically update. If I go to manually check for updates, it says that I have the latest.
That is why.
Please update to the current Firefox 82.0 release.
If "Help -> About Firefox" isn't working then download and install the current release.
You can find the full version of the current Firefox release (82.0) in all languages and all operating systems here:
It did work fine in Safe Mode.
I was not aware there was a new version. (82.0) I guess I got too dependent upon the auto update.
I will first update to 82.xxx and see if the problem is corrected. If not, I may return.
Thanks so much for your quick responses and helpful info.
KB