Can’t connect to acme-v02.api.letsencrypt.org from Singapore

Help
1

I have two AWS servers in the Singapore region that cannot access acme-v02.api.letsencrypt.org. They report the following errors:

$ openssl s_client -connect acme-v02.api.letsencrypt.org:443 -showcerts
CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 320 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

$ curl -sv https://acme-v02.api.letsencrypt.org
*   Trying 172.65.32.248:443...
* TCP_NODELAY set
* Connected to acme-v02.api.letsencrypt.org (172.65.32.248) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: Connection reset by peer in connection to acme-v02.api.letsencrypt.org:443
* Closing connection 0

The IP addresses of the two servers are: 54.255.55.25 and 18.138.237.72. Are they blocked?

2

Welcome to the community @johnny3

I'll just repeat to you what I said to another Singapore AWS person ...

Does this problem continue? There are temp errors that can occur and I don't know of any outage. Your two posts may just be the first to discover the problem. But, would be helpful to know if it repeats. Thanks

4 Likes
3

@MikeMcQ Thank you for your reply. I just tested and the connection has been restored, although I still don't know the reason.

4 Likes
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.