URL: https://linuxfr.org/forums/linux-debian-ubuntu/posts/letsencrypt-error-getting-validation-data Title: letsencrypt : Error getting validation data Authors: electro575 Date: 2017年10月29日T14:05:00+01:00 License: CC By-SA Tags: debian Score: -1 Bonjour à tous, J'essaie de mettre en place une communication sécurisé de type SSL Dans mon ancienne configuration de raspberry pi 2 debian jessie, je me servait de ces deux fichiers de config avec nginx : **/etc/letsencrypt/live/serveur1.domaine.fr/fullchain.pem ; /etc/letsencrypt/live/serveur1.domaine.fr/privkey.pem ;** Depuis que je suis passé à debian stretch sur la raspberry pi2, je n'arrive plus à regénérer ces deux fichiers ci-dessus. J'ai lancé cette commande et voici le log correspondant : ```bash root@raspberrypi:/opt/letsencrypt# letsencrypt certonly --domains serveur1.domaine.fr --email essai@courrier.com Saving debug log to /var/log/letsencrypt/letsencrypt.log How would you like to authenticate with the ACME CA? ------------------------------------------------------------------------------- 1: Spin up a temporary webserver (standalone) 2: Place files in webroot directory (webroot) ------------------------------------------------------------------------------- Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1 Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for serveur1.domaine.fr Waiting for verification... Cleaning up challenges Failed authorization procedure. serveur1.domaine.fr (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Error getting validation data IMPORTANT NOTES: - The following errors were reported by the server: Domain: serveur1.domaine.fr Type: connection Detail: Error getting validation data 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. ``` Est-ce un problème de permission ? Un souci de port ? Pourtant je ne pense pas avoir de problème à ce niveau la Merci d'avance