Php curl error 35 ssl connect error

cURL error 35: SSL connect error

The cURL error 35 can appear in the Really Simple SSL debug log when the CURL function cannot connect to your website using SSL. Curl often uses a different set of certificates, shipped with PHP. There are several things that can cause this problem, in most cases updating both cURL and PHP to a newer version will resolve this issue. If this doesn’t resolve the problem, please contact your webhosting company, as they can check why CURL is having issues.

Lightweight plugin, Heavyweight Security features. Get Pro and leverage your SSL certificate for WordPress security standards.

Join our mailing list — 6 Tips & Tricks in your inbox over the next days!

Plugins

© Really Simple Plugins
CoC 70461155
Kalmarweg 14-5
9723 JG, Groningen (NL)

Get Started

About

Popular articles

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.

The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.

The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.

The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.

The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Withdrawing consent, may adversely affect certain features and functions.

The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.

The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.

The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.

The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.

Источник

PHP cURL SSL connect error 35 – Top Causes and fixes

Usually, PHP cURL SSL connect error 35 occur due to version mismatch or outdated cURL package.

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

Today, let’s see how our Support Engineers fix PHP cURL SSL connect error 35 for our customers.

What is PHP curl SSL connect error 35?

Before getting deeper into the error, firstly let’s understand what is PHP cURL.

cURL stands for Client for URL. Usually, PHP uses cURL to connect to the specified website URL. Here we are discussing cURL request to an SSL website.

In many situations, when a server tries to connect to an SSL website, the cURL request ends up in an error message.

cURL error (35): SSL connect error.

The error message denotes that there is an error somewhere in SSL/TLS handshake. In short, the cURL error code 35 denotes an SSL connection error.

The error can be due to an outdated cURL package, connection errors or else a version mismatch between the PHP cURL and SSL protocol of the end server.

A sample error at a Drupal website will show up as:

How we fix the PHP cURL SSL connect error?

So far, we have seen what is PHP cURL SSL connect error. Our Dedicated Engineers with expertise over a decade usually fix this error for our customers.

As the first step of troubleshooting, we check the webserver log.

It gives a detailed summary of all the SSL/TLS handshakes. From this data, our experts find the exact reason for the timeout.

1. SSL protocol of destination site

In most cases, errors will be with the PHP cURL versions in the server.

For instance, the command-line cURL may be using the latest version and the SSL protocol may be outdated.

Meanwhile, if the server tries to connect to an endpoint with an older SSL protocol, it fails and ends up in cURL error 35. This is particularly applicable with outdated SSL protorcols like SSLv2, SSLv3.

So, we check the versions of the cURL and SSL protocol. Later, if there is any version mismatch, our Support Engineers update it to the latest.

2. Outdated cURL package

Similarly, an outdated cURL package in the servers shows up the SSL connect error. In this case, our Support Engineers check the cURL version in the server.

This command gives the currently used cURL version in the server.

Later, we update the cURL package to the latest version. After that, we update the Network Security Services (NSS) package on the server using:

This fixes the package and the error does not show up again.

3. Customizing cURL configuration

Some customers customize the cURL settings on the server. However, improper setting of the PHP cURL configuration file leads to error 35.

In such cases, our Support Team check the configuration file and correct it.

Here, we first confirm the availability of cURL module support for PHP with the command:

For example, the correct settings appear as:

/etc/php.d/curl.ini, curl cURL support => enabled cURL Information => 7.66.0

We also ensure that the website uses the correct PHP version with cURL support.

4. Firewall restrictions

In many cases, the cURL SSL error can happen due to firewall restrictions on the server too. For example, when network administrators ban SSL connections, none of the data transactions to or from the server happens.

Thus, we always check the firewall on the server and ensure that the server accepts SSL port connections from selected APIs and networks.

[Still having trouble in fixing PHP cURL SSL connect error? – We’ll fix it for you.]

Conclusion

In short, PHP cURL SSL connect error 35 usually occur due to version mismatch of cURL and SSL, outdated cURL package, firewall restrictions and so on. Today, we also saw how our Support Engineers fix this error for our customers.

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.

Источник

How to fix error 35 PHP cURL SSL connect?

cURL connects with the website using SSL – This is a usual process between the server and you! Sometimes, it will show an error by saying cURL isn’t connecting with your website. And, you need to search for the solution right now! We’ll give you some guess maybe the package of cURL is outdated or mismatch version of PHP.

What exactly is cURL? It is nothing but “Client for URL”! Yes, PHP takes the responsibility to connect cURL with your website using SSL. Whenever the server takes the first step to getting connected with the SSL website it retrieves a message of error saying

cURL error (35): SSL connect error.

Maybe the handshake of TLS or SSL is the reason behind this error.

Let’s confirm this error in detail:

The error you got with the number is 35 and it says SSL is not ready for connection. Check the package of cURL and the version in-between protocol of SSL and cURL PHP.

Solution: Update the latest package of SSL protocol and cURL for better results.

This command will give the result of the current version you using up. After the check, you can move on with the new version of cURL. Once if you update the new version of cURL then start update on NSS (Network Security Services) using the below-mentioned command:

By now, you won’t be visible with error 35.

Use the below-mentioned command for checking the settings of cURL:

If the setting is correct please confirm it by below results:

/etc/php.d/curl.ini, curl cURL support => enabled cURL Information => 7.66.0

Here, the version is correct so, no more error 35.

Solution: Do check on the server activity whether it accepts the connection of SSL only from the chosen network and APIs.

We have given you more steps and analysis for cURL can’t connect with SSL connections. I Hope, you might get an idea for improper connections between cURL and SSL protocol. Look out our solutions deep to figure out current scenarios. We have depicted the nature of cURL customization and SSL protocol activity. Guess it gives a way for the fix!

Author kumkumsharma Views 20,607 First release May 17, 2021 Last update May 17, 2021 Rating 0.00 star(s) 0 ratings

Источник

Saved searches

Use saved searches to filter your results more quickly

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. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cURL error 35: Unknown SSL protocol error #1349

cURL error 35: Unknown SSL protocol error #1349

Comments

I have problems connecting with Guzzle through a proxy to any SSL site. If I try it with standard cURL in PHP it works fine, however, with Guzzle the connection fails and returns:

[GuzzleHttp\Exception\ConnectException] cURL error 35: Unknown SSL protocol error in connection to api.ipify.org:443 

The cURL code that works well:

 $options = array( CURLOPT_RETURNTRANSFER => true, CURLOPT_PROXY => '1.2.3.4:1234', CURLOPT_PROXYUSERPWD => "proxy:auth", ); $ch = curl_init( 'https://api.ipify.org?format=json' ); curl_setopt_array( $ch, $options ); $content = curl_exec( $ch ); $err = curl_errno( $ch ); $errmsg = curl_error( $ch ); $header = curl_getinfo( $ch ); curl_close( $ch ); $header['errno'] = $err; $header['errmsg'] = $errmsg; $header['content'] = $content; print_r($header); 

The Guzzle code that fails:

 // http client $this->client = $client = new Client([ 'cookies' => true ]); $res = $this->client->request('GET', 'https://api.ipify.org?format=json', [ 'proxy' => 'https://proxy:auth@1.2.3.4:1234', 'verify' => false, 'curl' => [ //CURLOPT_SSLVERSION => 3 //CURLOPT_SSLVERSION => CURL_SSLVERSION_DEFAULT, CURLOPT_SSL_VERIFYPEER => false ], ]); print_r($res); 

Any ideas? I’m guessing it has something to do how Guzzle handles HTTP SSL requests, since it is also using cURL underlying, I am confused why this wouldn’t work.

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

Источник