ctory should also contain
symlinks without timestamp that point to the actual timestamped files.
What does `letsencrypt.sh -c` tells you (and if you are not using this,
what are you using?)
--
Romain Tartière http://people.FreeBSD.org/~romain/
pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95
Am 23.03.2016 um 05:30 schrieb @lbutlr:
My executable is named /usr/local/bin/letsencrypt.sh and does not have a
certonly option.
$ letsencrypt.sh -h
Usage: /usr/local/bin/letsencrypt.sh [-h] [command [argument]] [parameter
[argument]] [parameter [argument]] ...
I have this version
43 Mar 4 23:38 privkey-1457159890.pem
>> 8 -rw--- 1 443 443 3243 Mar 5 05:06 privkey-1457179567.pem
>> 8 -rw--- 1 443 443 3247 Mar 12 04:35 privkey-1457782552.pem
>> 8 -rw--- 1 443 443 3243 Mar 19 04:15 privkey-1458382543.pem
>>
>> Or I am miss
443 3243 Mar 19 04:15 privkey-1458382543.pem
Or I am missing a step.
I use the port security/letsencrypt.sh which is working fine.
I create the keys with:
sudo letsencrypt certonly --webroot
--webroot-path=/usr/local/www/letsencrypt/ --renew-by-default
--agree-tos --email -d -d
The
Is anyone using this port successfully?
It appears to be running here, but is generating some 0 length files:
total 64
8 -rw--- 1 443 443 1854 Mar 4 23:38 cert-1457159890.csr
0 -rw--- 1 443 443 0 Mar 4 23:38 cert-1457159890.pem
8 -rw--- 1 443 443 1854 Mar 5 05:06 cert-1
