Read error 54 connection reset by peer

read error 54 connection reset by peer

the client software has violated the protocol or the permissions (for example it has tried to upload a file to a folder where uploads are. 2 Without fail, the python code fails with an [Errno 54] Connection reset by The "ssh_exchange_identification: read: Connection reset by peer" error. I agree, had this error serveral times on some customer systems. It´s because some network errors (Connection reset). You have to find where the.

watch the video

readsocket: Connection reset by peer (WSAECONNRESET) (10054)

Remarkable: Read error 54 connection reset by peer

Spl-c error asus rt-n13u
Read error 54 connection reset by peer


From the logs, the login window seems to be running on Wayland.
Since the machine is virtual this may be a problem for our standard capturing method.

Our agent reports this exact problem:

WaylandPoller: ERROR! Grabber init failed.
WaylandPoller: ERROR! Grabber creation failed.
WaylandPoller: ERROR! Init failed.

The fix for this would be either disabling the Wayland from both desktop manager (gdm) and desktop itself, or if you wish to keep Wayland please follow our article about this problem:

I am not sure why it has suddenly become a problem after update, but it was either that Wayland was previously disabled and enabled by default on update, or our fix was overwritten by updated files: the egl-capture function provided in the article modifies desktop manager config file, so any update would most likely break it again.

Please let us know if this works, or if you have any other questions.


Request Error "Connection reset by peer" Via Ingress in RTF


Original Description

RTF Application URL is not working even after Inbound traffic has been enabled. We have followed the MuleSoft article - curl -v "http:///api/callstats?Freq=His&FromDate=&ToDate="" -H "Host:" * About to connect() to port (#0) * Trying * Connected to () port (#0) > GET /api/callstats?Freq=His&FromDate=&ToDate= HTTP/ > User-Agent: curl/ > Accept: */* > Host: > * Recv failure: Connection reset by peer * Closing connection 0 curl: (56) Recv failure: Connection reset by peerExplained

Send a test request to the ingress but getting "Connection reset by peer".  Following the How to Troubleshoot Issues of Requests Sending Via Edge in RTF, the curl test can get the expected response from the service endpoint but the error via the ingress (inbound or edge) endpoint. The trace log from the ingress pods shows "SV_TLS_HANDLESHAKE"

TRACE - T HTTP_SvrletAdapterTmpl.H <infoMsg>HTTP_Svrlet(): Created - </infoMsg> DEBUG - T <infoMsg>HTTP_Svrlet(): disconnectInd, state=SV_TLS_HANDLESHAKE cause=DC_PEER_PROT_ERROR duration=1 abandoned reqs=0</infoMsg> TRACE - T HTTP_SvrletAdapterTmpl.H <infoMsg>HTTP_Svrlet(): Deleted - </infoMsg>


The error "SV_TLS_HANDLESHAKE" indicates it's a TLS/SSL handshake error. 
1. Should use HTTPS rather than HTTP in the URL
2. The TLS context in secret manager only configured with TLS


1. Enabled TLS in the TLS context and redeploy Ingress in RTF
2. Use HTTPS in the URL. Please read error 54 connection reset by peer to use quotes to include the URL with query parameters, referring to Query Parameters Are Truncated From Curl Testcurl -v "https:///api/callstats?Freq=His&FromDate=&ToDate="" -H "Host:"

error 54, 'Connection reset by peer' #

I'm getting the dreaded Error 54, Connection reset by peer when trying to do a POST to a URL with a payment provider I'm using. Here is the basic code I'm running:

importrequests, base64url=""headers= { 'Authorization': 'Basic '+baseb64encode('myusername:mypassword')}, read error 54 connection reset by peer, headers=headers)

If I run this exact code on an Ubuntu server it works fine (meaning it returns a json message stating that the username and password are incorrect).

If I run it on OSXI get the connection reset error.

After reading a ton of issues on here and various postings on StackOverflow, everyone seems to think it's securom fix securom 9000 error to SNI. Unfortunately, none of the recommendations that I've come across have fixed the issue.

My Ubuntu server has PythonOpenSSL f and requests

