Failed to renew certificate

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. crt.sh | 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: allbananas.xyz balticblockchain.com balticweb3.com balticweb3week.com banaan.xyz bananacapital.xyz bananaconf.xyz bananaconference.xyz bananadao.xyz bananaevents.xyz bananaplant.xyz bananaventures.xyz nfttallinn.com nordicweb3.com nordicweb3week.com tallinnblockchain.com tallinnweb3.com tallinnweb3week.com

I ran this command: sudo certbot renew --dry-run

It produced this output: Processing /etc/letsencrypt/renewal/allbananas.xyz.conf


Failed to renew certificate allbananas.xyz with error: The manual plugin is not working; there may be problems with your existing configuration.
The error was: PluginError('An authentication script must be provided with --manual-auth-hook when using the manual plugin non-interactively.')


Processing /etc/letsencrypt/renewal/nfttallinn.com.conf


Simulating renewal of an existing certificate for allbananas.xyz and 21 more domains

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: bananaspace.xyz
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for bananaspace.xyz - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for bananaspace.xyz - check that a DNS record exists for this domain

Domain: nfttallinn.xyz
Type: unauthorized
Detail: 199.59.243.226: Invalid response from http://nfttallinn.xyz/.well-known/acme-challenge/KuI9-hKqDCSKTgBFUQMn7FUJp-9kndGMJkA0Yo0dWzI: "<html data-adblockkey="MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4p"

Domain: nfttln.com
Type: unauthorized
Detail: 199.59.243.226: Invalid response from http://nfttln.com/.well-known/acme-challenge/BMU5TqGznlzNvKJTl3AwD5g4m77Rq_0YgP8aF2rsyJY: "<html data-adblockkey="MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4p"

Domain: nfttln.xyz
Type: unauthorized
Detail: 199.59.243.226: Invalid response from http://nfttln.xyz/.well-known/acme-challenge/8_-maNeUOLVmDLalb6Kp8_hRlqCy4EkDQLXUym54YaI: "<html data-adblockkey="MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4p"

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Failed to renew certificate nfttallinn.com with error: Some challenges have failed.


All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/allbananas.xyz/fullchain.pem (failure)
/etc/letsencrypt/live/nfttallinn.com/fullchain.pem (failure)


2 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 hosting provider, if applicable, is: Google Cloud

I can login to a root shell on my machine (yes or no, or I don't know): T

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.11.0

This problem should be clear enough to sort out. Please review the Certbot docs about renewal when using --manual. If you have specific questions after that please ask them. The --manual topic is here: User Guide — Certbot 2.12.0.dev0 documentation

2 Likes

This problem should be clear too. There is no A and/or AAAA record in the public DNS for that domain name. You must have one of these for people to reach that domain from the public internet. And, Let's Encrypt needs that to reach your server too to validate an HTTP Challenge (which you are using).

Just add the needed A and/or AAAA records (IPv4 and IPv6)

2 Likes

These errors looks like your domain name has expired at your registrar. I just checked this one but all the error messages look similar so probably the same problem. You need to check with NameCheap

3 Likes

Here is what ICANN Lookup shows:

4 Likes

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