"happy hacker fake" cert issued


#1

Hey,

when I install letsencrypt the nginx plugin under Arch LInux, run letsencrypt without arguments, and select one domain, I’m still issued a “fake” cert. Is this intended? Do I still need to provide a --server?

(On a related note, when I select multiple domains, I get this error: https://github.com/letsencrypt/letsencrypt/issues/923.)

Thanks,
Sebastian


#2

Update your letsencrypt client.


#3
$ letsencrypt --version
letsencrypt 0.1.0

Using the --server https://acme-v01.api.letsencrypt.org/directory switch from the closed beta works. But should this still be needed, it needs to be mentioned somewhere, of course. :wink:


#4

Isn’t 0.1.0 like, ancient or something?

Not that I’m a good comparison, as my Gentoo grabs all the files from GitHub every single time I reinstall the client, but hey, 0.2.0.dev0 sounds like a big improvement over 0.1.0 :wink:


#5

That’s the version string still returned by the client, as far as I can tell. Just updated my checkout to confirm.


#6

You sure?


#7

Weird:

~/letsencrypt(branch:master) » git pull
Already up-to-date.

~/letsencrypt(branch:master) » ./letsencrypt-auto --version
Updating letsencrypt and virtual environment dependencies.......
Running with virtualenv: sudo /home/-redacted-/.local/share/letsencrypt/bin/letsencrypt --version
letsencrypt 0.1.0

#8

fresh install me is also 0.1.0


#9

As a further note, the contents of _init_.py on the checkout does show 0.2.0.dev0, but that’s not what the client returns.


#10

Weird… Mine does… ?

server ~ # letsencrypt --version
letsencrypt 0.2.0.dev0
server ~ #```

Anyhow, that shouldn't be the problem, as many of you successfully have gotten certificates with those clients.. Also, I've had the `--server`-var hardcoded in cli.ini since the private beta, so I'm not very helpful in that either :P

#11

Well, 0.1.0 was released two days ago, so I’d consider it “new enough”. The currently developed Git version comes with the “0.2.0.dev0” string.

Anyhow, should the --server switch still be necessary, I’d argue that it should be mentioned in the documentations, instead of scaring new users with a “happy hacker” cert. :wink: