HTTPSConnectionPool error when trying to renew cert


Hi all,

I keep hitting the following error when trying to renew 2 of my certs:

Attempting to renew cert from /etc/letsencrypt/renewal/ produced an unexpected error: HTTPSConnectionPool(host=‘’, port=443): Read timed out. (read timeout=45). Skipping.

I can telnet to the host, it’s pinging as well. here’s a trace route:


Tracing route to []
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home []
2 4 ms 3 ms 4 ms []
3 8 ms 5 ms 9 ms []
4 * * * Request timed out.
5 * * * Request timed out.
6 7 ms 6 ms 7 ms 0.ae4.GW1.EWR19.ALTER.NET []
7 7 ms 7 ms 7 ms []

Trace complete.

any ideas?


I am having the same error and previously showed an error for (Staging)


Having the same issue. Not able to renew the cert.


same here, have now also OSCP stapliing erros on my site…


I have the same Read timeout issue. My log file shows this:

2017-05-19 06:31:40,618:DEBUG:acme.client:Sending GET request to
2017-05-19 06:31:40,620:INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1):
2017-05-19 06:32:25,700:WARNING:certbot.renewal:Attempting to renew cert from /etc/letsencrypt/renewal/ produced an unexpected error: HTTPSConnectionPool(host='', port=443): Read timed out. (read timeout=45). Skipping.
2017-05-19 06:32:25,701:DEBUG:certbot.renewal:Traceback was:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/certbot/", line 418, in handle_renewal_request
    main.renew_cert(lineage_config, plugins, renewal_candidate)
  File "/usr/lib/python2.7/site-packages/certbot/", line 648, in renew_cert
    le_client = _init_le_client(config, auth, installer)
  File "/usr/lib/python2.7/site-packages/certbot/", line 399, in _init_le_client
    return client.Client(config, acc, authenticator, installer, acme=acme)
  File "/usr/lib/python2.7/site-packages/certbot/", line 202, in __init__
    acme = acme_from_config_key(config, self.account.key)
  File "/usr/lib/python2.7/site-packages/certbot/", line 42, in acme_from_config_key
    return acme_client.Client(config.server, key=key, net=net)
  File "/usr/lib/python2.7/site-packages/acme/", line 69, in __init__
  File "/usr/lib/python2.7/site-packages/acme/", line 658, in get
    self._send_request('GET', url, **kwargs), content_type=content_type)
  File "/usr/lib/python2.7/site-packages/acme/", line 631, in _send_request
    response = self.session.request(method, url, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/", line 464, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/site-packages/requests/", line 576, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/", line 433, in send
    raise ReadTimeout(e, request=request)
ReadTimeout: HTTPSConnectionPool(host='', port=443): Read timed out. (read timeout=45)

2017-05-19 06:32:25,701:DEBUG:certbot.main:Exiting abnormally:
Traceback (most recent call last):
  File "/bin/certbot", line 9, in <module>
    load_entry_point('certbot==0.12.0', 'console_scripts', 'certbot')()
  File "/usr/lib/python2.7/site-packages/certbot/", line 896, in main
    return config.func(config, plugins)
  File "/usr/lib/python2.7/site-packages/certbot/", line 702, in renew
  File "/usr/lib/python2.7/site-packages/certbot/", line 435, in handle_renewal_request
    len(renew_failures), len(parse_failures)))
Error: 1 renew failure(s), 0 parse failure(s)

I can telnet on 443



i also debugged the problem.

I cannot get a nonce header back, so i think the APP is down right now !



Having the same issue trying to cert renewal


Is this an official mistake?


Yes, App is down, as you can see here:


Aaaaaaaa!!! WTF!!!


This error is a result of an ongoing service disruption. Please follow for more information. We should have all of the remaining issues resolved shortly.

In the meantime I’m going to lock this thread since there isn’t a need for further discussion on this particular error. Please open a new thread if you need to resume discussion.

Thanks for your patience, we apologize for the disruption and I expect more detailed root cause information will be shared in the near future.