Simulating renewal of an existing certificate for driveyourkpis.com and www.driveyourkpis.com
Failed to renew certificate driveyourkpis.com with error: Could not bind TCP port 80 because it is already in use by another process on this system (such as a web server). Please stop the program in question and then try again.
All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/driveyourkpis.com/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
My web server is (include version):
nginx
The operating system my web server runs on is (include version):
Ubuntu 20.04.4 LTS (GNU/Linux 5.13.0-1029-aws x86_64)
I can login to a root shell on my machine (yes or no, or I don't know):
yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot1.30.0
I did not perform the install. Is there a way that I could verify this? (besides asking the person that did the install lol). They said they just followed some tutorials to get it to work but do not recall using the standalone plugin
You could check (and/or post the contents of) the file /etc/letsencrypt/renewal/driveyourkpis.com.conf.
Alternatively, you could just try the following command:
certbot renew --nginx --dry-run
This would tell Certbot to use the nginx plugin instead of the standalone plugin (which is most likely configured now) so it will use nginx itself to perform the challenge.
Note that using --nginx configures Certbot to use the nginx plugin as authenticator as well as the installer. Now, your nginx is already configured for the certificate, so Certbot won't additionally modify your nginx configuration permanently (which it would if it was the first time you'd get a cert), but it does have the additional benefit of reloading your nginx automatically.