Problem with TLS cert renewal when site was renamed and replaced

[jernst]

Somehow host example.com with site id s1111 ended up having site id s2222 in the paths in certbot's config file. So certbot put the challenge response into the wrong directory, and letsenrypt failed to renew. This may have something to do with an old site having been renamed, and a new site being put in place at example.com.

An unusual case, but worth capturing.