Renewals failing

[ddyer]

There’s extraneous stuff in the cron job, which runs as root, but the action line is this:

 ../certbot-auto -v --apache renew >> renew.log

Here’s the conf file

renew_before_expiry = 30 days

version = 0.27.1
archive_dir = /etc/letsencrypt/archive/www.boardspace.net
cert = /etc/letsencrypt/live/www.boardspace.net/cert.pem
privkey = /etc/letsencrypt/live/www.boardspace.net/privkey.pem
chain = /etc/letsencrypt/live/www.boardspace.net/chain.pem
fullchain = /etc/letsencrypt/live/www.boardspace.net/fullchain.pem

Options used in the renewal process

[renewalparams]
authenticator = apache
installer = apache
account = f12f2787322263e15c409190710c9595
server = https://acme-v02.api.letsencrypt.org/directory

Here’s a sample from the log file’s daily run.

---

Processing /etc/letsencrypt/renewal/www.boardspace.net.conf

---

Mon Dec 17 17:33:22 UTC 2018

---

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.boardspace.net/fullchain.pem (failure)

---

IMPORTANT NOTES:

• The following errors were reported by the server:

  Domain: www.real-me.net
  Type: unauthorized
  Detail: Invalid response from
  http://www.real-me.net/.well-known/acme-challenge/pAuDJZgIxvo1LJVB-7ed6uvY8o2WYbTfVBtGKi4QVsI:
  “\n\n404 Not
  Found\n\n

  Not Found

  \n<p”

  Domain: boardspace.net
  Type: unauthorized
  Detail: Invalid response from
  http://boardspace.net/.well-known/acme-challenge/kTEJw_dTsawPb77C2C0qmgvmO2vjSzOLnJ13BUw2FaQ:
  “\n\n404 Not
  Found\n\n

  Not Found

  \n<p”

  Domain: real-me.net
  Type: unauthorized
  Detail: Invalid response from
  http://real-me.net/.well-known/acme-challenge/kgjSi3S8q44J6aA0Whvajgijx8b94Cb5j91BkjeUWxA:
  “\n\n404 Not
  Found\n\n

  Not Found

  \n<p”

  Domain: www.boardspace.net
  Type: unauthorized
  Detail: Invalid response from
  http://www.boardspace.net/.well-known/acme-challenge/GOSD4KRAyurF311oy-LUIejDhP5Nz8Vcmi6rm1QAryE:
  “\n\n404 Not
  Found\n\n

  Not Found

  \n<p”

  To fix these errors, please make sure that your domain name was
  entered correctly and the DNS A/AAAA record(s) for that domain
  contain(s) the right IP address.
  Mon Dec 17 17:34:01 UTC 2018