install can't reach elpa.frontside.io

[EnnoOstendorf]

I tried to install frontmacs by just adding the line from the readme to my ~/.emacs, when starting emacs i get this error:

Debugger entered--Lisp error: (gnutls-error #<process elpa.frontside.io> -12)
  signal(gnutls-error (#<process elpa.frontside.io> -12))
  gnutls-negotiate(:process #<process elpa.frontside.io> :type gnutls-x509pki :hostname "elpa.frontside.io")
[...]

looks to me, that the host elpa.frontside.io is not reachable, pinging it gives me 100% packet loss.

Here is my ~/.emacs:

;; boot frontmacs
(load (expand-file-name "~/.emacs.d/init-frontmacs.el" ))                                                                              

and the init-frontmacs.el is at the right place.

[Robdel12]

Thanks for the bug report @EnnoOstendorf! This is one we should fix ASAP, I'm getting the same issue on my end too.

We're using S3 & cloudfront but ran into SSL issues a while back. I'm betting it has to do with that trickery.

[cowboyd]

If I navigate to https://elpa.frontside.io/archive-contents

Here's what I see:

(1
 (frontmacs .
        [(0 2 17)
         ((f
           (0 19 0))
          (magit
           (2 8 0))
          (git-link
           (0 4 5))
          (git-timemachine
           (3 0))
          (github-clone
           (0 2))
          (swiper
           (0 7 0))
          (counsel
           (0 8 0))
          (flx
           (0 6 1))
          (smex
           (3 0))
          (projectile
           (0 14 0))
          (counsel-projectile
           (20171227 1315))
          (ag
           (0 4 7))
          (exec-path-from-shell
           (1 11))
          (page-break-lines
           (0 11))
          (crux
           (0 3 0))
          (yasnippet
           (0 11 0))
          (mocha-snippets
           (1 0 0))
          (vkill
           (20091203 1022))
          (key-chord
           (20160227 438))
          (hlinum
           (20160521 2112))
          (undo-tree
           (0 6 5))
          (browse-kill-ring
           (2 0 0))
          (ace-window
           (0 9 0))
          (zoom-frm
           (20170125 1953))
          (expand-region
           (0 11 0))
          (comment-dwim-2
           (1 2 2))
          (company
           (0 9 2))
          (flycheck
           (30))
          (diff-hl
           (1 8 4))
          (ruby-tools
           (0 1 2))
          (inf-ruby
           (2 5 0))
          (yari
           (0))
          (rspec-mode
           (1 11))
          (js2-refactor
           (0 8 0))
          (smartparens
           (1 9 0))
          (js2-mode
           (20170624))
          (js-doc
           (20160714 2134))
          (rjsx-mode
           (0 1 3))
          (tide
           (2 3 1))
          (emmet-mode
           (1 0 8))
          (web-mode
           (14 1))
          (markdown-mode
           (2 1))
          (yaml-mode
           (0 0 13))
          (rainbow-mode
           (0 12))
          (diminish
           (0 45))
          (which-key
           (2 0 1))
          (volatile-highlights
           (1 11))
          (multiple-cursors
           (1 4 0))
          (drag-stuff
           (0 3 0))
          (use-package
           (2 3)))
         "Frontside config package for emacs" tar nil]))

Our host does not support ping :( so unfortunately this is not a good diagnostic.

It looks like this might be an SSL error. We use Let's Encrypt to sign our SSL certs, so you will need to have their cert in your trust chain.

[EnnoOstendorf]

Thank you! I don't know, how to add Lets Encrypt to my trust chain. Is the 'trust chain' systemwide or emacs specific? I googled it, but i am obiously to stupid to find the right keywords. I am working on an ubuntu 16.04 TLS VM in our company cloud, the admins say, that must be configured per application, but i don't know where. Would it be an option to remove all 's' in https in the inti-frontmacs.el ?

[cowboyd]

It would definitely be an option, but then you wouldn't be downloading the frontmacs package over a secure connection. I'm not exactly sure how to verify where in the trust chain it's falling over, but here's how I do it on Safari.

[qpre]

Hey !

I don't know if it is related, but it feels like it: when installing, it get's to: Opening TLS connection with ‘openssl s_client -connect elpa.frontside.io:443 -no_ssl2 -ign_eof’...done Then nothing happens.

I'm running OSX (10.13 (17A405)) and emacs 25.2.1.

Any idea on how to get passed this ?

[cowboyd]

@EnnoOstendorf @qpre We're having difficulty reproducing this issue. Would one of you be willing to make your environment available to us to see if we can't diagnose it?

[EnnoOstendorf]

Yes of course: I took a freshly installed vserver or docker image with ubuntu 16.04 minimal image, then in a shell

apt-get update; apt-get install emacs mkdir .emacs.d; cd .emacs.d; wget https://raw.githubusercontent.com/thefrontside/frontmacs/master/scripts/init-frontmacs.el

.emacs file see above

running emacs in the shell with --debug-init produces the error from above. hope this helps

[amarshall]

I had the same issue as @qpre (where it hangs with zero network but 100% CPU) using emacs 25.3.1 on macOS 10.13.3 as installed by Homebrew. However, after reinstalling emacs with --with-gnutls, it succeeds.