Curl error 56 receiving data failed with unity tls error code 1048578 unity

Curl error but never on the first call #158

I’ll try to explain my problem.

I’m using the 2.6.1 rest client and I’m calling an API from Unity with it.
For a particular endpoint, for the very first time I’m calling it, it will be ok and the next calls too.
I then stop my application and re-run it and then, for an unknow reason, I will meet the following error

‘Curl error 56: Receiving data failed with unitytls error code 1048578’
‘Proyecto26.RequestException: Failed to receive data’

To be more precise about the repro steps.
Let’s say I’ve got 2 website A & B with multiple endoints.

• calling endpoint on A —>OK
• calling another endpoint on A —>OK
• calling auth endpoint on B->OK
  // sequence of calls
• calling some endpoint on B —> OK
• .
• calling some endpoint on B —> KO for some 500 errors.

while I meet an error during the «sequence of calls» I can rerun the app without be blocked at the auth phase.
Once all the calls are OK (and it should be), the next time I will run my app, the auth endpoint on B will be blocked with the curl error. until I restart Unity.

Here is the auth call code.. but maybe the sequence is the problem. the weird thing is that only restarting Unity solves the problem. that supposes this is not due to some app persistence or memory allocation.

What can explain that? I suppose something is wrong in the whole process. I’m not a C# expert.. if you could help me..

The text was updated successfully, but these errors were encountered:

Источник

IMAP «curl: (56) Failure when receiving data from the peer» refs #1778 #3668

I did this

I expected the following

Success to authenticate and run further IMAP commands.

Note 1 : the verbose output doesn’t show the outgoing A002 AUTHENTICATE PLAIN SOMETHING command, but it is sent and shown when I use an incorrect password.

Note 2 : I don’t know why it is talking about Kerberos.

curl/libcurl version

operating system

The text was updated successfully, but these errors were encountered:

I assume you mean this is the same or similar as #1778 was?

Yes I think it’s similar, and I found it while looking for an existing report.

It’s the same error code, and the same message, and the same Kerberos thing. Only de «default cache» value changes from KEYRING:persistent:1000 to FILE:/tmp/krb5cc_1000 (whatever that means ^^)

Might this be happening when kinit is not run and therefore there is no ticket in the cache?

I think the problem is, the code block below is returning TRUE purely because of the existance of GSSAPI capability without checking any user or domain data is actually retrieved from the cache. As a result, it proceeds with the GSSAPI mechanism and when Curl_auth_create_gssapi_user_message is run, Curl_gss_init_sec_context simply fails.

I have more info to share:

1. Using CURLOPT_LOGIN_OPTIONS=»AUTH=PLAIN» will force another auth method and succeed.
2. We have a few IMAP connections that were failing with error «Access denied», upong checking verbose, it was trying NTML and not working, but switching to auth=plain solved the issue too.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Git Clone Fails — error: RPC failed; result=56, HTTP code = 200

Troubleshooting Git

On this page

Related content

Still need help?

The Atlassian Community is here for you.

Symptoms

During a clone or fetch, Git fails with the following error:

Diagnosis

Temporarily disable any firewall or anti-virus software and attempt the clone again.

To turn on Git debug logging, before pushing using the command line, proceed like this for different OS:

On Linux

Execute the following in the command line before executing the Git command:

On Windows

Execute the following in the command line before executing the Git command:

Cause

Issue #1:

Error code 56 indicates a curl receive error of CURLE_RECV_ERROR which means there was some issue that prevented the data from being received during the clone process. Typically this is caused by a network setting, firewall, VPN client, or anti-virus that is terminating the connection before all data has been transferred.

Issue #2:

The bug below could be causing that situation:

BSERV-7633 — Getting issue details. STATUS : under a stress test, with multiple concurrent Git clones, some fail with the following error:

Workaround

Switch to using SSH to perform the clone.

Resolution

Change the anti-virus settings, firewall settings, or VPN client so that they allow connections from Stash and do not terminate them prematurely.

Issue #2:

Please upgrade your instance to a release that contains the fix.

Источник

curl: (56) GnuTLS recv error (-54): Error in the pull function. #1707

I did this

I expected the following

