I don't know if this is related, but I'm trying to renew a cert (hmcinq.com) on Ubuntu 16.04 using certbot and get:
Cert is due for renewal, auto-renewing...
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Attempting to renew cert from /etc/letsencrypt/renewal/www.hmcinq.com.conf produced an unexpected error: HTTPSConnectionPool(host='acme-v01.api.letsencrypt.org', port=443): Read timed out. (read timeout=45). Skipping.
All renewal attempts failed. The following certs could not be renewed:
1 renew failure(s), 0 parse failure(s)
If I try just visiting https://acme-v01.api.letsncrypt.org/ in my web browser I get:
An error occurred while processing your request.
If I test it in curl I get:
curl https://acme-v01.api.letsencrypt.org -I
HTTP/1.1 504 Gateway Time-out
Expires: Mon, 17 Jul 2017 21:11:43 GMT
Cache-Control: max-age=0, no-cache, no-store
Date: Mon, 17 Jul 2017 21:11:43 GMT
If I ping it it seems up:
PING acme-v01.api.letsencrypt.org (184.108.40.206) 56(84) bytes of data.
64 bytes from acme-v01.api.letsencrypt.org (220.127.116.11): icmp_seq=1 ttl=55 time=38.2 ms
64 bytes from acme-v01.api.letsencrypt.org (18.104.22.168): icmp_seq=2 ttl=55 time=38.2 ms
Visiting status.letsencrypt.org does show the staging server is currently down, but claims acme-v01 is up?