[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Web Browsers Report being "Unable to Connect" after Wi-Fi Connection
From: |
raingloom |
Subject: |
Re: Web Browsers Report being "Unable to Connect" after Wi-Fi Connection Drop Period |
Date: |
Mon, 23 May 2022 23:45:00 +0200 |
On Mon, 23 May 2022 23:09:35 +0200
Ricardo Wurmus <rekado@elephly.net> wrote:
> "Wamm K. D." <jaft.r@outlook.com> writes:
>
> > The consequence is that I've noticed a particular behavior
> > relatively frequently: when the connection drops, the browser I'm
> > using will get stuck thinking that it cannot connect to the
> > internet once the internet connection comes back, sometimes
> > (especially if I tried to load a page while the internet connection
> > was down). Trying to load any other page results in the "Unable to
> > Connect" (or equivalent) page.
>
> When this happens again, please visit “about:networking#dns” and clear
> the DNS cache. Maybe this helps.
>
> On Guix System there’s also nscd, which has its own cache. It’s
> possible that a lookup failure is cached there as well. To clear the
> nscd cache use “sudo herd invalidate nscd”.
>
Wouldn't newly opened sites on different domain not be affected by the
cache? When this happens with me IceCat simply does not open
*anything*. Entirely fresh lookups fail.
But I guess just testing the cache clearing solution could easily prove
or disprove the theory. If it really is DNS cache related, then
someone should probably write a bug report upstream.