no error, wiki.en.zip file saved.

curl/libcurl version

operating system

notes

wget works. date is correct.

The text was updated successfully, but these errors were encountered:

Is this reproducible with just curl? It could be a temporary network problem.

It looks like a temporary network problem. Using that same packaged version in Ubuntu 16 I downloaded 20% in about an hour and the speed was all over the place. It is far too slow for me to complete the whole thing.

Try adding -v to the command and see if that tells something more. If the transfer ends before the 9877MB are transferred (it showed me Content-Length: 10356881301 ), it really should output an error.

Like @jay, I cannot reproduce a problem with this URL, although I built the current git master and ran the command line tool using GnuTLS/3.5.14. I got the whole file downloaded (in my first and only attempt to get the whole thing) in 11m03, at about a 14.8 megabytes/second transfer rate on average.

I tried from another machine with curl 7.47.0 (i586-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.5.5 and it also managed to download the first part of the file just fine. I didn’t bother to wait for the whole file there.

@bagder Thank you for the tests and details. Here is what happens:

Part of the file has been saved

But not completely, since the whole file is 10356881301B ,

That seems to be an error detected by and returned from a GnuTLS function. I’ve googled around for it a bit but it didn’t give me any clear answers. I think it hints to a problem with that GnuTLS version, possibly in combination with something in your network/environment that makes it trigger for you. It’s hard to know better without a way to reproduce it.

@bagder agreed, there is no evidence that is nothing than a network/env problem, so closing this.

Источник

cURL Errors and Reasons (The Complete List)

Advertisement

Parent Page

Below is the list of all cURL errors and the reasons behind these errors.

# Ok Ok

CURL error code 0 – CURLE_OK (0)

All fine. Proceed as usual.

# Unsupported Protocol Unsupported Protocol

CURL error code 1 – CURLE_UNSUPPORTED_PROTOCOL (1)

The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn’t use, it can be a misspelled protocol string or just a protocol libcurl has no code for.

# Failed Init Failed Init

CURL error code 2 – CURLE_FAILED_INIT (2)

Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn’t get done at init time.

# URL Malfomat URL Malfomat

CURL error code 3 – CURLE_URL_MALFORMAT (3)

The URL was not properly formatted.

# Not Built In Not Built In

CURL error code 4 – CURLE_NOT_BUILT_IN (4)

A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl.

# Couldn’t Resolve Proxy Couldn’t Resolve Proxy

CURL error code 5 – CURLE_COULDNT_RESOLVE_PROXY (5)

Couldn’t resolve proxy. The given proxy host could not be resolved.

# Couldn’t resolve host Couldn’t resolve host

CURL error code 6 – CURLE_COULDNT_RESOLVE_HOST (6)

Couldn’t resolve host. The given remote host was not resolved.

# Couldn’t connect Couldn’t connect

CURL error code 7 – CURLE_COULDNT_CONNECT (7)

Failed to connect() to host or proxy.

# Weird server reply Weird server reply

CURL error code 8 – CURLE_WEIRD_SERVER_REPLY (8)

The server sent data libcurl couldn’t parse. This error code was known as as CURLE_FTP_WEIRD_SERVER_REPLY before 7.51.0.

# Remote access denied Remote access denied

CURL error code 9 – CURLE_REMOTE_ACCESS_DENIED (9)

We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.

# FTP accept failed FTP accept failed

CURL error code 10 – CURLE_FTP_ACCEPT_FAILED (10)

While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.

# FTP weird pass reply FTP weird pass reply

CURL error code 11 – CURLE_FTP_WEIRD_PASS_REPLY (11)

After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned.

# FTP accept timeout FTP accept timeout

CURL error code 12 – CURLE_FTP_ACCEPT_TIMEOUT (12)

During an active FTP session while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.

# FTP weird pasv reply FTP weird pasv reply

CURL error code 13 – CURLE_FTP_WEIRD_PASV_REPLY (13)

libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed.

# FTP weird 227 format FTP weird 227 format

CURL error code 14 – CURLE_FTP_WEIRD_227_FORMAT (14)

FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code is passed back.

# FTP cant get host FTP cant get host

CURL error code 15 – CURLE_FTP_CANT_GET_HOST (15)

An internal failure to lookup the host used for the new connection.

# HTTP2 HTTP2

CURL error code 16 – CURLE_HTTP2 (16)

A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

# FTP couldnt set type FTP couldnt set type

CURL error code 17 – CURLE_FTP_COULDNT_SET_TYPE (17)

Received an error when trying to set the transfer mode to binary or ASCII.

# Partial file Partial file

CURL error code 18 – CURLE_PARTIAL_FILE (18)

A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn’t match the previously given size.

# FTP couldnt retr file FTP couldnt retr file

CURL error code 19 – CURLE_FTP_COULDNT_RETR_FILE (19)

This was either a weird reply to a ‘RETR’ command or a zero byte transfer complete.

# Quote error Quote error

CURL error code 21 – CURLE_QUOTE_ERROR (21)

When sending custom “QUOTE” commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.

# HTTP returned error HTTP returned error

CURL error code 22 – CURLE_HTTP_RETURNED_ERROR (22)

This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400.

# Write error Write error

CURL error code 23 – CURLE_WRITE_ERROR (23)

An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.

# Upload failed Upload failed

CURL error code 25 – CURLE_UPLOAD_FAILED (25)

Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server’s explanation for this.

# Read error Read error

CURL error code 26 – CURLE_READ_ERROR (26)

There was a problem reading a local file or an error returned by the read callback.

# Out of memory Out of memory

CURL error code 27 – CURLE_OUT_OF_MEMORY (27)

A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs.

# Operation timedout Operation timedout

CURL error code 28 – CURLE_OPERATION_TIMEDOUT (28)

Operation timeout. The specified time-out period was reached according to the conditions.

# FTP port failed FTP port failed

CURL error code 30 – CURLE_FTP_PORT_FAILED (30)

The FTP PORT command returned error. This mostly happens when you haven’t specified a good enough address for libcurl to use. See CURLOPT_FTPPORT.

# FTP couldnt use rest FTP couldnt use rest

CURL error code 31 – CURLE_FTP_COULDNT_USE_REST (31)

The FTP REST command returned error. This should never happen if the server is sane.

# Range error Range error

CURL error code 33 – CURLE_RANGE_ERROR (33)

The server does not support or accept range requests.

# HTTP post error HTTP post error

CURL error code 34 – CURLE_HTTP_POST_ERROR (34)

This is an odd error that mainly occurs due to internal confusion.

# SSL connect error SSL connect error

CURL error code 35 – CURLE_SSL_CONNECT_ERROR (35)

A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.

# Bad download resume Bad download resume

CURL error code 36 – CURLE_BAD_DOWNLOAD_RESUME (36)

The download could not be resumed because the specified offset was out of the file boundary.

# File couldnt read file File couldnt read file

CURL error code 37 – CURLE_FILE_COULDNT_READ_FILE (37)

A file given with FILE:// couldn’t be opened. Most likely because the file path doesn’t identify an existing file. Did you check file permissions?

# LDAP cannot bind LDAP cannot bind

CURL error code 38 – CURLE_LDAP_CANNOT_BIND (38)

LDAP cannot bind. LDAP bind operation failed.

# LDAP search failed LDAP search failed

CURL error code 39 – CURLE_LDAP_SEARCH_FAILED (39)

LDAP search failed.

# Function not found Function not found

CURL error code 41 – CURLE_FUNCTION_NOT_FOUND (41)

Function not found. A required zlib function was not found.

# Aborted by callback Aborted by callback

CURL error code 42 – CURLE_ABORTED_BY_CALLBACK (42)

Aborted by callback. A callback returned “abort” to libcurl.

# Bad function argument Bad function argument

CURL error code 43 – CURLE_BAD_FUNCTION_ARGUMENT (43)

A function was called with a bad parameter.

# Interface failed Interface failed

CURL error code 45 – CURLE_INTERFACE_FAILED (45)

Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections’ source IP address with CURLOPT_INTERFACE.

# Too many redirects Too many redirects

CURL error code 47 – CURLE_TOO_MANY_REDIRECTS (47)

Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.

# Unknown option Unknown option

CURL error code 48 – CURLE_UNKNOWN_OPTION (48)

An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the program that uses libcurl. The error buffer might contain more specific information about which exact option it concerns.

# Telnet option syntax Telnet option syntax

CURL error code 49 – CURLE_TELNET_OPTION_SYNTAX (49)

A telnet option string was Illegally formatted.

# Got nothing Got nothing

CURL error code 52 – CURLE_GOT_NOTHING (52)

Nothing was returned from the server, and under the circumstances, getting nothing is considered an error.

# SSL engine notfound SSL engine notfound

CURL error code 53 – CURLE_SSL_ENGINE_NOTFOUND (53)

The specified crypto engine wasn’t found.

# SSL engine setfailed SSL engine setfailed

CURL error code 54 – CURLE_SSL_ENGINE_SETFAILED (54)

Failed setting the selected SSL crypto engine as default!

# Send error Send error

CURL error code 55 – CURLE_SEND_ERROR (55)

Failed sending network data.

# Recv error Recv error

CURL error code 56 – CURLE_RECV_ERROR (56)

Failure with receiving network data.

# SSL certproblem SSL certproblem

CURL error code 58 – CURLE_SSL_CERTPROBLEM (58)

problem with the local client certificate.

# SSL cipher SSL cipher

CURL error code 59 – CURLE_SSL_CIPHER (59)

Couldn’t use specified cipher.

# PEER failed verification PEER failed verification

CURL error code 60 – CURLE_PEER_FAILED_VERIFICATION (60)

The remote server’s SSL certificate or SSH md5 fingerprint was deemed not OK. This error code has been unified with ## CURL error code – CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

# Bad content encoding Bad content encoding

CURL error code 61 – CURLE_BAD_CONTENT_ENCODING (61)

Unrecognized transfer encoding.

# LDAP invalid url LDAP invalid url

CURL error code 62 – CURLE_LDAP_INVALID_URL (62)

Invalid LDAP URL.

# Filesize exceeded Filesize exceeded

CURL error code 63 – CURLE_FILESIZE_EXCEEDED (63)

Maximum file size exceeded.

# Use ssl failed Use ssl failed

CURL error code 64 – CURLE_USE_SSL_FAILED (64)

Requested FTP SSL level failed.

# Send fail rewind Send fail rewind

CURL error code 65 – CURLE_SEND_FAIL_REWIND (65)

When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed.

# SSL engine initfailed SSL engine initfailed

CURL error code 66 – CURLE_SSL_ENGINE_INITFAILED (66)

Initiating the SSL Engine failed.

# Login denied Login denied

CURL error code 67 – CURLE_LOGIN_DENIED (67)

The remote server denied curl to login (Added in 7.13.1)

# TFTP notfound TFTP notfound

CURL error code 68 – CURLE_TFTP_NOTFOUND (68)

File not found on TFTP server.

# TFTP perm TFTP perm

CURL error code 69 – CURLE_TFTP_PERM (69)

Permission problem on TFTP server.

# Remote disk full Remote disk full

CURL error code 70 – CURLE_REMOTE_DISK_FULL (70)

Out of disk space on the server.

# TFTP illegal TFTP illegal

CURL error code 71 – CURLE_TFTP_ILLEGAL (71)

Illegal TFTP operation.

# TFTP unknownid TFTP unknownid

CURL error code 72 – CURLE_TFTP_UNKNOWNID (72)

Unknown TFTP transfer ID.

# Remote file exists Remote file exists

CURL error code 73 – CURLE_REMOTE_FILE_EXISTS (73)

File already exists and will not be overwritten.

# TFTP nosuchuser TFTP nosuchuser

CURL error code 74 – CURLE_TFTP_NOSUCHUSER (74)

This error should never be returned by a properly functioning TFTP server.

# Conv failed Conv failed

CURL error code 75 – CURLE_CONV_FAILED (75)

Character conversion failed.

# Conv reqd Conv reqd

CURL error code 76 – CURLE_CONV_REQD (76)

Caller must register conversion callbacks.

# SSL cacert badfile SSL cacert badfile

CURL error code 77 – CURLE_SSL_CACERT_BADFILE (77)

Problem with reading the SSL CA cert (path? access rights?)

# Remote file not found Remote file not found

CURL error code 78 – CURLE_REMOTE_FILE_NOT_FOUND (78)

The resource referenced in the URL does not exist.

# SSH SSH

CURL error code 79 – CURLE_SSH (79)

An unspecified error occurred during the SSH session.

# SSL shutdown failed SSL shutdown failed

CURL error code 80 – CURLE_SSL_SHUTDOWN_FAILED (80)

Failed to shut down the SSL connection.

# Again Again

CURL error code 81 – CURLE_AGAIN (81)

Socket is not ready for send/recv wait till it’s ready and try again. This return code is only returned from curl_easy_recv and curl_easy_send (Added in 7.18.2)

# SSL crl badfile SSL crl badfile

CURL error code 82 – CURLE_SSL_CRL_BADFILE (82)

Failed to load CRL file (Added in 7.19.0)

# SSL issuer error SSL issuer error

CURL error code 83 – CURLE_SSL_ISSUER_ERROR (83)

Issuer check failed (Added in 7.19.0)

# FTP pret failed FTP pret failed

CURL error code 84 – CURLE_FTP_PRET_FAILED (84)

The FTP server does not understand the PRET command at all or does not support the given argument. Be careful when using CURLOPT_CUSTOMREQUEST, a custom LIST command will be sent with PRET CMD before PASV as well. (Added in 7.20.0)

# RTSP cseq error RTSP cseq error

CURL error code 85 – CURLE_RTSP_CSEQ_ERROR (85)

Mismatch of RTSP CSeq numbers.

# RTSP session error RTSP session error

CURL error code 86 – CURLE_RTSP_SESSION_ERROR (86)

Mismatch of RTSP Session Identifiers.

# FTP bad file list FTP bad file list

CURL error code 87 – CURLE_FTP_BAD_FILE_LIST (87)

Unable to parse FTP file list (during FTP wildcard downloading).

# Chunk failed Chunk failed

CURL error code 88 – CURLE_CHUNK_FAILED (88)

Chunk callback reported error.

# No connection available No connection available

CURL error code 89 – CURLE_NO_CONNECTION_AVAILABLE (89)

(For internal use only, will never be returned by libcurl) No connection available, the session will be queued. (added in 7.30.0)

# SSL pinnedpubkeynotmatch SSL pinnedpubkeynotmatch

CURL error code 90 – CURLE_SSL_PINNEDPUBKEYNOTMATCH (90)

Failed to match the pinned key specified with CURLOPT_PINNEDPUBLICKEY.

# SSL invalidcertstatus SSL invalidcertstatus

CURL error code 91 – CURLE_SSL_INVALIDCERTSTATUS (91)

Status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS.

# HTTP2 stream HTTP2 stream

CURL error code 92 – CURLE_HTTP2_STREAM (92)

Stream error in the HTTP/2 framing layer.

# Recursive api call Recursive api call

CURL error code 93 – CURLE_RECURSIVE_API_CALL (93)

An API function was called from inside a callback.

# Auth error Auth error

CURL error code 94 – CURLE_AUTH_ERROR (94)

An authentication function returned an error.

# HTTP3 HTTP3

CURL error code 95 – CURLE_HTTP3 (95)

A problem was detected in the HTTP/3 layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

# Quic connect error Quic connect error

CURL error code 96 – CURLE_QUIC_CONNECT_ERROR (96)

QUIC connection error. This error may be caused by an SSL library error. QUIC is the protocol used for HTTP/3 transfers.

# Obsolete* Obsolete*

CURL error code * – CURLE_OBSOLETE*

These error codes will never be returned. They were used in an old libcurl version and are currently unused.

Like this:

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Источник

I’ve got a connection issue that I’m stumped on. While playing on a dedicated server, I get zombies/players running in place, cannot interact with anything etc however I do not lose internet and maintain voip in Steam Chat. To the nitty gritty: Windows 10 Pro, dedicated server from Bluefang, no other players affected. Windows Defender is my antivirus and Steam folder is excluded. Game is 19.6 and no mods on the server nor do I have mods installed and never have had mods on this computer. Spectrum is my isp and I’m hardwired to the router. Here is my log:   https://pastebin.com/embed_js/w4nBeyX3

Second time in an hour it happened again and this is the log: https://pastebin.com/embed_js/WBGxEvWZ

I have done tracert a few times but not at the time of the crash and I never observed any packet loss. The server is in New York City, I am in Ohio. My ping is always a steady 45-50 and doesn’t seem to change when this happens (although it’s frozen at the time). 

Any thoughts? Any more info that you want?

Thanks in advance.

I did this

$ imap -v imaps://some_server --user some_user
[...]
< * OK IMAP4rev1 proxy server ready
> A001 CAPABILITY
< * CAPABILITY ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ID IDLE IMAP4rev1 LIST-EXTENDED LITERAL+ MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES UIDPLUS UNSELECT WITHIN ESORT I18NLEVEL=1 SORT THREAD=ORDEREDSUBJECT LIST-STATUS XLIST AUTH=PLAIN AUTH=GSSAPI
< A001 OK completed
* gss_init_sec_context() failed: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000).
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
curl: (56) Failure when receiving data from the peer

