Certbot renewal fails - www.wls-online.net

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: www.wls-online.net

I ran this command: sudo certbot renew

It produced this output:

sudo: unable to resolve host SemMoodle
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/www.wls-online.net.conf

Cert is due for renewal, auto-renewing…
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for www.wls-online.net
Waiting for verification…
Cleaning up challenges
Attempting to renew cert from /etc/letsencrypt/renewal/www.wls-online.net.conf produced an unexpected error: Failed authorization procedure. www.wls-online.net (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: SERVFAIL looking up CAA for wls-online.net. Skipping.

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.wls-online.net/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)


The following errors were reported by the server:

Domain: www.wls-online.net
Type: connection
Detail: DNS problem: SERVFAIL looking up CAA for wls-online.net

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

My web server is (include version):

The operating system my web server runs on is (include version): Debian 8

My hosting provider, if applicable, is: Linode

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): No CP

When I look at my DNS host I see that both wls-online.net and www.wls-online.net are pointed to the same IP and have DNS records. What am I missing as to why it is failing?



Hi @WLS-ITGuy,

You have not configured your DNS zone properly. Right now all requests to wls-online.net returns a refused answer.

As far as I can see, seems you have configured www.wls-online.net as a domain zone instead of create a domain zone for wls-online.net and add there your records.


1 Like

I am not sure I follow. I have a DNS Zone for www.wls-online.net as well as wls-online.net.

When I checked it, wls-online.net zone wasn't configured properly. Now it is working fine and you shouldn't receive the CAA error.

Anyway, you can do what you want, it is correct, but in my opinion, you should only have one zone wls-online.net and add there your records for your subdomains like www etc.


1 Like

I gotcha. I had it backwards. I created a www.wls-online.net zone and had a *.wls-online.net record.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.