Lets Encrypt error on Centos 7

5 posts / 0 new
Last post
#1 Wed, 07/31/2019 - 12:36
ckwsp101

Lets Encrypt error on Centos 7

Is this a known issue?

Renewal worked in the past for existing sites.

.. request failed : Web-based validation failed :
usage:
  certbot [SUBCOMMAND] [options] [-d domain] [-d domain] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
cert. Major SUBCOMMANDS are:

  (default) run        Obtain & install a cert in your current webserver
  certonly             Obtain cert, but do not install it (aka "auth")
  install              Install a previously obtained cert in a server
  renew                Renew previously obtained certs that are near expiry
  revoke               Revoke a previously obtained certificate
  register             Perform tasks related to registering with the CA
  rollback             Rollback server configuration changes made during install
  config_changes       Show changes made to server config during installation
  plugins              Display information about installed plugins
letsencrypt: error: unrecognized arguments: --cert-name <redacted_domain>
Webmin version 1.921
Usermin version 1.771
Virtualmin version 6.07
Operating system CentOS Linux 7.6.1810
Mon, 08/05/2019 - 03:51
petecook

I had something similar in the past. After manually installing certbot, virtualmin started using certbot instead of its own built-in letsencrypt scripts, and it failed. Uninstalling certbot unfortunately did not help, since from that moment on Virtualmin insisted on using certbot and moaned not finding it. But there must be a way how to tell Virtualmin to use its own scripts again, unfortunately I dont know how.

Mon, 08/05/2019 - 08:54 (Reply to #2)
Mon, 08/05/2019 - 09:58
ckwsp101

After updating certbot to 0.36.0-1.el7 epel issue resolved. Virtualmin Lets Encrypt working again.

Due to repo configuration error I was using obsolete certbot.

Mon, 08/05/2019 - 10:56
RJM Web Design
RJM Web Design's picture

I've had that happen with Virtualmin's native script when I jumped the gun and didn't wait long enough for DNS to resolve on the new or migrated site. In those cases, it wasn't an error. It was just my own impatience.

--Richard