Curl error 56 proxy connect aborted

Norberto Burciaga

My personal Web Log

Solving “Error in cURL request: Proxy CONNECT aborted”

INTRODUCTION

cURL is a tool that allows you to connect and communicate to many different types of servers with many different types of protocols, specially HTTP.

Some times happens that from where you are, for security reasons, you need to do an HTTP call thru a proxy server, so you need to configure the proxy settings in your cURL options.

PROBLEM

“Error in cURL request: Proxy CONNECT aborted” when calling a URL using a proxy.

DESCRIPTION

To configure the proxy settings into the CURL call the following parameters were used:

CURLOPT_PROXY => $proxyHost,
CURLOPT_PORT => $prxoyPort,

Where $proxyHost and $proxyPort are php variables with values of the valid proxy host address and port number.

But this configuration was sending the Exception: “Error in cURL request: Proxy CONNECT aborted”.

Reading at the curl_setopt manual (1) it says:

CURLOPT_PORT: An alternative port number to connect to

and it was noticed that the following format is being used in some of the examples:

SOLUTION

The CURLOPT_PORT option was not used and instead the port was added to the CURLOPT_PROXY option as concatenation host:port like the following:

CONCLUSION

Some proxies also use authentication, in my case authentication was not required, but if you do, add the following option to cURL:

Источник

Get curl: (56) Proxy CONNECT aborted using https example #1

I’m trying to do a simple forward HTTPS proxy, but I can’t seem to get the https example you’ve provided working. Whenever I try to curl google through the proxy, I get the curl: (56) Proxy CONNECT aborted error. I’ve tried several different proxy definition variations, but no success:

Any suggestions and/or ideas are greatly appreciated. I’m on OS X 10.10.

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

Try passing the flag: —insecure

I think you have to import a custom CA certificate in the client to work with HTTPS.

@h2non Forgot to add that variation I’d tried. Using —insecure doesn’t work.

Are you talking about importing the certificate into the OS X keychain?

Yes, but try first forwarding to another HTTPS server, such as: https://httpbin.org

Earlier today I tried using my own self-signed cert that I’d added to the OS X keychain as I was heading down the same thought path as you, but I still saw the same error. I added it as a system root CA will full trust for all users. When I couldn’t get that to work, I went back to your example to see if it was just my configuration. Same issue. I’m running out of ideas.

I see where could be the issue, the —secure flag in balboa is not working as expected.
There’s required to pass the secure: false option to rocky , but you can’t do that from balboa currently.

Источник

Why does curl not work, but wget works?

For curl, it returns no output at all, but with wget, it returns the entire HTML source:

Here are the 2 commands. I’ve used the same user agent, and both are coming from the same IP, and are following redirects. The URL is exactly the same. For curl, it returns immediately after 1 second, so I know it’s not a timeout issue.

If NY Times might be cloaking, and not returning the source to curl, what could be different in the headers curl is sending? I assumed since the user agent is the same, the request should look exactly the same from both of these requests. What other «footprints» should I check?

2 Answers 2

The way to solve is to analyze your curl request by doing curl -v . and your wget request by doing wget -d . which shows that curl is redirected to a login page

followed by a loop of redirections (which you must have noticed, because you have already set the —max-redirs flag).

On the other hand, wget follows the same sequence except that it returns the cookie set by nytimes.com with its subsequent request(s)

The request sent by curl never includes the cookie.

The easiest way I see to modify your curl command and obtain the desired resource is by adding -c cookiefile to your curl command. This stores the cookie in the otherwise unused temporary «cookie jar» file called «cookiefile» thereby enabling curl to send the needed cookie(s) with its subsequent requests.

For example, I added the flag -c x directly after «curl » and I obtained the output just like from wget (except that wget writes it to a file and curl prints it on STDOUT).

Источник

How to fix cURL 56 recv failure connection reset by peer in CentOS?

by Ansu Anto | Apr 22, 2020

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.

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:

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.

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.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

I got this error because I set app up to require SSL certificate but i did not have https in the url. This blog helped me realize that right away. Thank you!

Hi,
Glad to know that our article helps you solves the issue 🙂 .

Источник

Why curl: (56) Recv failure: Connection reset by peer? #1016

I have build forword proxy on my vps.

It get normal output on my terminal.

An error info occur.

Why [url]https://www.yahoo.com[/url] can get by curl with forword proxy,[url]https://dl-ssl.google.com/linux/linux_signing_key.pub[/url] can’t get by the same forword proxy on the same machine?

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

If you enable debug tracing with —trace-ascii dump.txt , does it shed any more light? «Recv failure» is a really generic error so its hard for us to tell without more info. Can you attach such a debug trace here and we might be able to tell something more?

curl -x «vps_ip:80» —trace-ascii /tmp/dump.txt https://dl-ssl.google.com/linux/linux_signing_key.pub -o /tmp/key.pub
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0curl: (56) Recv failure: Connection reset by peer

