Je peux lire des réponses en Anglais : oui
Mon nom de domaine est :
fileshare.acroe-ica.org
fileshare.eastndc.eu
www-test.eastndc.eu
J’ai exécuté cette commande :
sudo certbot renew --pre-hook “service haproxy stop” --post-hook “service haproxy start” --renew-hook “/root/haproxy_letsencrypt/concat_certificate.sh”
Elle a produit cette sortie :
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/fileshare.acroe-ica.org.conf
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Running pre-hook command: service haproxy stop
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for fileshare.acroe-ica.org
http-01 challenge for fileshare.eastndc.eu
http-01 challenge for www-test.eastndc.eu
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (fileshare.acroe-ica.org) from /etc/letsencrypt/renewal/fileshare.acroe-ica.org.conf produced an unexpected error: Failed authorization procedure. fileshare.acroe-ica.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://fileshare.acroe-ica.org/.well-known/acme-challenge/Pv7YptWBxv1BxMIyXBQXKGKfYr2hE2YJ5PoOCHOO3pI: Connection refused, fileshare.eastndc.eu (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://fileshare.eastndc.eu/.well-known/acme-challenge/7Xe9O74ONsLq7sngB9XAgB95Sp51RBcdBK8J0VVVamk: Connection refused, www-test.eastndc.eu (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www-test.eastndc.eu/.well-known/acme-challenge/OYGKlvBi4EC5gdNTimRQ4Id06oqjSn_rnXTrY-i_hAs: Connection refused. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/fileshare.acroe-ica.org/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/fileshare.acroe-ica.org/fullchain.pem (failure)
Running post-hook command: service haproxy start
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: fileshare.acroe-ica.org
Type: connection
Detail: Fetching
http://fileshare.acroe-ica.org/.well-known/acme-challenge/Pv7YptWBxv1BxMIyXBQXKGKfYr2hE2YJ5PoOCHOO3pI:
Connection refusedDomain: fileshare.eastndc.eu
Type: connection
Detail: Fetching
http://fileshare.eastndc.eu/.well-known/acme-challenge/7Xe9O74ONsLq7sngB9XAgB95Sp51RBcdBK8J0VVVamk:
Connection refusedDomain: www-test.eastndc.eu
Type: connection
Detail: Fetching
http://www-test.eastndc.eu/.well-known/acme-challenge/OYGKlvBi4EC5gdNTimRQ4Id06oqjSn_rnXTrY-i_hAs:
Connection refusedTo 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.
Mon serveur Web est (inclure la version) :
haproxy
Le système d’exploitation sur lequel mon serveur Web s’exécute est (version incluse) :
Linux srv-203 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Je peux me connecter à un shell root sur ma machine (oui ou non, ou je ne sais pas) :
Oui !
J’utilise un panneau de configuration pour gérer mon site (non, ou fournit le nom et la version du panneau de configuration) :
non
J’utilise let’s encrypt sous ha proxy.
Jusqu’à récemment, la mise à jout des certificats se passait bien.
Depuis quelque jours, échec.
Quelques remarques :
** mon serveur haproxy est je crois bien joignable en HTTP. **
Exemple : http://www-test.eastndc.eu/
** à ma connaissance, aucune modification n’a été faite sur mes accès réseau **
** il ne me semble pas que le problème soit du à l’abandon de tls-sni-01 **
Mais comment puis-je le vérifier ?
merci par avance pour votre aide !!