• Unable to connect

    From Jeff Layman@Jeff@invalid.invalid to alt.comp.software.firefox on Fri Feb 27 08:03:24 2026
    From Newsgroup: alt.comp.software.firefox

    148.0 LM22.3

    After updating to 148.0 from 147.0.4 a few days ago I find that, when
    starting Fx, the last tab it should open (from the previous day's
    session) often shows:

    "Unable to connect

    Firefox canrCOt establish a connection to the server at www.whatever.com."

    Sometimes it spontaneously completes the page after a few seconds, but
    usually it takes a tab reload to get to the full page. Anyone seen
    anything like this? Is it having an issue with some Javascript, perhaps?
    --
    Jeff

    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Andy Burns@usenet@andyburns.uk to alt.comp.software.firefox on Fri Feb 27 09:14:37 2026
    From Newsgroup: alt.comp.software.firefox

    Jeff Layman wrote:

    After updating to 148.0 from 147.0.4 a few days ago I find that, when starting Fx,-a the last tab it should open (from the previous day's
    session) often shows:

    "Unable to connect

    Not seen it, but have probably only restarted a couple of times since
    updating to v148
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to alt.comp.software.firefox on Fri Feb 27 19:25:23 2026
    From Newsgroup: alt.comp.software.firefox

    Jeff Layman <Jeff@invalid.invalid> wrote:

    148.0 LM22.3

    After updating to 148.0 from 147.0.4 a few days ago I find that, when >starting Fx, the last tab it should open (from the previous day's
    session) often shows:

    "Unable to connect

    Firefox canrCOt establish a connection to the server at www.whatever.com."

    Sometimes it spontaneously completes the page after a few seconds, but >usually it takes a tab reload to get to the full page. Anyone seen
    anything like this? Is it having an issue with some Javascript, perhaps?

    Yes, that sounds likely. I think there are remnants of the last session remaining.

    I use the NoScript add on. If I have a crash, or need to shut down and
    restart Firefox, or if I have pages that have been open for too long,
    say 20 minutes on a site that uses a lot of javascript, I have found it necessary to disable NoScript for half a minute, re-enable it, then
    re-allow javascript where I allow it temporarily. I suspect it has to do
    with sites I've allowed permanently to run javascript.

    If you don't use NoScript, you could accomplish the same thing by
    briefly disabling javascript in about:preferences, then re-enabling it.
    That should force a purge of remnants of past sessions on a specific Web
    site.
    --- Synchronet 3.21b-Linux NewsLink 1.2