From: "Wamm K. D." <jaft.r@outlook.com>
To: raingloom <raingloom@riseup.net>
Cc: Ricardo Wurmus <rekado@elephly.net>, help-guix@gnu.org
Subject: Re: Web Browsers Report being "Unable to Connect" after Wi-Fi Connection Drop Period
Date: Tue, 24 May 2022 00:49:12 -0500 [thread overview]
Message-ID: <BY5PR07MB70297B24844F231A826C2E7199D79@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)
In-Reply-To: <20220523234500.56c43841@riseup.net> (raingloom@riseup.net's message of "Mon, 23 May 2022 23:45:00 +0200")
On Mon. (May 23, 2022) at 11:45:00 PM +02, raingloom <raingloom@riseup.net> wrote:
> 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.
Welp; I'd really hoped we had a working workaround but no change,
unfortunately, even with both cleared. I just ran into it, again (hence
being able to test); gonna have to wait this one out.
prev parent reply other threads:[~2022-05-24 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 19:34 Web Browsers Report being "Unable to Connect" after Wi-Fi Connection Drop Period Wamm K. D.
2022-05-23 20:04 ` Ekaitz Zarraga
2022-05-23 20:07 ` raingloom
2022-05-23 21:09 ` Ricardo Wurmus
2022-05-23 21:45 ` raingloom
2022-05-24 5:49 ` Wamm K. D. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BY5PR07MB70297B24844F231A826C2E7199D79@BY5PR07MB7029.namprd07.prod.outlook.com \
--to=jaft.r@outlook.com \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).