"Reset by peer" connecting to Let's encrypt API from Singapore

Help
1

I have a instance on AWS EC2 from Singapore. When my program called the API https://acme-v02.api.letsencrypt.org/directory, I got TCP connection reset.

My IP is 13.215.223.218 or 18.136.12.145

I tested mtr and curl, and here is the information I tested.

[root@console ~]# curl https://acme-v02.api.letsencrypt.org -v
* About to connect() to acme-v02.api.letsencrypt.org port 443 (#0)
*   Trying 172.65.32.248...
* Connected to acme-v02.api.letsencrypt.org (172.65.32.248) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* NSS error -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
* Closing connection 0
curl: (35) TCP connection reset by peer

[root@console ~]# traceroute  acme-v02.api.letsencrypt.org
traceroute to acme-v02.api.letsencrypt.org (172.65.32.248), 30 hops max, 60 byte packets
 1  15.230.209.10 (15.230.209.10)  1.957 ms 15.230.209.64 (15.230.209.64)  7.783 ms 15.230.209.48 (15.230.209.48)  1.378 ms
 2  240.1.168.13 (240.1.168.13)  900.061 ms  899.900 ms  900.198 ms
 3  242.4.77.1 (242.4.77.1)  1.533 ms 242.4.77.135 (242.4.77.135)  1.152 ms 242.4.76.3 (242.4.76.3)  1.699 ms
 4  150.222.3.8 (150.222.3.8)  39.841 ms 150.222.3.6 (150.222.3.6)  39.823 ms 150.222.3.34 (150.222.3.34)  1.265 ms
 5  99.83.90.55 (99.83.90.55)  10.596 ms  10.585 ms  10.573 ms
 6  * 162.158.160.19 (162.158.160.19)  1.941 ms 162.158.160.151 (162.158.160.151)  1.650 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *

12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  *

 * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
2

Welcome to the community @sam_skycloud

I moved your topic to the Help section.

Normally you would be shown a form to fill out but I think your post is clear enough. Interestingly, another poster also complained of "reset by peer" from an AWS EC2 Singapore server.

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

The poster at the other Singapore thread reports the problem has cleared.

Is yours also resolved?

2 Likes
4

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