update
net::ERR_CLEARTEXT_NOT_PERMITTED
net::ERR_CLEARTEXT_NOT_PERMITTED
Can you extend support for today only?
Hi, I have 2 machines (Win10 and Win11) with FF 140.3.1esr (32-bit) installed which demonstrates the same failure when I enter one site's url: PR_CONNECT_RESET_ERROR C… (læs mere)
Hi,
I have 2 machines (Win10 and Win11) with FF 140.3.1esr (32-bit) installed which demonstrates the same failure when I enter one site's url:
PR_CONNECT_RESET_ERROR
Chrome at the same machines goes at this url w/o any failures. Any ideas what to change on "about:config" in FF to allow it opening this url w/o such error?
We recently update Firefox with version 138.0 and now getting the message "Gah. Your tab just crashed" when opening the browser. We attempted to update and install vers… (læs mere)
We recently update Firefox with version 138.0 and now getting the message "Gah. Your tab just crashed" when opening the browser.
We attempted to update and install version 138.0.1 only resulting with the same error. We also found and attempted the following all resulting with the same error: - change the about:config page for settings to false for both browser.tabs.remote.autostart and browser.tabs.remote.autostart.2
- clear browser cache.
- enable Temporary Mode in the Help menu. This appears to fix the problem but only for the current browser session. When a new Firefox window is opened, the error reappears.
What is needed to resolve this error or is there a way to permanently enable Temporary Mode or some similar setting? Thanks for all your help with this.
We have an application running on Firefox and noticed that with new Firefox ESR, Ajax call (XMLHttpRequest ) from js script running on Firefox browser on thin clients see… (læs mere)
We have an application running on Firefox and noticed that with new Firefox ESR, Ajax call (XMLHttpRequest ) from js script running on Firefox browser on thin clients seems to be blocked frequently (same call succeed most of the time, but blocked from time to time). Issue was raised starting with Firefox 128.2.0esr), but in general persist with newer Firefox ESR. We tried replacing XMLHttpRequest with fetch which seems making no much difference so far.