I have several certificates that test fine with an autorenew dry run except one which works og and qualsys test fine but the autorenew dry run shows
Attempting to renew cert (gourmetbritain-competition.com) from /etc/letsencrypt/renewal/gourmetbritain-competition.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6… Skipping.
The following certs could not be renewed:
/etc/letsencrypt/live/gourmetbritain-competition.com/fullchain.pem (failure)
…
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
The following certs were successfully renewed:
/etc/letsencrypt/live/cle.bell-computing.com/fullchain.pem (success)
/etc/letsencrypt/live/bell-computing.com/fullchain.pem (success)
/etc/letsencrypt/live/staging.bell-computing.com/fullchain.pem (success)
/etc/letsencrypt/live/pmcarpetsandflooring.com/fullchain.pem (success)
The following certs could not be renewed:
/etc/letsencrypt/live/gourmetbritain-competition.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)
1 renew failure(s), 0 parse failure(s)
I have run netstat -plten and got the following fwiw
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 113 17959 1378/mysqld
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 2163010 11756/nginx
tcp 0 0 127.0.0.1:81 0.0.0.0:* LISTEN 0 17286 1552/httpd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16149 1333/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 18617 1884/master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 2163012 11756/nginx
tcp6 0 0 :::80 :::* LISTEN 0 2163011 11756/nginx
tcp6 0 0 :::22 :::* LISTEN 0 16151 1333/sshd
tcp6 0 0 ::1:25 :::* LISTEN 0 18618 1884/master
tcp6 0 0 :::443 :::* LISTEN 0 2163013 11756/nginx