Having freshly followed these instructions, I am dealing with a slightly different problem. I get the following errors, presumably when the trigger is trying to get a new certificate. I can get a new cert on the command line, but this seems to suggest that acme.sh has exited by the time the request comes back in when automatically triggered.  Obviously, this also triggers all kinds of other alerts throughout our devops. Any suggestions as to where I can look at any logs and why this might be happening? Syslog has failed to reveal anything of import.     Thanks,   M.   15/Feb/2019:19:44:15 +0000 INFO Virtual Server  staging-SSL : "Connect failure - Connection refused"    S ******** "letsencrypt" "127.0.0.1:88" - "-" w 491 0 0 0 0 0 0 0 - GET "https://staging.********/.well-known/acme-challenge/13362ac3-f3e3-4638-91d8-50ed18a36158"     15/Feb/2019:19:44:15 +0000 SERIOUS Pool  letsencrypt : Pool has no back-end nodes responding ... View more