After setting up lets encrypt on my server and running it I end up with the following files: $ ls -nls total 48 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 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 As you can see, the cert…pem files are 0 bytes. I have not gotten the last step I need to take in order to attach these certs to apache so I can switch over to https. Trying to link to the csr files didn’t seem to work, so I am doing something wrong. I am using the lets encrypt.sh port from FreeBSD postmaster (since letsenrypt still isn’t quite native on FreeBSD). Anyone have some pointers or an RTFM link? -- Nihil est--in vita priore ego imperator Romanus fui. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|