unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: GNU Elpa not reachable (possibly OT)
Date: Fri, 01 Mar 2019 08:27:50 +0100	[thread overview]
Message-ID: <875zt35a15.fsf@fastmail.fm> (raw)
In-Reply-To: <874l915ek4.fsf@fastmail.fm>

Hi,

just FYI, this issue appears to be resolved now. elpa.gnu.org is 
pingable again (though it connects to the IPv4 address) and 
updating my packages in Emacs also works again.

Thanks to all who helped fix this.

Best,

Joost

 

On Mon, Feb 18 2019, Joost Kremers wrote:
> Hi all,
>
> The past few days I've been having trouble updating my packages, 
> which turns out
> to be caused by Emacs not being able to reach 
> <https://elpa.gnu.org>. The
> problem isn't that the server is down (it isn't), but I'm not 
> entirely sure what
> the problem is, so I thought I'd post here, in case anyone can 
> help, even though
> it may not be an actual Emacs problem...
>
> Trying to refresh my package list results in the following 
> error:
>
> 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?
>
> Thanks,
>
> Joost


-- 
Joost Kremers
Life has its moments



  parent reply	other threads:[~2019-03-01  7:27 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
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 [this message]
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=875zt35a15.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).