Followup on [Bug 235277] www/apache24: py36-certbot failing after updating apache24

[Gerard Seibert]

I filed BUG 235277 yesterday. That bug was shown as fixed, I updated my
ports tree last night and updated the port. My system now shows:

~ $ uname -a
FreeBSD scorpio.seibercom.net 12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC  amd64

~ $ freebsd-version
12.0-RELEASE-p2

~ $ pkg info py36-certbot
py36-certbot-0.30.2_2,1
Name           : py36-certbot
Version        : 0.30.2_2,1

~ $ pkg info py36-certbot-apache
py36-certbot-apache-0.30.2_1
Name           : py36-certbot-apache
Version        : 0.30.2_1

~ $ pkg info apache24
apache24-2.4.38
Name           : apache24
Version        : 2.4.38

~ $ pkg info python36
python36-3.6.8
Name           : python36
Version        : 3.6.8

When attempting to run certbot to update my certificates, this command
line message is displayed:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /usr/local/etc/letsencrypt/renewal/seibercom.net.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert is due for renewal, auto-renewing...
Non-interactive renewal: random delay of 111 seconds
Could not choose appropriate plugin: The apache plugin is not working; there may be problems with your existing configuration.
The error was: NoInstallationError('Could not find configuration root',)
Attempting to renew cert (seibercom.net) from /usr/local/etc/letsencrypt/renewal/seibercom.net.conf produced an unexpected error: The apache plugin is not working; there may be problems with your existing configuration.
The error was: NoInstallationError('Could not find configuration root',). Skipping.
All renewal attempts failed. The following certs could not be renewed:
  /usr/local/etc/letsencrypt/live/seibercom.net/fullchain.pem (failure)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

All renewal attempts failed. The following certs could not be renewed:
  /usr/local/etc/letsencrypt/live/seibercom.net/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 renew failure(s), 0 parse failure(s)

This is the actual command that is being issued via CRON:

/usr/local/bin/certbot renew --apache --deploy-hook "service dovecot restart" --deploy-hook "/usr/home/gerard/Scripts/Monit_SSL_Updater.sh"

I have attached the letsencrypt log file.

What I want to know is if this is a problem on my side or is there
still a bug with certbot?

Thanks!

-- 
Gerard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: letsencrypt.log
Type: application/octet-stream
Size: 5041 bytes
Desc: letsencrypt.log
URL: <http://lists.freebsd.org/pipermail/freebsd-python/attachments/20190129/e92326ce/attachment.obj>