LetsEncrypt.sh
Matthias Fechner
idefix at fechner.net
Sat Mar 19 14:58:57 UTC 2016
Am 19.03.2016 um 13:40 schrieb @lbutlr:
> 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-1457179567.csr
> 0 -rw------- 1 443 443 0 Mar 5 05:06 cert-1457179567.pem
> 8 -rw------- 1 443 443 1854 Mar 12 04:35 cert-1457782552.csr
> 0 -rw------- 1 443 443 0 Mar 12 04:35 cert-1457782552.pem
> 8 -rw------- 1 443 443 1854 Mar 19 04:15 cert-1458382543.csr
> 0 -rw------- 1 443 443 0 Mar 19 04:15 cert-1458382543.pem
> 8 -rw------- 1 443 443 3243 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 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 <email> -d <domain1> -d <domain2> ....
The keys are stored in
/usr/local/etc/letsencrypt/live/<domain>/*.pem
Gruß
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
More information about the freebsd-ports
mailing list