updated _acme-challenge.terrasinipalermovacation.com txt record
updated _acme-challenge.terrasinipalermovacationrentals.com txt record
certificates on server with certbot certificates show up to date
site shows expired cert and no padlock whynopadlock.com shows expired certificates "Your SSL certificate is expired! (Expired on: 2024-07-23) You will want to renew your SSL certificate as soon as possible!"
This part of the command you ran tells certbot to just issue the new certificate; it doesn't do anything to install, activate, or otherwise tell any of your software to use that new cert. You still need to do that yourself.
But why are you issuing the cert this way? Both sites are open to the public Internet; surely you can automate better than manually doing DNS validation whenever the cert expires.
Restarted the server now.
It appears that fixed it.
The message from whynopadlock is Expiration Date Your SSL certificate is current. Your SSL certificate expires in 88 days. (2024-10-24)
It won't if you used manual DNS validation--you'd need to issue the cert using an automated method. If the sites are open to the Internet, as they are, I'd expect you should be able to use HTTP validation, which is more easily automated.
Also, the certbot-auto wrapper script doesn't exist any longer. You should never just copy/paste stuff from somewhere without knowing what it actually does.
And the --deploy-hook is stored in the renewal configuration file for the cert, so it doesn't need to go in the cronjob if it's used once.