cat /tmp/dump.txt
== Info: Hostname was NOT found in DNS cache
== Info: Trying vps_ip.
== Info: Connected to vps_ip (vps_ip) port 80 (#0)
== Info: Establish HTTP proxy tunnel to dl-ssl.google.com:443
=> Send header, 126 bytes (0x7e)
0000: CONNECT dl-ssl.google.com:443 HTTP/1.1
0028: Host: dl-ssl.google.com:443
0045: User-Agent: curl/7.38.0
005e: Proxy-Connection: Keep-Alive
007c:
== Info: Recv failure: Connection reset by peer
== Info: Received HTTP code 0 from proxy after CONNECT
== Info: Closing connection 0

It looks like your proxy simply doesn’t respond properly here.

To close the firewall ,problem solved.

Ok thanks for the update.

close firewall is workless

© 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.

Источник

Hi @fiboknacky , thank you so much for your patience in this case to help me bro.
Actually, at the beginning the proxy config (in adsapi_php.ini) was commented and the original error was:
_Fatal error: Uncaught SoapFault exception: [HTTP] Could not connect to host in C:xampphtdocsGoogleAdwordsgoogleads-php-libsrcGoogleAdsApiCommonAdsSoapClient.php:98
Stack trace:
#0 C:xampphtdocsGoogleAdwordsgoogleads-php-libsrcGoogleAdsApiCommonAdsSoapClient.php(98): SoapClient->__doRequest(‘<?xml version=»…’, ‘https://adwords…’, », 1, 0)
#1 [internal function]: GoogleAdsApiCommonAdsSoapClient->__doRequest(‘<?xml version=»…’, ‘https://adwords…’, », 1, 0)
#2 C:xampphtdocsGoogleAdwordsgoogleads-php-libsrcGoogleAdsApiCommonAdsSoapClient.php(154): SoapClient->__soapCall(‘get’, Array, NULL, Array, Array)
#3 C:xampphtdocsGoogleAdwordsgoogleads-php-libsrcGoogleAdsApiAdWordsv201710cmCampaignService.php(158): GoogleAdsApiCommonAdsSoapClient->_soapCall(‘get’, Array)
#4 C:xampphtdocsGoogleAdwordsgoogleads-php-libexamplesAdWordsv201710BasicOperationsGetCampaigns.php(55): GoogleAdsApiAdWordsv201710cmCampaignService->get(Object(GoogleAdsApiAdWordsv201710cmSelector in C:xampphtdocsGoogleAdwordsgoogleads-php-libsrcGoogleAdsApiCommonAdsSoapClient.php on line 98
then I turned the proxy config on (as I read some solutions from internet) and got the error that we were talking about so far.
As the original error in this comment, do you have any idea how to fix it?

I have been trying to send curl requests with a proxy. When I send such requests with a POST method, it works fine, but it doesn’t work with GET method and I get:

CURLE_RECV_ERROR (56) — Failure when receiving data from the peer.

Any possible reason why that occurs?

The below code returns this error whereas when I execute it with another url using POST METHOD it works fine.

$handle = curl_init($url);
curl_setopt($handle, CURLOPT_POST          , 0);
curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
curl_setopt($handle, CURLOPT_HEADER        , 1);
curl_setopt($handle, CURLOPT_MAXREDIRS     , 5);
curl_setopt($handle, CURLOPT_FOLLOWLOCATION, true);
curl_setopt($handle, CURLOPT_USERAGENT     , 'Mozilla/5.0 (Windows; U; Windows NT   5.1; en-GB; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4');
// curl_setopt($handle, CURLOPT_POSTFIELDS    , "gender=M");
curl_setopt($handle,CURLOPT_PROXY          , $proxyUrl);
curl_setopt($handle,CURLOPT_PROXYUSERPWD   , $urlProxyUserPwd);

echo curl_exec($handle);

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»;

I’m trying to build a web scraper written in PHP and while it works for most of requests, some of them fail with the following error:

cURL (56): Proxy CONNECT aborted

I’ve set my proxy provider (HTTP proxies) accordingly and since they’re mostly disposable proxies, I’d be surprised if it was a problem with the proxies itself. Also the fact that it’s displaying inconsistent behavior— it could go well on first attempt/fail on second and vice-versa, making it really hard to debug.

Unfortunately googling the question leads me to nowhere and the error message is too generic.

The cURL flags I have set are these:

    curl_setopt($ch, CURLOPT_URL, $url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
    curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
    curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
    curl_setopt($ch, CURLOPT_HTTPPROXYTUNNEL, 1); 
    curl_setopt($ch, CURLOPT_PROXY, $proxy->proxy->ip);
    curl_setopt($ch, CURLOPT_PROXYPORT, $proxy->proxy->port);
    curl_setopt($ch, CURLOPT_PROXYUSERNAME, $proxy->proxy->user);
    curl_setopt($ch, CURLOPT_PROXYPASSWORD, $proxy->proxy->pass);
    curl_setopt($ch, CURLOPT_ENCODING, 'gzip, deflate');

Have anyone been through this?