Error code: 2S119/1 in Firefox 56
I get the Error code: 2S119/1 when I want to sign up to the Briskoda website after putting in my username and password. This error code did not come up in FF 52 ESR and it also does not come up in Waterfox.
Does anyone know what is different or has changed from FF 52 to FF 56 that FF 56 throws up this error?
所有回复 (4)
Any specific reason for using Firefox 56 and not a supported release part from possibly Legacy extension ?
You can try these steps in case of issues with webpages:
You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings).
"Remove the Cookies" for websites that cause problems:
- Settings -> Privacy & Security
Cookies and Site Data: "Manage Data"
"Clear the Cache":
- Settings -> Privacy & Security
Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear
- https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox
- https://support.mozilla.org/en-US/kb/how-clear-firefox-cache
Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window
Thanks for the reply,
I like FF56 for its customization and legacy extensions.
I have tried the cookie and cache routes.
Safe mode does not work either.
I thought there has to be a specific change from FF52 to FF56 and it has to be related to this error code.
I was hoping there might be a setting in about:config.
I just do not have enough clout about FF to know this.
Hi
Please appreciate that Firefox 56 is no longer supported - it is quite a few years old now and there have been many changes to menus and functionality that mean that the issue that you are seeing may now have been resolved in the current version of Firefox.