Certificate not found. Deployment canceled when issuing LetsEncrypt cert

This use to work a few months ago. If I create a new subdomain and try to issue a letsencrypt certificate to it (wo site create sub.domain.com --le --dns=dns_cf) the logs show it is created sucessfully, shows where the cert is located (/etc/letsencrypt/config/sub.domain.com_ecc/sub.domain.com.cer) but then errors out with Certificate not found. Deployment canceled.

System Information

• [Distributor ID: Ubuntu Description: Ubuntu 19.04 Release: 19.04 Codename: disco ] lsb_release -a

• [NGINX (1.16.1 ):

user www-data worker_processes auto worker_connections 50000 keepalive_timeout 8 fastcgi_read_timeout 300 client_max_body_size 100m allow 127.0.0.1 ::1 PHP 7.2 is not installed

MySQL (10.3.22-MariaDB) on localhost:

port 3306 wait_timeout 60 interactive_timeout 28800 max_used_connections 1 datadir /var/lib/mysql/ socket /var/run/mysqld/mysqld.sock my.cnf [PATH] /etc/mysql/conf.d/my.cnf ] wo info

• [nginx version: nginx/1.16.1 (WordOps Nginx-wo) built with OpenSSL 1.1.1d 10 Sep 2019 TLS SNI support enabled configure arguments: --with-cc-opt=‘-g -O2 -fdebug-prefix-map=/build/nginx-yZZjue/nginx-1.16.1=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2’ --with-ld-opt=‘-Wl,-Bsymbolic-functions -Wl,-z,relro -fPIC’ --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --build=‘WordOps Nginx-wo’ --with-debug --with-pcre-jit --with-file-aio --with-threads --with-http_ssl_module --with-http_v2_module --with-http_stub_status_module --with-http_realip_module --with-http_v2_hpack_enc --with-http_auth_request_module --with-openssl-opt=‘enable-ec_nistp_64_gcc_128 enable-tls1_3 no-ssl3-method’ --with-http_addition_module --with-http_geoip_module --with-http_gzip_static_module --with-http_mp4_module --with-http_sub_module --without-http_memcached_module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/headers-more-nginx-module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/nginx-auth-pam --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/nginx-cache-purge --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/nginx-echo --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/nginx-upstream-fair --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/ngx_http_substitutions_filter_module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/memc-nginx-module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/srcache-nginx-module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/HttpRedisModule --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/redis2-nginx-module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/ngx_devel_kit --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/set-misc-nginx-module --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/nginx-module-vts --add-module=/build/nginx-yZZjue/nginx-1.16.1/debian/modules/ngx_brotli ] nginx -V
• [WordOps v3.11.4 ] wo -v
• [OS: Linux 5.3.10-1-pve #1 SMP PVE 5.3.10-1 (Thu, 14 Nov 2019 10:43:13 +0100) x86_64 Shell: /bin/bash PHP binary: /usr/bin/php7.3 PHP version: 7.3.14-1+ubuntu19.04.1+deb.sury.org+1 php.ini used: /etc/php/7.3/cli/php.ini WP-CLI root dir: phar://wp-cli.phar/vendor/wp-cli/wp-cli WP-CLI vendor dir: phar://wp-cli.phar/vendor WP_CLI phar path: /etc/letsencrypt/live WP-CLI packages dir: WP-CLI global config: WP-CLI project config: WP-CLI version: 2.4.0 ] wp cli info --allow-root
• [https://transfer.vtbox.net/fUZt2/wordops.txt ] curl -sL git.io/fjAp3 | sudo -E bash -

[joeyblake]

I am having the same issue. Running WordOps v3.12.2 I have migrated from EasyEngine, so perhaps that has something to do with it.

It seems that the _ecc directory is created in “config” /etc/letsencrypt/config/nextcloud.domain.com_ecc/

But the script is looking for the certificates in “renewal” /etc/letsencrypt/renewal/nextcloud.domain.com_ecc/

I copied the entire nextcloud.domain.com_ecc directory into the “renewal” directory

cp -r /etc/letsencrypt/config/nextcloud.domain.com_ecc /etc/letsencrypt/renewal/nextcloud.domain.com_ecc

and can successfully run

wo site update nextcloud.domain.com --le

[alexdhika]

simple, you just need add this row to /etc/letsencrypt/config/account.conf

CERT_HOME='/etc/letsencrypt/renewal'