I expected the following

Success to authenticate and run further IMAP commands.

Note 1 : the verbose output doesn’t show the outgoing A002 AUTHENTICATE PLAIN SOMETHING command, but it is sent and shown when I use an incorrect password.

Note 2 : I don’t know why it is talking about Kerberos.

curl/libcurl version

curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

operating system

Linux

Having trouble with cURL 56 recv failure connection reset by peer in the CentOS server?

The error occurs mainly due to failure in receiving network data.

At Bobcares, we often get requests to fix cURL errors as part of our Server Management Services.

Today, let’s get into the details on how our Support Engineers fix this error.

Why does cURL 56 recv failure connection reset by peer occurs?

cURL error 56 is a temporary error that happens due to different reasons like, idle server connection, firewall restrictions, whitespace in the URL, etc.

For instance, the error appears as follows.

Let’s detail how our Support Engineers fix this for our customers.

How we fix this error cURL error?

At Bobcares, we have more than a decade of expertise in managing servers, we see many customers facing errors. It happens mainly when fetching package updates, installing new software, etc.

Now, let’s see the major reasons and how our Support Engineers fix this error.

Idle server connection

Recently, one of the customers approached us with a cURL error. He was getting the following error while transferring the backup to the remote destination.

cURL error 56: TCP connection reset by peer

