YetOpen/certbot-zimbra

cat: /etc/ssl/certs/2e5ac55d.0: No such file or directory Error!

yosunpasha opened this issue · 3 comments

I installed Zimbra Certs on April and It expired on July after that I am unable to access everything zmcontrol wont open services not working i fixed this but now when i tried to certs Certbot-zimbra, won't renew certificatse and giving me this error:

root@mail:/opt/zimbra# certbot_zimbra.sh -n -a -H mail.kamburoglu.org -e mail.afyonbasimevi.com
certbot-zimbra v0.7.12 - https://github.com/YetOpen/certbot-zimbra
Checking for dependencies...
Detected Zimbra 8.8.15 on UBUNTU18_64
Using domain mail.kamburoglu.org (as certificate DN)
Got 1 domains to use as certificate SANs: mail.afyonbasimevi.com
Checking zimbra-proxy is running and enabled
Detecting port from zimbraMailProxyPort
Checking if process is listening on port 80 with name "nginx" user "zimbra"
Nginx templates already patched.
Nginx includes already patched, skipping zmproxy restart.
Detecting certbot version...
Detected certbot 1.21.0
Running /usr/bin/certbot certonly  --webroot -w /opt/zimbra/data/nginx/html --cert-name mail.kamburoglu.org -d mail.kamburoglu.org -d mail.afyonbasimevi.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Certificate not yet due for renewal

You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.
(ref: /etc/letsencrypt/renewal/mail.kamburoglu.org.conf)

What would you like to do?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Keep the existing certificate for now
2: Renew & replace the certificate (may be subject to CA rate limits)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Renewing an existing certificate for mail.kamburoglu.org and mail.afyonbasimevi.com

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/mail.kamburoglu.org/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/mail.kamburoglu.org/privkey.pem
This certificate expires on 2022-02-19.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
 * Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
 * Donating to EFF:                    https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Preparing certificates for deployment.
cat: /etc/ssl/certs/2e5ac55d.0: No such file or directory

An error seems to have occurred. Please read the output above for clues and try to rectify the situation.
If you believe this is an error with the script, please file an issue at https://github.com/YetOpen/certbot-zimbra.
root@mail:/opt/zimbra# apt-cache policy ca-certificates
ca-certificates:
  Installed: 20210119~18.04.2
  Candidate: 20210119~18.04.2
  Version table:
 *** 20210119~18.04.2 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
        100 /var/lib/dpkg/status
     20180409 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

When I try another command It gives me another error.

root@mail:/opt/zimbra# certbot --force-renewal --preferred-chain "ISRG Root X1" renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/kamburoglu.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Failed to renew certificate kamburoglu.org 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/mail.kamburoglu.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for mail.kamburoglu.org and mail.afyonbasimevi.com

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The following renewals succeeded:
  /etc/letsencrypt/live/mail.kamburoglu.org/fullchain.pem (success)

The following renewals failed:
  /etc/letsencrypt/live/kamburoglu.org/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 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.

Also I don't get it why renew scheduler won't work.

See #140

I've never seen this error before, did certbot change how the manual plugin works?
PluginError('An authentication script must be provided with --manual-auth-hook when using the manual plugin non-interactively.')

The script uses authenticator "webroot" so I don't know why certbot complains about a manual plugin?