From: Tim Visher <tim.visher@gmail.com>
To: emacs <help-gnu-emacs@gnu.org>
Subject: Error connecting to TLS ELPA since 27.1
Date: Sat, 26 Sep 2020 08:20:25 -0400 [thread overview]
Message-ID: <CAHa53uxsrL_mNEgRzCVa-3BtKPkp76hCZvYQ+Zaz_RfCtMei5A@mail.gmail.com> (raw)
Hi Everyone,
Since upgrading to 27.1 a few days ago when interacting with ELPA I get the
following error:
```
error in process sentinel: Error retrieving:
https://elpa.gnu.org/packages/archive-contents (error connection-failed
"connect" :host "elpa.gnu.org" \
:service 443)
```
I recall seeing some changes to TLS in the NEWS file this time around. Is
there anything I can do to debug this? I appear to be able to install
packages from ELPA (I just bumped to org 9.4 for instance) so this appears
to be innocuous but obviously I would love for it not to be happening. :)
Thanks in advance!
--
In Christ,
Timmy V.
https://blog.twonegatives.com
http://five.sentenc.es
next reply other threads:[~2020-09-26 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 12:20 Tim Visher [this message]
2020-09-30 17:26 ` Error connecting to TLS ELPA since 27.1 Tim Visher
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=CAHa53uxsrL_mNEgRzCVa-3BtKPkp76hCZvYQ+Zaz_RfCtMei5A@mail.gmail.com \
--to=tim.visher@gmail.com \
--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).