# Activation and renewal errors
**URL:** https://community.letsencrypt.org/t/activation-and-renewal-errors/207219
**Category:** Help
**Created:** [October 24, 2023, 4:30pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219 "2023-10-24T16:30:16Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@mmfacc](https://community.letsencrypt.org/u/mmfacc)
#### Post date: [October 24, 2023, 4:30pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/1 "2023-10-24T16:30:16Z")
POST request to [https://acme-v02.api.letsencrypt.org/acme/authz-v3/277007748486](https://acme-v02.api.letsencrypt.org/acme/authz-v3/277007748486) failed: cURL error 35: TCP connection reset by peer (see [libcurl - Error Codes](https://curl.haxx.se/libcurl/c/libcurl-errors.html)) for [https://acme-v02.api.letsencrypt.org/acme/authz-v3/277007748486](https://acme-v02.api.letsencrypt.org/acme/authz-v3/277007748486)
OR
Could not obtain directory: cURL error 56: TCP connection reset by peer (see [libcurl - Error Codes](https://curl.haxx.se/libcurl/c/libcurl-errors.html)) for [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory)
Manually runnning curl is up and down. When is not working:
curl -Ikv [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory)
- About to connect() to [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) port 443 (#0)
- Trying 172.65.32.248...
- Connected to [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) (172.65.32.248) port 443 (#0)
- Initializing NSS with certpath: sql:/etc/pki/nssdb
- NSS error -5961 (PR\_CONNECT\_RESET\_ERROR)
- TCP connection reset by peer
- Closing connection 0
curl: (35) TCP connection reset by peer
This happens on newer and older NSS packages
Any idea?
---
### Author:  [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)
#### Post date: [October 24, 2023, 4:35pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/2 "2023-10-24T16:35:22Z")
Hello @mmfacc, welcome to the Let's Encrypt community. š
Maybe related to this:
> [@\[SOLVED\] Failed to connect to acme-v02.api.letsencrypt.org port 443 after 3064 ms: Couldn't connect to server](https://community.letsencrypt.org/t/solved-failed-to-connect-to-acme-v02-api-letsencrypt-org-port-443-after-3064-ms-couldnt-connect-to-server/206853):
>
> Iā¦
---
### Author:  [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)
#### Post date: [October 24, 2023, 4:43pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/3 "2023-10-24T16:43:04Z")
> [@Bruce5051](#):
>
> Maybe related to this:
Very unlikely. A faulty local network routing would be failing always.
@mmfacc Do these curl requests work reliably?
```nohighlight
curl -I https://www.cloudflare.com
curl -I https://www.google.com
```
---
### Author:  [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)
#### Post date: [October 24, 2023, 4:44pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/4 "2023-10-24T16:44:06Z")
> [@MikeMcQ](#):
>
> Very unlikely.
Fair enough. š
---
### Author:  [@mmfacc](https://community.letsencrypt.org/u/mmfacc)
#### Post date: [October 24, 2023, 4:48pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/5 "2023-10-24T16:48:40Z")
> [@MikeMcQ](#):
>
> `curl -I https://www.cloudflare.com`
randomly
curl -I [https://www.cloudflare.com](https://www.cloudflare.com)
curl: (35) Network file descriptor is not connected
curl: (35) TCP connection reset by peer
---
### Author:  [@mmfacc](https://community.letsencrypt.org/u/mmfacc)
#### Post date: [October 24, 2023, 4:51pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/6 "2023-10-24T16:51:20Z")
> [@MikeMcQ](#):
>
> `curl -I https://www.google.com`
curl -I [https://www.google.com](https://www.google.com) wors most reliably
---
### Author:  [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)
#### Post date: [October 24, 2023, 4:54pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/7 "2023-10-24T16:54:38Z")
Looks like intermittent connective issues between your system and the Internet.
Where, hard to say at this point.
---
### Author:  [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)
#### Post date: [October 24, 2023, 5:01pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/8 "2023-10-24T17:01:11Z")
> [@mmfacc](#):
>
> [https://www.google.com](https://www.google.com) wors most reliably
But does google still fail some times? Because then yes a general comms issue connecting outbound from your system.
If google was 100% but the other two sometimes failed that's different. Because Let's Encrypt API also uses Cloudflare.
---
### Author:  [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)
#### Post date: [October 24, 2023, 5:05pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/9 "2023-10-24T17:05:34Z")
> [@mmfacc](#):
>
> wors
I took that as a minor type for `worst`, and assumed it meant
"curl -I [https://www.google.com/](https://www.google.com/) **being the least** reliable"
---
### Author:  [@rg305](https://community.letsencrypt.org/u/rg305)
#### Post date: [October 24, 2023, 5:59pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/10 "2023-10-24T17:59:32Z")
> [@Bruce5051](#):
>
> I took that as a minor type for `worst`
I read it as `was`.
I guess my automatic autocorrection worked bess - lol
---
### Author:  [@rg305](https://community.letsencrypt.org/u/rg305)
#### Post date: [October 24, 2023, 5:59pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/11 "2023-10-24T17:59:46Z")
Are you on WiFi?
Please show these outputs:
```plaintext
traceroute -T -p 443 www.google.com
traceroute -T -p 443 acme-v02.api.letsencrypt.org
```
---
### Author:  [@mmfacc](https://community.letsencrypt.org/u/mmfacc)
#### Post date: [October 24, 2023, 6:38pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/12 "2023-10-24T18:38:52Z")
Doing some test it looks like the problem with cloudflare as curl google always works.
At this point it looks to be some kind upstream provider routing issue.
---
### Author:  [@futureweb](https://community.letsencrypt.org/u/futureweb)
#### Post date: [October 24, 2023, 6:48pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/13 "2023-10-24T18:48:41Z")
Also noticing raising Error Counts on our LE Monitoring ... guess there is a Problem on LE side since about 8:10pm ... š¤·š»
---
### Author:  [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)
#### Post date: [October 24, 2023, 7:08pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/14 "2023-10-24T19:08:18Z")
@futureweb You should probably start a new thread with your detailed observations. The problems might overlap but possibly not.
---
### Author:  [@futureweb](https://community.letsencrypt.org/u/futureweb)
#### Post date: [October 24, 2023, 7:21pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/15 "2023-10-24T19:21:36Z")
Ccurrently not on my PC, just had a quick look into the boards on my mobile phone to check If problems are reported as my monitoring reported elevated LE Renewal Errors ...
If they persist when I'm back on my PC I will open own Thread with more Details (on phone too much hassle to aggregate all needed info ... also no actual threat on my side as we Queue all create/renewals on failure)
---
### Author:  [@system](https://community.letsencrypt.org/u/system)
#### Post date: [November 23, 2023, 7:22pm UTC](https://community.letsencrypt.org/t/activation-and-renewal-errors/207219/16 "2023-11-23T19:22:25Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.