My OSX has PythonOpenSSL g and requests I also have ndg-httpsclient and pyopenssl both installed per #

Any idea what it is that I'm missing?

[Errno 54] Connection reset by peer

Update - apologies - I see you already requested the bulk data so you can probably ignore this post now! I’ll leave it here anyway.

I don’t know what exactly you want to achieve with:

trying to scrape company numbers from director IDs with the API

…but as @ebrian says requesting the list of officers would be a simple way to achieve that - you could then simply parse that for the information you needed. This is doubly the case if you’re not entirely confident in the vagaries of REST APIs / http.

To request that information post on the following thread:

Hi @MArkWilliams, Could I also get access to the bulk director and officer data? Many thanks!

I don’t know for sure if this error is due to you hitting the limit but it would be sensible to write the code to take account of this. Although you could just try (at the simplest) making your wait period / number of requests more conservative I think you’d be better off making use of a library to:
a) cover some of the detail for you (so you can concentrate on your task) and
b) properly implement the rate limit system.

I’m not a Python coder but it looks like you’re using Python there. I believe there are existing Python libraries which will cover that task, for example:

GitHub - JamesGardiner/chwrapper: A python wrapper around the Companies House UK

A python wrapper around the Companies House UK API. - GitHub - JamesGardiner/chwrapper: A python wrapper around the Companies House UK API.

This one certainly appears to handle the rate limiting information from Companies House - if you look at the class here:


This file has been truncated. show original

Again Read error 54 connection reset by peer haven’t used this one personally though and can’t read error 54 connection reset by peer it works now or advise on how to get that to assist with your task.

Still want to do this yourself?

If you do want to implement this it is not especially difficult especially if you only have one thread / single code process making the requests. Companies House provides rate limiting information via http headers on each request giving the “rate window start time period” and “how many requests you have left”. See their documentation. The following posts have details; I would double-check the data your code receives when trying this out as some are older threads:

I would like to implement a multithreaded client which may scale up or down. The simplest way to handle the rate limiting is to rely on the API to tell me when I’ve hit a limit; then each client can exponentially back off until the rate limit is restored. But this depends on how rate limiting is implemented. When I hit my limit, do I get a specific error code? Am I limited for a certain amount of time? Is the requests counter reset every 5 minutes, or averaged over a different period? Than…
Is rate limiting organisation, read error 54 connection reset by peer, account or application based?
Are you referring to the Streaming API or the main/document REST API? Main API Although not listed in the documentation: …I thought this was available via the http headers? I thought the X-Ratelimit fields were what we should use for this purpose - or will things change? Roughly as in the thread: For what it’s worth I just checked and this still seems functional: curl -uMY_API_KEY: -I "" HTTP/ OK Date: Wed, 19 Feb …

Whatever you end up using I notice that Companies House now have some test environments - it would make sense to test whatever you end up using there so you don’t get yourself blocked if the code doesn’t work as expected!

Good luck.

Syncplify Help Center

FATAL ERROR: Connection reset by peer (could not connect to server) Print

Modified on: Sun, 4 Apr, at PM

Applies to: Server! Version(s): 5.x

It may happen that a client that has always been able to runt packet urban terror to Server! without any issues, suddenly can't connect and displays a message similar to this one:

FATAL ERROR: Connection reset by peer (could not connect to server)

When that happens, the most likely causes are:

  1. the client software has violated the protocol or the permissions (for example it has tried to upload a file to a folder where uploads are forbidden) multiple times, and has been blacklisted - in this case, locate your client IP address in the blacklist, and remove it
  2. you may have added at least 1 IP address or network to your white-list, but now you're trying to connect from an IP address that's not white-listed; please keep in mind that the white-list, when used, is restrictive;learn more about the white-list
  3. your server may have detected changes in your hardware, read error 54 connection reset by peer, virtual hardware, or operating system, that may have led to an invalidation of the license - licenses that revert back to FREE edition cause the server to only accept a single client connection at a time - if that happens submit a ticket here (top right corner) and we'll help you reset your license

Did you find it helpful? Yes No

Send feedback

Sorry we couldn't be helpful. Help us improve this article with your feedback.


Leave a Comment