Jump to content

Paypal Error Send with CURL method failed ! Error 14094410 sslv3 alert handshake failure


msherif4u

Recommended Posts

Array
(
[0] => Making new connection to 'api-3t.paypal.com/nvp'
[1] => Connect with CURL method successful
[2] => Sending this params:
[3] => METHOD=SetExpressCheckout&VERSION=84&PWD=JYN3ZL4T3BETWKNX&USER=aqadir1981_api1.gmail.com&SIGNATURE=AFcWxV21C7fd0v3bYYYRCpSSRl31AOhMBQNJRj0WyjhxxGvGbZofWOqq&CANCELURL=http%3A%2F%2Fdandyflower.com%2Fquick-order%3Fpaypal_ec_canceled%3D1%26&RETURNURL=http%3A%2F%2Fdandyflower.com%2Fmodules%2Fpaypal%2Fexpress_checkout%2Fpayment.php&REQCONFIRMSHIPPING=0&NOSHIPPING=1&BUTTONSOURCE=FR_PRESTASHOP_H3S&L_PAYMENTREQUEST_0_NUMBER0=44&L_PAYMENTREQUEST_0_NAME0=Monstera+Deliciosa+-+Size+%3A+120cm&L_PAYMENTREQUEST_0_DESC0=Swiss+Cheese+Plant%0D%0ABotanical+Name%3A%C2%A0Monstera+DeliciosaCommon+Name%3A%C2%A0Monstera+DeliciosaApplication%3A+Floor+plantLight+Req...&L_PAYMENTREQUEST_0_AMT0=53.09&L_PAYMENTREQUEST_0_QTY0=1&PAYMENTREQUEST_0_PAYMENTACTION=Sale&PAYMENTREQUEST_0_CURRENCYCODE=USD&PAYMENTREQUEST_0_SHIPPINGAMT=8.17&PAYMENTREQUEST_0_ITEMAMT=53.09&PAYMENTREQUEST_0_AMT=61.26&ADDROVERRIDE=1&EMAIL=kibsmaaria%40gmail.com&PAYMENTREQUEST_0_SHIPTONAME=Mohammad+Sherif&PAYMENTREQUEST_0_SHIPTOPHONENUM=0552560700&PAYMENTREQUEST_0_SHIPTOSTREET=Al+Basra&PAYMENTREQUEST_0_SHIPTOSTREET2=&PAYMENTREQUEST_0_SHIPTOCITY=Al+Ain&PAYMENTREQUEST_0_SHIPTOSTATE=Al+Ain&PAYMENTREQUEST_0_SHIPTOCOUNTRYCODE=AE&PAYMENTREQUEST_0_SHIPTOZIP=15551&SOLUTIONTYPE=Sole&LANDINGPAGE=Login&USER=aqadir1981_api1.gmail.com&PWD=JYN3ZL4T3BETWKNX&SIGNATURE=AFcWxV21C7fd0v3bYYYRCpSSRl31AOhMBQNJRj0WyjhxxGvGbZofWOqq
[4] => Send with CURL method failed ! Error: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

Link to comment
Share on other sites

Which Paypal module version are you using ? Paypal does not support SSL 3.0 protocol since End of last year. You should update your  Paypal module.

 

See here: https://www.paypal-community.com/t5/PayPal-Forward/PayPal-Response-to-SSL-3-0-Vulnerability-aka-POODLE/ba-p/891829

 

And here: https://www.prestashop.com/forums/topic/380185-paypal-modification-ssl-v3-to-tls/

Edited by selectshop.at (see edit history)
Link to comment
Share on other sites

latest version is 3.8.4, so your's is outdated. You should download latest version. It depends on where you are located there are two versions. Paypal Europe (whole world, except USA, Canada) And Paypal USA.

 

You can download it here: https://www.prestashop.com/en/partners-free-module, choose payment modules, on page 3 you will find them.

Edited by selectshop.at (see edit history)
Link to comment
Share on other sites

i have upgraded but i get this error now

 

Please try to contact the merchant:

  1. <b>PayPal response:</b>
  2. TIMESTAMP -> 2015-06-23T09:26:23Z
  3. L_ERRORCODE0 -> 10605
  4. L_SHORTMESSAGE0 -> Transaction refused because of an invalid argument. See additional error messages for details.
  5. L_LONGMESSAGE0 -> Currency is not supported
  6. L_SEVERITYCODE0 -> Error
Link to comment
Share on other sites

This is common sense.  The error says that the currency is not supported.  So first, confirm what currency you are using on your store.  Second, confirm that Paypal supports this currency.

 

Once you have that information, contact Paypal support to determine how to proceed.

Edited by bellini13 (see edit history)
Link to comment
Share on other sites

  • 4 weeks later...

Hi,

I am getting the same error on my website prestashop version 1.5.2 and Paypal Module Version 3.10.1 Updated 22/07/2015

 

It was working fine for the last 2 years but all of a sudden since the 18th of July Started to get this error

 

Send with CURL method failed ! Error: Couldn't resolve host 'api-3t.paypal.com'
Connect failed with fsockopen method

 

This Doesn't happen every time but i get it this error 50% of the times someone tries to check out.

 

Curl is enabled on server

 

Any help would be appreciated

Link to comment
Share on other sites

the error says that connectron failed with both CURL and fsock (those are different things).  The actual error is that your hosting server cannot resolve the paypal URL api-3t.paypal.com

 

This is not a module issue, but rather a connectivity issue between your hosting server and the paypal gateway server.  You should raise this issue to your hosting provider and have them trace this problem for you.

Link to comment
Share on other sites

As also Bellini informed, your problem is a server problem. Any chance to upgrade the php-Version ? In fact you are having two problems related to your server: fsockopen and the api. Maybe that due to a bad configured firewall on your server the connection with paypal breaks or ends before handshake is finalized. This could have several reasons (firewall, execution time, cURL library outdated or broken). You should ask your provider and read the error-logs of your server and than fix the problem. It is not a Paypal or Prestashop error.

Link to comment
Share on other sites

Hi,

I am having a similar problem than xtremewarehouse.

It worked well for a long time and 3 or 4 days ago the error message came each time a customer wants to pay with Paypal

 

"Send with CURL method failed ! Error: Operation timed out after 0 milliseconds with 0 out of 0 bytes received
Connect failed with fsockopen method"

 

I am using Prestashop1.6.09 and uploaded the latest version of the Paypal module 3.10.1

 

I raised the issue with my internet provider and they said after investigating that it was not a server error but that the VPS IP address is being filtered by the Paypal system.and I needed to review myPayPal account settings or ask PayPal about their filter policy.

 

I contacted Paypal 2 days ago though their support website www.paypal.com/mts explaining my problem.

 

They got back to me straight away by email with the following message:

"If you can provide me with the IP addresses from which the payment requests are being sent to PayPal, I will verify with our network team and confirm if we are blocking your IP(s) or not."

 

I sent the IP address but they still didn't get back to me.

 

I will post their reply as soon as I have one but if anyone has a solution in the meantine I will certainely be very happy to hear it!!!

Link to comment
Share on other sites

Hi,

 

We had to move to a new server with another host and that solved the problem as we couldn't wait any longer.

 

However we have another issue after moving to the new server that the product url is not displaying Attributes and values so instead of displaying url 

 

http://xtremewarehouse.com.au/664-optimum-nutrition-serious-mass.html#/size-12lb/flavour-strawberry

 

it comes as

 

http://xtremewarehouse.com.au/664-optimum-nutrition-serious-mass.html#/-/-

 

Any idea why this is happening

 

Thanks in advance

Link to comment
Share on other sites

Hi,

 

We had to move to a new server with another host and that solved the problem as we couldn't wait any longer.

 

However we have another issue after moving to the new server that the product url is not displaying Attributes and values so instead of displaying url 

 

http://xtremewarehouse.com.au/664-optimum-nutrition-serious-mass.html#/size-12lb/flavour-strawberry

 

it comes as

 

http://xtremewarehouse.com.au/664-optimum-nutrition-serious-mass.html#/-/-

 

Any idea why this is happening

 

Thanks in advance

Please open a new topic, as your problem is not related.

Link to comment
Share on other sites

I just got a reply from Paypal Technical Support Team (finally after 3 days!!) with the following message:

Daniel, sorry for the delayed response. Our network team confirmed the following :

"After observing at this IP, we do not see any blocking or preventing access to 203.56.191.195."

If this is the IP from where your API requests are originating from, then it is confirmed that PayPal is not blocking that IP.

Based on this, I wanted you try the following from the server that is sending these requests.

- Run a traceroute to the endpoint that you are trying to connect to. Command to be ran is :

tracert api-3t.paypal.com

Please provide me with the outcome."

Link to comment
Share on other sites

My saga is not over!!!!

 

I contacted again my hosting company and sent them Paypal reply. They answered within minutes and according to them Paypal is at fault.

Here is the message they sent me which I forwarded to Paypal:

 

 

"The trace route that they have requested is available below:

traceroute api-3t.paypal.com
traceroute to api-3t.paypal.com (173.0.84.101), 30 hops max, 60 byte packets
1 202.87.31.155 (202.87.31.155) 0.049 ms 0.015 ms 0.013 ms
2 bdr.mx1.eqx.sis.net.au (122.252.0.193) 7.818 ms 7.980 ms 7.969 ms
3 ten-0-2-0-922.bdr02.syd03.nsw.VOCUS.net.au (114.31.200.141) 7.934 ms 7.932 ms 7.916 ms
4 ten-0-2-0-5.cor03.syd03.nsw.VOCUS.net.au (114.31.192.60) 163.774 ms 163.908 ms 164.152 ms
5 ten-0-1-0-4.cor01.syd04.nsw.VOCUS.net.au (175.45.72.120) 163.694 ms ten-0-5-0-1.cor01.syd04.nsw.VOCUS.net.au (175.45.72.118) 163.394 ms 163.395 ms
6 ten-0-0-0-1.cor02.sjc01.ca.VOCUS.net (114.31.199.36) 163.791 ms ten-0-1-0-1.cor02.sjc01.ca.VOCUS.net (114.31.199.44) 160.122 ms ten-0-0-0-2.cor01.sjc01.ca.VOCUS.net (114.31.199.29) 159.687 ms
7 bundle-100.bdr03.sjc01.ca.VOCUS.net (114.31.199.123) 160.557 ms 157.008 ms bundle-100.cor02.sjc01.ca.VOCUS.net (114.31.199.59) 156.019 ms
8 bundle-100.bdr03.sjc01.ca.VOCUS.net (114.31.199.123) 157.111 ms 157.761 ms ae8-561.sjc12.ip4.gtt.net (46.33.90.49) 183.791 ms
9 ae8-561.sjc12.ip4.gtt.net (46.33.90.49) 178.607 ms paypal-gw.ip4.gtt.net (173.205.56.6) 184.162 ms 184.189 ms
10 64.4.244.160 (64.4.244.160) 177.689 ms paypal-gw.ip4.gtt.net (173.205.56.6) 178.234 ms 64.4.244.152 (64.4.244.152) 183.798 ms
11 64.4.244.100 (64.4.244.100) 201.186 ms 64.4.244.160 (64.4.244.160) 183.877 ms 183.671 ms
12 64.4.244.94 (64.4.244.94) 197.324 ms 203.198 ms 64.4.244.84 (64.4.244.84) 196.167 ms
13 64.4.244.80 (64.4.244.80) 202.208 ms * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

You can see that we are not able to reach their API from the VPS (203.56.191.195) and the trace stops at their IP address 64.4.244.80:

http://whatismyipaddress.com/ip/64.4.244.80

The IP is definitely blocked at their end."

 

Hopefully I will see the end on it soon!!

Happy to hear from anyone if you have some ideas!!!

Edited by Daniel D (see edit history)
Link to comment
Share on other sites

actually that is a successful traceroute.  routers and devices can be configured to ignore these types of traces which is why you see *** at certain steps

 

instead, tell your host to try to telnet to paypals gateway on port 443.  the output should look something like below.

telnet api-3t.paypal.com 443

Trying 173.0.88.101...
Connected to api-3t.paypal.com.
Escape character is '^]'.

as you can see, I am able to connect.  see what your output would be

Link to comment
Share on other sites

Hi Thanks for the help.

I contacted my host to telnet to paypals gateway on port 443 and they got:

 

telnet api-3t.paypal.com 443
Trying 173.0.92.21...
Connected to api-3t.paypal.com.
Escape character is '^]'.
Connection closed by foreign host.

 

I am still waiting for Paypal to reply :-(

Link to comment
Share on other sites

telnet api-3t.paypal.com 443

Trying 173.0.92.21...

Connected to api-3t.paypal.com.

Escape character is '^]'.

Connection closed by foreign host.

How long before the "connection  closed by foreign host" appeared?  From the looks of it, your IP is not blocked and the connection likely timed out

Link to comment
Share on other sites

so thats a 30 second time out.  which is pretty common if you do not send any information to them.  you have to keep in mind we are using telnet to open a connection to Paypal, but you are not sending them any information during this test.  So after 30 seconds, Paypal hangs up.

 

This all looks normal, Paypal does not appear to be blocking this IP address

Link to comment
Share on other sites

I am hitting desperation point.

And Paypal still doesn't get back to me despite calling them every day!

 

This is the last reply from my host:

 

"""If that is normal behavior for paypal telent SSL connection than it means that the connection is established.

I see that the outoging connections filter is disabled so there is no way that the connection is being filtered from the VPS and I also see that ModSecurity has been disabled for the affected host.

I really don't see what else we could do regarding this case. Still PayPal should be the one that support their plugins/modules so its their opinion that would matter the most...""""

Link to comment
Share on other sites

I finally got a reply from Paypal. After one week!!!

here is their reply:

"According to our(PayPal) logs, the merchant has attempted to connect 6 times to 3 different IPs associated with api-3t in the last 7 days. 
 
4 - 173.0.92.21
1 - 173.0.84.101
1 - 173.0.88.101
 
The 173.0.92.21 was removed from DNS on 7/25 which means that it was probably wired off from api. The fact the merchant attempted to connect to this IP after it was removed from DNS indicates the merchant is using hardcoded IPs in their application configuration instead of using DNS. 
 
The other two attempts to the current api servers were both attempts over port 80. api-3t does not accept connections over port 80, they must use 443. 
 
Recommend to Merchant:
Remove any references to api-3t by IP address in merchant’s application
Ensure all connection attempts are using TLS with the default port (443)"
 ==============================================================================================================
 
I don't understand the 2 recommendations to merchant.
Could someone explain? Is there anything I could do on my side?
Thanks
Edited by Daniel D (see edit history)
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...