From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: GNU Elpa not reachable (possibly OT)
Date: Mon, 18 Feb 2019 18:19:34 +0200 [thread overview]
Message-ID: <83sgwljch5.fsf@gnu.org> (raw)
In-Reply-To: <874l915ek4.fsf@fastmail.fm> (message from Joost Kremers on Mon, 18 Feb 2019 15:58:19 +0100)
> From: Joost Kremers <joostkremers@fastmail.fm>
> Date: Mon, 18 Feb 2019 15:58:19 +0100
>
> error in process filter: Error retrieving:
> https://elpa.gnu.org/packages/archive-contents (error http 400)
>
> Funny thing is, I can paste that URI in the address bar of my
> browser and the file loads just fine.
>
> Looking at this reddit page:
>
> https://www.reddit.com/r/emacs/comments/arnbhb/cant_reach_elpa_for_the_last_couple_of_days/
>
> I tried the same thing as in one of the posts there, and indeed,
> `nslookp elpa.gnu.org` gives me:
>
>
> ```
> Non-authoritative answer:
> Name: elpa.gnu.org
> Address: 209.51.188.89
> Name: elpa.gnu.org
> Address: 2001:470:142:5::89
> ```
>
> and then `ping elpa.gnu.org` yields:
>
> ```
> PING elpa.gnu.org(2001:470:142:5::89 (2001:470:142:5::89)) 56 data
> bytes
> >From 2001:470:142::1 (2001:470:142::1) icmp_seq=1 Destination
> unreachable: Address unreachable
> ```
>
> Several IPv6 test sites tell me my IPv6 connectivity is fine,
> except for one, which states that "Your router or firewall is
> filtering ICMPv6 messages sent to your computer."
>
> So I'm wondering if that may be the cause of the problem and if
> yes, what can I do about it?
Write to savannah-hackers-public@gnu.org with these details.
next prev parent reply other threads:[~2019-02-18 16:19 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 [this message]
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
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=83sgwljch5.fsf@gnu.org \
--to=eliz@gnu.org \
--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).