Hello, I try to renew certificate for my Zimbra (7 ver) mail server (mail.benta.spb.ru), but letsencrypt-auto say that problem with authorization. I try some times and now it say that too many times with bad authorization and I cannot renew my certificate! Oh! All mail in our company is stopped… =( Where I can take off block?
3 month ago I normally renew my certificate, but now error with some authorization. Where I can to fix it?
I want ask:
- How long I am blocking?
- What th e problem with authorization?
I have so message from log of letsencrypt:
[root@mail letsencrypt]# ./letsencrypt-auto renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/mail.benta.spb.ru.conf
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for mail.benta.spb.ru
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (mail.benta.spb.ru) from /etc/letsencrypt/renewal/mail.benta.spb.ru.conf produced an unexpected error: Failed authorization procedure. mail.benta.spb.ru (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://mail.benta.spb.ru/.well-known/acme-challenge/9-sLvAJ3qR-Qg0XWzDdWylqGvdLv1BiBogge8J9ci7s: Timeout during connect (likely firewall problem). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/mail.benta.spb.ru/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/mail.benta.spb.ru/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: mail.benta.spb.ru
Type: connection
Detail: Fetching
http://mail.benta.spb.ru/.well-known/acme-challenge/9-sLvAJ3qR-Qg0XWzDdWylqGvdLv1BiBogge8J9ci7s:
Timeout during connect (likely firewall problem)To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
What I can doing that authorizating will pass?
Whith best regards, Raulina.