So we checked the backup log files and confirmed that the backups have been generated successfully.

On further checking, we found that the server was idle while transferring the backups to the remote destination. However, the backups were successfully exported to Google drive.

In addition, to avoid this situation, the tips we follow are:

• We always upgrade the user’s OS to avoid TCP/IP issues.
• Also, we use the recent versions of PHP and cURL.
• Set the Maximum Transmission Unit (MTU) or the size of packets traveling over the network to the default value, 1500 bytes.
• We ensure that the firewall is not blocking the user’s connection.

Bad repository

Often bad repository URL can also trigger curl 56 errors.

For instance, while trying to install PHP on CentOS7 server one of our customers received the error:

Loaded plugins: fastestmirror, langpacks
http://mirror.xxx.net/el7-x86_64/rpms/ ... repomd.xml: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.

Here, the customer was using an outdated repository and that caused the error. Therefore, we corrected the repo settings on the server and the package install went on fine.

Similarly, the repository may fail to load due to DNS resolution failures as well. In such scenarios, we make use of the /etc/hosts files to map the repo website to the correct IP address.

Whitespace in the URL

Another customer approached us with a similar problem.

On further investigation, we found whitespace in the URL. We then removed whitespace from the URL.

And in the PHP settings, we added the following.

curl_setopt($ch, CURLOPT_URL, trim($url));

In addition, If whitespace is a valid part of the URL, we use rawurlencode() function in PHP, to store the URL as encoded including whitespace.

[Need assistance in fixing cURL errors? – We can help you.]

Conclusion

In short, cURL 56 recv failure connection reset by peer in CentOS occurs when the server is idle due to running a long process or due to improper usage of URL. Today, we saw how our Support Engineers fixed the error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

0