Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
kasdobo.copm
I ran this command:
certbot renew
It produced this output:
My web server is (include version)Apach24
The operating system my web server runs on is (include version):
FreeBSD 12.1
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Webmin to help but mostly from command line
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 1.7.0
By default certbot will cease if it encounters this type of error. In order to proceed with testing the rest of the domain names, @kasdivi would need to add --allow-subset-of-names to his certbot command.
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for theoceanwindow.com
http-01 challenge for wandjbrewers.com
http-01 challenge for www.theoceanwindow.com
http-01 challenge for www.wandjbrewers.com
Using the webroot path /usr/local/www/kasdivi.com for all unmatched domains.
Waiting for verification...
Challenge failed for domain theoceanwindow.com
Challenge failed for domain wandjbrewers.com
Challenge failed for domain www.theoceanwindow.com
Challenge failed for domain www.wandjbrewers.com
http-01 challenge for theoceanwindow.com
http-01 challenge for wandjbrewers.com
http-01 challenge for www.theoceanwindow.com
http-01 challenge for www.wandjbrewers.com
Cleaning up challenges
Attempting to renew cert (kasdivi.com) from /usr/local/etc/letsencrypt/renewal/kasdivi.com.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/usr/local/etc/letsencrypt/live/kasdivi.com/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/usr/local/etc/letsencrypt/live/kasdivi.com/fullchain.pem (failure)
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
jason@triggerfish:/usr/local/etc/apache24/extra:
new certificate deployed without reload, fullchain is
/usr/local/etc/letsencrypt/live/kasdivi.com/fullchain.pem
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)
Congratulations, all renewals succeeded. The following certs have been renewed:
/usr/local/etc/letsencrypt/live/kasdivi.com/fullchain.pem (success)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
jason@triggerfish:/usr/local/etc/apache24/extra:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for theoceanwindow.com
http-01 challenge for wandjbrewers.com
http-01 challenge for www.theoceanwindow.com
http-01 challenge for www.wandjbrewers.com
Using the webroot path /usr/local/www/wandjbrewers.com for all unmatched domains.
Waiting for verification...
Challenge failed for domain theoceanwindow.com
Challenge failed for domain www.theoceanwindow.com
http-01 challenge for theoceanwindow.com
http-01 challenge for www.theoceanwindow.com
Cleaning up challenges
Some challenges have failed.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
I mean... that's terrible 
, but I expected it.
