Thanks for your help. You're right -- I probably don't need more copies of the certs; the duplicates are a result of having a problem that is not obvious (to me) how to resolve and trying different things. The --renew command verifies my certs are current, they're just in the wrong place.
After a lot of poking around, I've found the folder /etc/letsencrypt/archive/sensorbot.org that seems to have a historic archive of the keys I had when I was using certbot (but which no longer works on my system, hence my switch to acme). I can see how the keys were managed, with new copies sequentially numbered and the latest symlinked to a file referenced in the apache config file. I'm wondering if there's a similar acme-based system for managing the keys, or if I have to rig something equivalent myself.
Also, apache references fullchain,pem and privkey.pem. In my acme certs folder, I have ca.cer, sennsorbot.org.csr, a pair of conf files, and several 0 byte files. How do I figure out how these map onto the keys that apache needs?
To be more specific, my apache config file has this:
and my acme cert folder looks like this:
drwxr-xr-x 2 root root 4096 May 2 02:25 backup
-rw-r--r-- 1 root root 1587 May 2 02:25 ca.cer
-rw-r--r-- 1 root root 0 May 2 02:28 fullchain.cer
-rw-r--r-- 1 root root 0 May 2 02:28 sensorbot.org.cer
-rw-r--r-- 1 root root 717 May 3 22:40 sensorbot.org.conf
-rw-r--r-- 1 root root 972 May 2 02:25 sensorbot.org.csr
-rw-r--r-- 1 root root 208 May 2 02:25 sensorbot.org.csr.conf
-rw-r--r-- 1 root root 0 May 2 02:28 sensorbot.org.key
Which of these files do I need to reference in the apache config file?
PS I tried this command, and modifying my apache config to match... but it didn't help:
./acme.sh --install-cert -d sensorbot.org --cert-file /etc/letsencrypt/live/sensorbot.org/sensorbot.org.cer --key-file /etc/letsencrypt/live/sensorbot.org/sensorbot.org.key --fullchain-file /etc/letsencrypt/live/sensorbot.org/fullchain.cer --reloadcmd "service apache2 force-reload"
It appears the files copied by the command above were 0 bytes, and apache understandably doesn't like that.