I have a wordpress multisite with a subdomain of staging.bell-computing.com. I have a certificate for it
Certificate Name: staging.bell-computing.com
Domains: staging.bell-computing.com
Expiry Date: 2018-10-01 12:24:09+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/staging.bell-computing.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/staging.bell-computing.com/privkey.pem
What do I need to do to make it recognised? It is in my conf list of other recognised servers and also in the list of domains in serverpilot. When I test it it says there is a name mismatch with gourmetbritain-competition.com.
When I do an autorenew dry run it can renew staging but not gourmetbritain. How do I fix this?
sudo certbot renew --dry-run Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/bell-computing.com.conf
Attempting to parse the version 0.25.1 renewal configuration file found at /etc/letsencrypt/renewal/bell-computing.com.conf with version 0.25.0 of Certbot. This might not work.
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for bell-computing.com
http-01 challenge for www.bell-computing.com
Waiting for verificationâŚ
Cleaning up challenges
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/bell-computing.com/fullchain.pem
Processing /etc/letsencrypt/renewal/staging.bell-computing.com.conf
Attempting to parse the version 0.25.1 renewal configuration file found at /etc/letsencrypt/renewal/staging.bell-computing.com.conf with version 0.25.0 of Certbot. This might not work.
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for staging.bell-computing.com
Waiting for verificationâŚ
Cleaning up challenges
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/staging.bell-computing.com/fullchain.pem
Processing /etc/letsencrypt/renewal/pmcarpetsandflooring.com.conf
Attempting to parse the version 0.25.1 renewal configuration file found at /etc/letsencrypt/renewal/pmcarpetsandflooring.com.conf with version 0.25.0 of Certbot. This might not work.
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for pmcarpetsandflooring.com
http-01 challenge for www.pmcarpetsandflooring.com
Waiting for verificationâŚ
Cleaning up challenges
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/pmcarpetsandflooring.com/fullchain.pem
Processing /etc/letsencrypt/renewal/gourmetbritain-competition.com.conf
Attempting to parse the version 0.25.1 renewal configuration file found at /etc/letsencrypt/renewal/gourmetbritain-competition.com.conf with version 0.25.0 of Certbot. This might not work.
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gourmetbritain-competition.com
http-01 challenge for www.gourmetbritain-competition.com
Cleaning up challenges
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/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.)