Deleted certs cause letsencrypt to fail

Help
1

let me first begin by saying i was not intending to delete the certs but ended up deleting them.
anyway, without the certs i cannot issue certs for this domain or use the certs that existed. i cannot revoke them either since it requires the cert to delete.

interestingly, this also causes the client to fail:

2015-12-12 06:56:57,741:DEBUG:letsencrypt.storage:Expected symlink /etc/letsencrypt/live//cert.pem for cert does not exist.
2015-12-12 06:56:57,742:DEBUG:letsencrypt.cli:Exiting abnormally:
Traceback (most recent call last):
File “/usr/bin/letsencrypt”, line 9, in
load_entry_point(‘letsencrypt==0.1.0’, ‘console_scripts’, ‘letsencrypt’)()
File “/usr/lib/python2.7/site-packages/letsencrypt/cli.py”, line 1283, in main
return args.func(args, config, plugins)
File “/usr/lib/python2.7/site-packages/letsencrypt/cli.py”, line 512, in obtain_cert
_auth_from_domains(le_client, config, domains)
File “/usr/lib/python2.7/site-packages/letsencrypt/cli.py”, line 318, in _auth_from_domains
lineage = _treat_as_renewal(config, domains)
File “/usr/lib/python2.7/site-packages/letsencrypt/cli.py”, line 230, in _treat_as_renewal
config, domains)
File “/usr/lib/python2.7/site-packages/letsencrypt/cli.py”, line 204, in _find_duplicative_certs
candidate_names = set(candidate_lineage.names())
File “/usr/lib/python2.7/site-packages/letsencrypt/storage.py”, line 459, in names
with open(target) as f:
TypeError: coercing to Unicode: need string or buffer, NoneType found

2

probably worth reinstalling the LE script and clearing the /etc/letsencrypt folder as if starting from scratch.

I’d also then make sure you test with the test server, so you don’t hit the rate limits.

3

presume this is Testing Against the Let's Encrypt Staging Environment the test server.

i will try to clear it out and start over although i already it the rate limit trying to fix this.

4

Yes, that’s the test ( staging) server.

It doesn’t have the same limits, so is good for testing ( although the certificates are not recognised by browsers as trusted by default). They’re good for test purposes though.