# Connection reset by peer - error

**URL:** <https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811>\
**Category:** Help\
**Created:** [June 6, 2018, 7:21pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811 "2018-06-06T19:21:45Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![richard.esmond](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@richard.esmond](https://community.letsencrypt.org/u/richard.esmond)\
**Post date:** [June 6, 2018, 7:21pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/1 "2018-06-06T19:21:45Z")

</div>

My domain is:

[testing.penforms.penrad.com](http://testing.penforms.penrad.com)

I ran this command:

Complete-ACMEChallenge dns1 -ChallengeType http-01 -Handler manual -force

It produced this output:

IdentifierPart : ACMESharp.Messages.IdentifierPart  
IdentifierType : dns  
Identifier : [testing.penforms.penrad.com](http://testing.penforms.penrad.com)  
Uri : [https://acme-v01.api.letsencrypt.org/acme/authz/ephjQMRV49XJoa64ifMHNoqeM7w\_0WNuBWOL1B8MGJ0](https://acme-v01.api.letsencrypt.org/acme/authz/ephjQMRV49XJoa64ifMHNoqeM7w_0WNuBWOL1B8MGJ0)  
Status : pending  
Expires : 6/13/2018 12:37:10 PM  
Challenges : {manual, }  
Combinations : {1, 0}

My web server is (include version):

Kestrel

The operating system my web server runs on is (include version):

Windows 10

I can login to a root shell on my machine: YES

* * *

I’m getting a Connection reset by peer error message.

{  
“type”: “http-01”,  
“status”: “invalid”,  
“error”: {  
“type”: “urn:acme:error:connection”,  
“detail”: “Fetching [http://testing.penforms.penrad.com/.well-known/acme-challenge/\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc:](http://testing.penforms.penrad.com/.well-known/acme-challenge/_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc:) Connection reset by peer”,  
“status”: 400  
},  
“uri”: “[https://acme-v01.api.letsencrypt.org/acme/challenge/ephjQMRV49XJoa64ifMHNoqeM7w\_0WNuBWOL1B8MGJ0/4984545111](https://acme-v01.api.letsencrypt.org/acme/challenge/ephjQMRV49XJoa64ifMHNoqeM7w_0WNuBWOL1B8MGJ0/4984545111)”,  
“token”: “\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc”,  
“keyAuthorization”: “\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc.hKfdQS7I\_cOOY8GmIc4MQ9RpEwdJIOTm\_oYkCyJZ-Wk”,  
“validationRecord”: [  
{  
“url”: “[http://testing.penforms.penrad.com/.well-known/acme-challenge/\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc](http://testing.penforms.penrad.com/.well-known/acme-challenge/_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc)”,  
“hostname”: “[testing.penforms.penrad.com](http://testing.penforms.penrad.com)”,  
“port”: “80”,  
“addressesResolved”: [  
“216.105.239.55”  
],  
“addressUsed”: “216.105.239.55”  
}  
]  
}

But when I hit this address locally it works fine, even when I have the Chrome debugger up watching the get.

[http://testing.penforms.penrad.com/.well-known/acme-challenge/\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc](http://testing.penforms.penrad.com/.well-known/acme-challenge/_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc)

Here is what I am returning:

\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc.hKfdQS7I\_cOOY8GmIc4MQ9RpEwdJIOTm\_oYkCyJZ-Wk

Am I missing something?

Thanks.

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [June 6, 2018, 8:47pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/2 "2018-06-06T20:47:05Z")

</div>

Hi @richard.esmond,

This looks like you might have a firewall that blocks connections from certain IP address ranges.

If not, you could look in your web server logs to see if it was your web server that deliberately dropped the connection from Let’s Encrypt.

---

<div class="post-metadata">

**Author:** ![richard.esmond](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@richard.esmond](https://community.letsencrypt.org/u/richard.esmond)\
**Post date:** [June 6, 2018, 9:08pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/3 "2018-06-06T21:08:08Z")

</div>

I am actually watching the log and the HTTP calls look like they are working fine.

Can you try this link and see if you get through?

[http://testing.penforms.penrad.com/.well-known/acme-challenge/\_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc](http://testing.penforms.penrad.com/.well-known/acme-challenge/_QVpP1Q4BnRc-fd2WRG0Laubk8dMRA7KgMD9zm3icSc)

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [June 6, 2018, 9:09pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/4 "2018-06-06T21:09:04Z")

</div>

I definitely can, but if the certificate authority’s validation servers can’t, it seems like something must be blocking them.

---

<div class="post-metadata">

**Author:** ![richard.esmond](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@richard.esmond](https://community.letsencrypt.org/u/richard.esmond)\
**Post date:** [June 6, 2018, 9:10pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/5 "2018-06-06T21:10:11Z")

</div>

Actually I see the transactions coming through. I have been assuming that there is something about how I am handlling the transaction is somehow off.

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [June 6, 2018, 9:26pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/6 "2018-06-06T21:26:15Z")

</div>

Are you sure that you aren’t just seeing your and my tests? If you start over with a new certificate request (that you don’t test for yourself and don’t post here), what will you see in the web server logs?

---

<div class="post-metadata">

**Author:** ![richard.esmond](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@richard.esmond](https://community.letsencrypt.org/u/richard.esmond)\
**Post date:** [June 6, 2018, 9:29pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/7 "2018-06-06T21:29:37Z")

</div>

I watched a dozen calls to my server even before I posted this message.

I am considering creating a new request.

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [June 6, 2018, 9:34pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/8 "2018-06-06T21:34:41Z")

</div>

> [@richard.esmond](#):
>
> I watched a dozen calls to my server even before I posted this message.

Well, I tested it about 5-6 times and I think other random people reading this forum may have tested it about 3 times, so if you tested it about 3 times yourself, that might be enough account for the dozen hits without a successful visit from the Let's Encrypt CA itself...

---

<div class="post-metadata">

**Author:** ![richard.esmond](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@richard.esmond](https://community.letsencrypt.org/u/richard.esmond)\
**Post date:** [June 6, 2018, 9:54pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/9 "2018-06-06T21:54:29Z")

</div>

They seem to mostly be coming from 17.133.7.117

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [June 6, 2018, 10:00pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/10 "2018-06-06T22:00:19Z")

</div>

That IP address is owned by Apple, probably not Let’s Encrypt.

Let’s Encrypt can reach your server, at least sometimes: [https://acme-staging-v02.api.letsencrypt.org/acme/authz/-it8z6A-yH2DoUEE-pzCIKSIIzIS1EwITamDVq4UaAg](https://acme-staging-v02.api.letsencrypt.org/acme/authz/-it8z6A-yH2DoUEE-pzCIKSIIzIS1EwITamDVq4UaAg)

---

<div class="post-metadata">

**Author:** ![richard.esmond](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@richard.esmond](https://community.letsencrypt.org/u/richard.esmond)\
**Post date:** [June 6, 2018, 10:02pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/11 "2018-06-06T22:02:17Z")

</div>

LOL - I’m getting trolled by apple!

I’ll redo the request and see if that fixes it.

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [July 6, 2018, 10:02pm UTC](https://community.letsencrypt.org/t/connection-reset-by-peer-error/63811/12 "2018-07-06T22:02:18Z")

</div>

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