I’ve just double-checked our logs, and I can confirm that there was definitely a validation from Certbot 0.29.1 on 2019-02-09, using the Apache authenticator. That version of Certbot, using that authenticator, should definitely default to using the HTTP-01 challenge even if TLS-SNI-01 is offered.
Can you check if tls-sni-01 is explicitly configured in your renewal config? This could happen if you used the --preferred-challenges=tls-sni-01 flag in the past. You can run
grep tls-sni /etc/letsencrypt/renewal/*
If you do find an example, follow these instructions to fix.
Otherwise, it’s a bit of a mystery what’s going on. It’s 95% likely things will work just fine at your next renewal, but I’d like to understand this better, and see if other people are likely to have the same issue. Can you upload your log file from 2019-02-09? It would be one of the files in /var/log/letsencrypt/.
Thanks,
Jacob