I am running a simple Collection with API requests having Environment variables in endpoints and request body as well. Also, I have some test scripts written for some of the requests. If I select and run some requests from the Collection in the Collection runner, it runs successfully. But when I tr…

Hi @abhinoy , Welcome to the community! :clap: You have quite the interesting issue there. Can you do the following check for me? Run each request in the collection individually, see if you can isolate one request thats having the issue. Can you provide a bigger screenshot of the issue? This mig…

Hi @odanylewycz thanks for the warm welcome :slight_smile: I tried running all the requests individually and was not able to reproduce the error. But more than one request… and the issue reappears. Now, I wasn’t able to pinpoint the reproduction of the issue by the size and/or the number of reques…

You’re welcome :slight_smile: Hm, the issue seems sporadic and quite specific. This issue gets pretty low level and can get complicated so I may not be able to fully help. Basically, my understanding of the issues lies on the networking side. I do now know how much access you have to the endpoint …

This issue is fixed for me by removing junk characters from the GraphQl variables input. I had junk characters in the GraphQl variables input which were not visible but in other notepad editor those were visible to remove those junk characters and ran the request.

I got the same error and I simply disable SSL verification and it works for me [image]

This happened to me due to the SSL certification expired. Using HTTP instead of HTTPS worked too without updating the SSL Cert.

For future folks, this happened to me because of VPN. As soon as I turned off my VPN postman requests started working again. Unclear at this time why my AWS lambdas are blocked by Postman + VPN connection, but this got me back up and running again.

for me it was caused by the header Connection: keep-alive remove it and then it should be working all the time.

this helped , since I was using mongodb atlas and was trying to make an api post request .

Error "read ECONNRESET" displayed while running Postman collection using Collection runner

Help Hub

divyamoorthy09 (Divya M) April 2, 2023, 12:10pm 11

I am also faced this issue “ECONNRESET error”. In mongodb server database access → built-in role → Read/write to any database. It works for me…

1 Like

Topic		Replies	Views
Error: read ECONNRESET while executing through Newman and collection runner Help Hub newman-project , collection-runner	9	17163	August 24, 2023
Error: read ECONNRESET while running postman collection Help Hub tests , variables , collections , cookies	3	35418	May 9, 2025
EConnectReset error Help Hub collections	2	2548	May 9, 2025
Newman gives "read ECONNRESET", but Postman works fine Help Hub newman-project	1	7534	May 16, 2020
ECONNRESET Error With Multiple Runner Sessions Help Hub	1	16198	May 9, 2025

Error "read ECONNRESET" displayed while running Postman collection using Collection runner

Related topics