spacemacs

jumar 2022-03-09T08:29:44.636759Z

I have a problem with package-refresh-contents First few times it just looked frozen on "Contacting host: melpa" so I C-g-ed it. Now it looks more responsive but I got an error

Contacting host:  [2 times]
Contacting host: 
Contacting host:  [2 times]
...
error in process sentinel: Error retrieving:  (error connection-failed "connect" :host "" :service 443) [2 times]

practicalli-johnny 2022-03-10T08:02:06.025459Z

When I did a package update just now, I get the following output

(Spacemacs) --> refreshing package archive: melpa... [1/3]
Contacting host: 
Importing package-keyring.gpg...done
Contacting host:  [2 times]
Package refresh done
(Spacemacs) --> refreshing package archive: gnu... [2/3]
Importing package-keyring.gpg...done
Contacting host: 
Package refresh done
(Spacemacs) --> refreshing package archive: nongnu... [3/3]
Importing package-keyring.gpg...done
Contacting host: 
Package refresh done
This is then followed by fetch, update and prepare messages for each package that has a newer version

jumar 2022-03-10T08:26:06.189029Z

Ok, that looks like more stuff than I have in my messages buffer but I really looks like it's just the minibuffer that isn't working/refreshed (at this point)

practicalli-johnny 2022-03-09T10:33:20.901879Z

It could be Melpa itself that is having problems. It's rare, but it happens.

👍 1
jumar 2022-03-09T11:55:50.537269Z

Yeah, it keeps happening.

practicalli-johnny 2022-03-09T12:45:08.076629Z

I assume your not behind a firewall that doesn't like passing HTTPS connections?

Drew Verlee 2022-03-10T06:10:16.962969Z

443 means you tried to use https but something in the network didn't allow it. Is what i read online just now.

practicalli-johnny 2022-03-10T07:44:10.306789Z

443 is the port that is used to connect to Melpa to download the packages. I don't believe it's a status code, as there doesn't seem to be a http status code of that value.

practicalli-johnny 2022-03-10T07:47:26.542299Z

If there are still issues connecting to Melpa, then try using http rather than HTTPS by running Emacs with the --insecure flag

emacs --insecure
This is not a good practice long term, so try find out what is blocking the HTTPS connection. If it's at work, perhaps they have made changes to the company firewall

jumar 2022-03-10T07:52:56.001079Z

Yeah, I don't want to do that. I also posted this in #emacs : https://clojurians.slack.com/archives/C099W16KZ/p1646898664139849

jumar 2022-03-10T07:53:46.295009Z

I would think it's possible that it's a certificate issue but it's weird that emacs says nothing about it.

jumar 2022-03-10T07:55:26.240989Z

Oh, it looks different now! In *Messages*

Importing package-keyring.gpg...done
Contacting host:  [2 times]
Contacting host: 
Contacting host:  [2 times]
Package refresh done
Looks like it succeeded but the minibuffer isn't updated (still shows "Contacting host: http://melpa.org:443"

practicalli-johnny 2022-03-10T07:56:45.097729Z

I think certificate issues affected early versions of Emacs 26. Later Emacs 26 and Emacs27 onwards should be fine.