Could you help me to renew my certificat 
)
I have all time this problem !
My log;
root@cloud:~# certbot --apache --verbose
Root logging level set at 10
Saving debug log to /var/log/letsencrypt/letsencrypt.log
certbot version: 0.11.1
Arguments: [’–apache’, ‘–verbose’]
Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#webroot,PluginEntryPoint#null,PluginEntryPoint#manual,PluginEntryPoint#standalone)
Requested authenticator apache and installer apache
Single candidate plugin: * apache
Description: Apache Web Server plugin - Beta
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: apache = certbot_apache.configurator:ApacheConfigurator
Initialized: <certbot_apache.configurator.ApacheConfigurator object at 0x7f254969ad50>
Prep: True
Selected authenticator <certbot_apache.configurator.ApacheConfigurator object at 0x7f254969ad50> and installer <certbot_apache.configurator.ApacheConfigurator object at 0x7f254969ad50>
Which names would you like to activate HTTPS for?
1: cloud.moulard.org
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel):
Picked account: <Account(936c8dfdfeb2689cdc12704f734a41aa)>
Sending GET request to https://acme-v01.api.letsencrypt.org/directory.
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
"GET /directory HTTP/1.1" 200 352
Received response:
HTTP 200
Content-Length: 352
Strict-Transport-Security: max-age=604800
Boulder-Request-Id: UvbebtTwz19PNeswhXnTunobNoAWrD2BOTnT7VDif9Q
Expires: Wed, 03 May 2017 14:28:53 GMT
Server: nginx
Connection: keep-alive
Pragma: no-cache
Cache-Control: max-age=0, no-cache, no-store
Date: Wed, 03 May 2017 14:28:53 GMT
X-Frame-Options: DENY
Content-Type: application/json
Replay-Nonce: Bul_7YFRa-7nDih_37FwzR0-c8WRJXHZ1DjzzeA68Bg
{
“key-change”: “https://acme-v01.api.letsencrypt.org/acme/key-change”,
“new-authz”: “https://acme-v01.api.letsencrypt.org/acme/new-authz”,
“new-cert”: “https://acme-v01.api.letsencrypt.org/acme/new-cert”,
“new-reg”: “https://acme-v01.api.letsencrypt.org/acme/new-reg”,
“revoke-cert”: “https://acme-v01.api.letsencrypt.org/acme/revoke-cert”
}
parse (top of loop): [30 days][]
CRE_UNITS matched
parse (bottom) [][30 days][][]
weekday False, dateStd False, dateStr False, time False, timeStr False, meridian False
dayStr False, modifier False, modifier2 False, units True, qunits False
_evalString(30 days, time.struct_time(tm_year=2017, tm_mon=5, tm_mday=3, tm_hour=14, tm_min=28, tm_sec=53, tm_wday=2, tm_yday=123, tm_isdst=0))
_buildTime: [30 ][][days]
units days --> realunit days
return
Should renew, less than 30 days before certificate expiry 2017-05-01 12:28:00 UTC.
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Requesting fresh nonce
Sending HEAD request to https://acme-v01.api.letsencrypt.org/acme/new-authz.
“HEAD /acme/new-authz HTTP/1.1” 405 0
Received response:
HTTP 405
Content-Length: 91
Allow: POST
Boulder-Request-Id: XhFO4hnZXrNVctdLAh5t8lYKMui_JIuuA_GmQNLpWtY
Expires: Wed, 03 May 2017 14:28:53 GMT
Server: nginx
Connection: keep-alive
Pragma: no-cache
Cache-Control: max-age=0, no-cache, no-store
Date: Wed, 03 May 2017 14:28:53 GMT
Content-Type: application/problem+json
Replay-Nonce: w3VO_DzJKAANA20lHXQS2rYJmj98eUrBjLo68ZBjllk
Storing nonce: w3VO_DzJKAANA20lHXQS2rYJmj98eUrBjLo68ZBjllk
JWS payload:
{
“identifier”: {
“type”: “dns”,
“value”: “cloud.moulard.org”
},
“resource”: “new-authz”
}
Sending POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz:
{
“header”: {
“alg”: “RS256”,
“jwk”: {
“e”: “AQAB”,
“kty”: “RSA”,
“n”: “uNFYM7q0pxH4OnwMC_2ZkDWkzRgDFeJUCFEm-p3yQQjuCOH5A8vlXaHx3HNrkWqq9NDsfGgMWaFXlamOauUA6Nlp3lk_NEmT_dA7ng4XNMDFtrPjhw4D3HigUOkwkyWwpbMl5ZFqoeN8cUr7Zg2mFSnkbyerO0wnccqWz_rgbJ1BbN7rK-qZaYLnIbNi3rr9YbjzAfrfeIJTLxcDZQsz-uRHL-yD5Q8SZQuw0MaYjw8GtM3UiFBUcJHft7Dy_pOKzXdwzo48E4n3j2wl4nAx9Z2zNa2cKupub0HTsz5Ix11tKCEz_hmdjW5QPaC9sDUaqaGvEk71qhwvphfqUL6rVQ”
}
},
“protected”: “eyJub25jZSI6ICJ3M1ZPX0R6SktBQU5BMjBsSFhRUzJyWUptajk4ZVVyQmpMbzY4WkJqbGxrIn0”,
“payload”: “ewogICJpZGVudGlmaWVyIjogewogICAgInR5cGUiOiAiZG5zIiwgCiAgICAidmFsdWUiOiAiY2xvdWQubW91bGFyZC5vcmciCiAgfSwgCiAgInJlc291cmNlIjogIm5ldy1hdXRoeiIKfQ”,
“signature”: “R8XhaWinaZaiYfF-uDV-MHDmQYr_rihdpYRr9kE3Vp3x-kB46Fajxc9q8MbBqiwgJSJRZRE1GFSPQOjrF8Cmmmel9ZIsPmy4CGWVIaOvUhdsJ0TqT1kDLczLl2pFbte8y88eqIJ4fg0Qt0h9ZX0JKB4k4eVjjS64DDdf8HDFQ2s0k7VYVLlmaFnd1062PUO3Q2tgn5eAreysEipCrpQsm5a_C6eGsd5nMP9lm8cuUCpPdmXRr3jnLcNFGME_ErAdNKEGihNGZGqoSbVCVILQWw11VgNG6MZYJy55nfIDZtola1ypYL3H-BrmISb5NaX8XeIYaTHQllFjCYsL8zHkig”
}
“POST /acme/new-authz HTTP/1.1” 201 1005
Received response:
HTTP 201
Content-Length: 1005
Strict-Transport-Security: max-age=604800
Boulder-Request-Id: UmQei6f0Zv3pGL55WE3ZlPmcY18Rp4TP68jYuQljjOM
Boulder-Requester: 6416818
Expires: Wed, 03 May 2017 14:28:54 GMT
Server: nginx
Connection: keep-alive
Link: https://acme-v01.api.letsencrypt.org/acme/new-cert;rel="next"
Location: https://acme-v01.api.letsencrypt.org/acme/authz/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk
Pragma: no-cache
Cache-Control: max-age=0, no-cache, no-store
Date: Wed, 03 May 2017 14:28:54 GMT
X-Frame-Options: DENY
Content-Type: application/json
Replay-Nonce: 7P4Ysqp3K3ddqbce28mxDrAvO3b5Z0_EPK9i0exlkV8
{
“identifier”: {
“type”: “dns”,
“value”: “cloud.moulard.org”
},
“status”: “pending”,
“expires”: “2017-05-10T14:28:54.074837739Z”,
“challenges”: [
{
“type”: “tls-sni-01”,
“status”: “pending”,
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902566”,
“token”: “482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4”
},
{
“type”: “http-01”,
“status”: “pending”,
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902569”,
“token”: “5UjCMjdiveMZqvSKWMvKyR8xOxKvqr3FgzR-o5tFcG0”
},
{
“type”: “dns-01”,
“status”: “pending”,
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902570”,
“token”: “oTJh018Mi8kNocmrPhHBzTAWxW_85UzWdsdPFPQ3ncM”
}
],
“combinations”: [
[
2
],
[
0
],
[
1
]
]
}
Storing nonce: 7P4Ysqp3K3ddqbce28mxDrAvO3b5Z0_EPK9i0exlkV8
Performing the following challenges:
tls-sni-01 challenge for cloud.moulard.org
Adding Include /etc/apache2/le_tls_sni_01_cert_challenge.conf to /files/etc/apache2/apache2.conf
writing a config file with text:
<VirtualHost *:443>
ServerName 11629ff4f98208a8bbaa51c7eddc8247.a543a0da26b87bbc7f1a4f0e4a7f6c83.acme.invalid
UseCanonicalName on
SSLStrictSNIVHostCheck on
LimitRequestBody 1048576
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /var/lib/letsencrypt/482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4.crt
SSLCertificateKeyFile /var/lib/letsencrypt/482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4.pem
DocumentRoot /var/lib/letsencrypt/tls_sni_01_page/
Creating backup of /etc/apache2/ports.conf
Creating backup of /etc/apache2/apache2.conf
Waiting for verification…
JWS payload:
{
“keyAuthorization”: “482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4.M-D0FPuVtPZedbURF6AQ7cRQg3BF3WH9b7pnK-k5IbA”,
“type”: “tls-sni-01”,
“resource”: “challenge”
}
Sending POST request to https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902566:
{
“header”: {
“alg”: “RS256”,
“jwk”: {
“e”: “AQAB”,
“kty”: “RSA”,
“n”: “uNFYM7q0pxH4OnwMC_2ZkDWkzRgDFeJUCFEm-p3yQQjuCOH5A8vlXaHx3HNrkWqq9NDsfGgMWaFXlamOauUA6Nlp3lk_NEmT_dA7ng4XNMDFtrPjhw4D3HigUOkwkyWwpbMl5ZFqoeN8cUr7Zg2mFSnkbyerO0wnccqWz_rgbJ1BbN7rK-qZaYLnIbNi3rr9YbjzAfrfeIJTLxcDZQsz-uRHL-yD5Q8SZQuw0MaYjw8GtM3UiFBUcJHft7Dy_pOKzXdwzo48E4n3j2wl4nAx9Z2zNa2cKupub0HTsz5Ix11tKCEz_hmdjW5QPaC9sDUaqaGvEk71qhwvphfqUL6rVQ”
}
},
“protected”: “eyJub25jZSI6ICI3UDRZc3FwM0szZGRxYmNlMjhteERyQXZPM2I1WjBfRVBLOWkwZXhsa1Y4In0”,
“payload”: “ewogICJrZXlBdXRob3JpemF0aW9uIjogIjQ4Mm11cHlMQ1F2ei0yVnV6Nmp0Y09CWnFsWHVVODhJc1dYc1VHRXhBTDQuTS1EMEZQdVZ0UFplZGJVUkY2QVE3Y1JRZzNCRjNXSDliN3BuSy1rNUliQSIsIAogICJ0eXBlIjogInRscy1zbmktMDEiLCAKICAicmVzb3VyY2UiOiAiY2hhbGxlbmdlIgp9”,
“signature”: “c7FBXk4ZLdBxtBfPg7k1Ghu7h3TnGMrgzBN4_RhGhKZ83Yvo0_w2POh0mq2BCYb_i8HjRNZlX8IRpzCeggiwGTMkGq0YuqwL0eojI_cpqPmV8b_yKVQKGKqrv7Lpjvjtp4CpPa7udircHKO_iq7Eb5mLWH_pR2YAV6itmzgSEJ7J753juSyzJWK9uRLtgA-Fz95lV5SxVNIW1ojZpHL1g_8z3bgDhmASNwxvhjFnkGaVIU2nsfXg2zPxnQuH2zbwRF4aYZzSf19T49Fz2wj5g29R8U1c7zjm1FjNF6a82x2wO1hFMGvtKoRv4GcjUX1TC4FVUu95Uf27YFv-b3gZdQ”
}
“POST /acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902566 HTTP/1.1” 202 339
Received response:
HTTP 202
Content-Length: 339
Boulder-Request-Id: Rerwy4T0u_L49bFsotUCsbxKqXkEK4tgzOoYK-YaYPc
Boulder-Requester: 6416818
Expires: Wed, 03 May 2017 14:28:58 GMT
Server: nginx
Connection: keep-alive
Link: https://acme-v01.api.letsencrypt.org/acme/authz/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk;rel="up"
Location: https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902566
Pragma: no-cache
Cache-Control: max-age=0, no-cache, no-store
Date: Wed, 03 May 2017 14:28:58 GMT
Content-Type: application/json
Replay-Nonce: 3clRvFmGARKWHIV5ILOIwUWxIUofbKspxROACQL2Mag
{
“type”: “tls-sni-01”,
“status”: “pending”,
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902566”,
“token”: “482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4”,
“keyAuthorization”: “482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4.M-D0FPuVtPZedbURF6AQ7cRQg3BF3WH9b7pnK-k5IbA”
}
Storing nonce: 3clRvFmGARKWHIV5ILOIwUWxIUofbKspxROACQL2Mag
Sending GET request to https://acme-v01.api.letsencrypt.org/acme/authz/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk.
“GET /acme/authz/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk HTTP/1.1” 200 1524
Received response:
HTTP 200
Content-Length: 1524
Strict-Transport-Security: max-age=604800
Boulder-Request-Id: lgwbNDOVWUvKftDLGYwCP8OhShhatckl88Z8o5yEafM
Expires: Wed, 03 May 2017 14:29:02 GMT
Server: nginx
Connection: keep-alive
Link: https://acme-v01.api.letsencrypt.org/acme/new-cert;rel="next"
Pragma: no-cache
Cache-Control: max-age=0, no-cache, no-store
Date: Wed, 03 May 2017 14:29:02 GMT
X-Frame-Options: DENY
Content-Type: application/json
Replay-Nonce: gwa4OQvVaPhCU6k0cYaRbfbcqQf0EOh6EJNAsfJ5DfQ
{
“identifier”: {
“type”: “dns”,
“value”: “cloud.moulard.org”
},
“status”: “invalid”,
“expires”: “2017-05-10T14:28:54Z”,
“challenges”: [
{
“type”: “tls-sni-01”,
“status”: “invalid”,
“error”: {
“type”: “urn:acme:error:connection”,
“detail”: “Failed to connect to 84.39.33.18:443 for tls-sni-01 challenge”,
“status”: 400
},
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902566”,
“token”: “482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4”,
“keyAuthorization”: “482mupyLCQvz-2Vuz6jtcOBZqlXuU88IsWXsUGExAL4.M-D0FPuVtPZedbURF6AQ7cRQg3BF3WH9b7pnK-k5IbA”,
“validationRecord”: [
{
“hostname”: “cloud.moulard.org”,
“port”: “443”,
“addressesResolved”: [
“84.39.33.18”
],
“addressUsed”: “84.39.33.18”
}
]
},
{
“type”: “http-01”,
“status”: “pending”,
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902569”,
“token”: “5UjCMjdiveMZqvSKWMvKyR8xOxKvqr3FgzR-o5tFcG0”
},
{
“type”: “dns-01”,
“status”: “pending”,
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/DHB3z49MRy-sOHZtgflZKdaZkDTqiYQdpUCwR5yHUjk/1119902570”,
“token”: “oTJh018Mi8kNocmrPhHBzTAWxW_85UzWdsdPFPQ3ncM”
}
],
“combinations”: [
[
2
],
[
0
],
[
1
]
]
}
Reporting to user: The following errors were reported by the server:
Domain: cloud.moulard.org
Type: connection
Detail: Failed to connect to 84.39.33.18:443 for tls-sni-01 challenge
To fix these errors, please make sure that your domain name was entered correctly and the DNS A 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.
Cleaning up challenges
Exiting abnormally:
Traceback (most recent call last):
File “/usr/bin/certbot”, line 11, in
load_entry_point(‘certbot==0.11.1’, ‘console_scripts’, ‘certbot’)()
File “/usr/lib/python2.7/dist-packages/certbot/main.py”, line 882, in main
return config.func(config, plugins)
File “/usr/lib/python2.7/dist-packages/certbot/main.py”, line 608, in run
action, lineage = _auth_from_available(le_client, config, domains, certname)
File “/usr/lib/python2.7/dist-packages/certbot/main.py”, line 104, in _auth_from_available
renewal.renew_cert(config, domains, le_client, lineage)
File “/usr/lib/python2.7/dist-packages/certbot/renewal.py”, line 296, in renew_cert
new_certr, new_chain, new_key, _ = le_client.obtain_certificate(domains)
File “/usr/lib/python2.7/dist-packages/certbot/client.py”, line 265, in obtain_certificate
self.config.allow_subset_of_names)
File “/usr/lib/python2.7/dist-packages/certbot/auth_handler.py”, line 77, in get_authorizations
self._respond(resp, best_effort)
File “/usr/lib/python2.7/dist-packages/certbot/auth_handler.py”, line 134, in _respond
self._poll_challenges(chall_update, best_effort)
File “/usr/lib/python2.7/dist-packages/certbot/auth_handler.py”, line 198, in _poll_challenges
raise errors.FailedChallenges(all_failed_achalls)
FailedChallenges: Failed authorization procedure. cloud.moulard.org (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to 84.39.33.18:443 for tls-sni-01 challenge
Failed authorization procedure. cloud.moulard.org (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to 84.39.33.18:443 for tls-sni-01 challenge
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: cloud.moulard.org
Type: connection
Detail: Failed to connect to 84.39.33.18:443 for tls-sni-01
challengeTo fix these errors, please make sure that your domain name was
entered correctly and the DNS A 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.
root@cloud:~#
