From: Joost Kremers <joostkremers@fastmail.fm>
To: help-gnu-emacs@gnu.org
Subject: Re: GNU Elpa not reachable (possibly OT)
Date: Tue, 19 Feb 2019 18:03:38 +0100 [thread overview]
Message-ID: <87tvgz4snp.fsf@fastmail.fm> (raw)
In-Reply-To: <m2sgwlm3cf.fsf@gmail.com>
On Mon, Feb 18 2019, Robert Pluim wrote:
>> error in process filter: Error retrieving:
>> https://elpa.gnu.org/packages/archive-contents (error http 400)
>
> Do you get this error straight away, or after a timeout?
It takes a bit of time. Sometimes it doesn't appear at all. I
normally use paradox, which just sits there trying to refresh the
package list. If I disable paradox, I get this error, though not
straight away.
> Any chance of you running tcpdump or wireshark to capture what
> traffic
> Emacs is sending?
tcpdump is installed on my machine, but the man page doesn't tell
me what command I'd have to enter to get the results you're
interested in, so you'd have to help me out a bit.
> You may have a not-quite-working IPv6 setup, which is causing
> Emacs to
> try to connect via IPv6 and failing rather than falling back to
> IPv4.
>
> Could you let us know which version of Emacs this is? Also that
> network trace would be *really* useful.
"GNU Emacs 26.1.91 (build 2, x86_64-pc-linux-gnu, GTK+ Version
3.22.30)\n of 2019-02-04"
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2019-02-19 17:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 14:58 GNU Elpa not reachable (possibly OT) Joost Kremers
2019-02-18 16:19 ` Eli Zaretskii
2019-02-18 21:10 ` Joost Kremers
2019-02-19 0:17 ` Bob Proulx
2019-02-19 3:37 ` Eli Zaretskii
2019-02-19 5:07 ` Bob Proulx
2019-02-19 16:05 ` Eli Zaretskii
2019-02-19 16:59 ` Joost Kremers
2019-02-19 17:05 ` Bob Proulx
2019-02-19 17:27 ` Eli Zaretskii
2019-02-20 9:10 ` Joost Kremers
2019-02-18 17:08 ` Robert Pluim
2019-02-18 18:19 ` Robert Pluim
2019-02-19 17:03 ` Joost Kremers [this message]
2019-02-19 19:08 ` Robert Pluim
2019-02-20 9:42 ` Joost Kremers
2019-02-20 10:15 ` Robert Pluim
2019-03-01 7:27 ` Joost Kremers
2019-03-01 10:02 ` Robert Pluim
2019-03-01 21:06 ` Jude DaShiell
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvgz4snp.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=help-gnu-emacs@gnu.org \
/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).