+1
I have the exact same issue as @Y05H10.
Failed authorization procedure. website.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to XXX.XXX.XXX.XXX:443 for TLS-SNI-01 challenge
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: website.com
Type: connection
Detail: Failed to connect to XXX.XXX.XXX.XXX: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.
The strange thing is I can dig my DNS entry and get all the data that LE says might be wrong (DNS A record is there, IP is correct.) Furthermore I can reach SSH, Port 80 and Port 443 (with test apache servers I setup using self signed certificates) from my computer or through various proxies.
With LE, all means that require LE contacting my server fail (Apache, webroot, standalone). The server is a vanilla Ubuntu box with no firewall etc. set up.
I'm sort of out of ideas - the only thing I can think of is that the place that hosts my servers (servdiscount.com, btw) blocks traffic inbound from letsencrypt's verification servers - for whatever reason they would do that.
I was finally able to resolve it by using Neilpang's ACME Shell Script and using the DNS mode.
However, it still bugs me it doesn't work the way it should... Anybody got any ideas?