NoInstallationError(«Could not find a usable ‘nginx’ binary

SSL TLS letsencrypt.org

I’m using certbot version 0.31.0

root@vps:~# certbot --version
certbot 0.31.0

And I received via email a string like this:

Could not choose appropriate plugin: The nginx plugin is not working; there may be problems with your existing configuration.
The error was: NoInstallationError("Could not find a usable 'nginx' binary. Ensure nginx exists, the binary is executable, and your PATH is set correctly.",)
Attempting to renew cert (jblanco.org) from /etc/letsencrypt/renewal/jblanco.org.conf produced an unexpected error: The nginx plugin is not working; there may be problems with your existing configuration.
The error was: NoInstallationError("Could not find a usable 'nginx' binary. Ensure nginx exists, the binary is executable, and your PATH is set correctly.",). Skipping.

In the community forum community.letsencrypt.org they say that it is probably related to which certbot cannot find the nginx binary (or perhaps the nginx configuration directory). But this is not the case.

In my case it is a domain (jblanco.org) that I have not renewed.

To put the right context, I have some errors:


Attempting to renew cert (jblanco.org) from /etc/letsencrypt/renewal/jblanco.org.conf produced an unexpected error: Failed authorization procedure. blog.jblanco.org (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for blog.jblanco.org, jblanco.org (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for jblanco.org, aula.jblanco.org (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for aula.jblanco.org, www.jblanco.org (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for www.jblanco.org. Skipping.

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/jblanco.org/fullchain.pem (failure)

/etc/letsencrypt/live/jblanco.org/fullchain.pem (failure)

IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: blog.jblanco.org
Type: None
Detail: DNS problem: NXDOMAIN looking up A for blog.jblanco.org

Domain: jblanco.org
Type: None
Detail: DNS problem: NXDOMAIN looking up A for jblanco.org

Domain: aula.jblanco.org
Type: None
Detail: DNS problem: NXDOMAIN looking up A for aula.jblanco.org

Domain: www.jblanco.org
Type: None
Detail: DNS problem: NXDOMAIN looking up A for www.jblanco.org

With the help option we can see this two options:


manage certificates:
certificates Display information about certificates you have from Certbot
revoke Revoke a certificate (supply --cert-path or --cert-name)
delete Delete a certificate

Then I’ve try first make a revoke, then a delete.

The sintax was:

certbot revoke --cert-path /etc/letsencrypt/archive/jblanco.org/cert1.pem --key-path /etc/letsencrypt/archive/jblanco.org/privkey1.pem
Saving debug log to /var/log/letsencrypt/letsencrypt.log

But I saw an error like this:

An unexpected error occurred:
The client lacks sufficient authorization :: Certificate is expired

Then the option delete, was my solution, but first I disabled the site:

rm /etc/nginx/sites-enabled/jblanco.org.conf

And to make me sure that it was deleted after the next command I perform this command:

root@vps:~# find /etc/letsencrypt/ -name "*jblanco.org*"
/etc/letsencrypt/live/jblanco.org
/etc/letsencrypt/archive/jblanco.org
/etc/letsencrypt/renewal/jblanco.org.conf

Then finally:


certbot delete
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Which certificate(s) would you like to delete?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: jblanco.org
2: ***
3: ***
4: ***
5: ***
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Deleted all files relating to certificate jblanco.org.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

And I put again the find command just to be sure, and voilà!

See you!