I think this was a change in Certbot 0.37.0:
This is pure speculation, but if I remember correctly, things can go horribly wrong in Nginx if you disable session caching in one virtual host while leaving it enabled in another virtual host. I wonder if that applies to Apache and session tickets.
Speculating:
-
Hold off on upgrading to Certbot 0.37.0 for now.
-
Adjust or revert the Certbot Apache configuration file. It's named something like
/etc/letsencrypt/options-ssl-apache.conf.
If I understand it correctly, Certbot will automatically upgrade the file if it hasn't been modified. So you could do something like add a comment saying "# XXX upgrade me later`" or something and Certbot would leave the file alone.