eStore Script Stuck at PayPal IPN Payment Verify

[nlarzill]

Hi, Suddenly, the Paypal IPN processing in wp-estore has stopped working.

Here is the content of the ipn_handle_debug.log file :

[12/27/2013 6:26 PM] – SUCCESS :Paypal Class Initiated by 173.0.81.1 eStore Version: 6.9.6.8

[12/27/2013 6:26 PM] – SUCCESS :Post string : [redacted]

The next log entry shoud be “Connection to [www.paypal.com] successfuly completed” but it never gets written in the log file.

I tried to narrow down the problem by adding additional debug logs in the paypal.php source file.

What I found out is that the script gets stuck on the “fgets” line in the following code :

// loop through the response from the server and append to variable

while(!feof($fp)) {

$this->ipn_response .= fgets($fp, 1024);

}

It seems that Paypal never sends any response string (whatever VERIFIED or INVALID) after the Post data is sent back to Paypal (IPN protocol).

I disabled all my plugins and reverted to the twenty-thirteen theme, but the problem is still here.

Any idea what is happening?

Regards,

Nicolas

[wpCommerce]

Hi, can you please connect to your site via FTP to see if there is any error_log file?

Has your hosting provider blocked the execution of fsockopen function for PHP?

[nlarzill]

I checked out the error_log file. The newest entry is 6 months old.

I asked my hosting provider for fsockopen and am awaiting the answer.

Meanwhile, I upgraded the estore plugin to is latest version (7.0.5) and slightly modified the code to force it to use the validate_ipn_using_curl function instead of the validate_ipn function which uses fsockopen.

Sadly the problem persists with curl.

The script gets stuck on the curl_exec instruction.

In the meantime, I also received an email from Paypal, stating that the IPN notifications sent to [http://anti-mildiou.com/wp-content/plugins/wp-cart-for-digital-products/paypal.php] have failed, with no further details.

Any clue?

Nicolas

[admin]

Have you seen what happens when you go to that IPN URL? It is automatically redirecting to the homepage which is wrong/strange.

You have got another script/plugin or hack somewhere on this site which is doing this auto redirection. So at this stage the IPN can’t be posted to that URL because it get auto redirected. Please fix that so that IPN url is accessible then test again.

[nlarzill]

The behaviour you observed was because I disabled the plugin during the night.

Now, it is active and you could check that the IPN url is triggering the paypal.php script.

To narrow down the problem, I made the following tests :

Test 1 :

To check if my Paypal merchant account could be faulty, I configured the e-store plugin with a different merchant account.

Result : exactly the same behaviour. The payment receives no validation response from Paypal during the IPN handshake.

Test 2 :

To check if my WordPress installation could by faulty, I installed a fresh WordPress on a subdomain.

The only plugin that I installed is the e-store plugin.

I made a test purchase.

Result : exactly the same odd behaviour.

Test 3 :

I made a test with the Paypal sandbox.

The main difference is the Paypal url that is used for the IPN handshake : [https://www.sandbox.paypal.com/cgi-bin/webscr] (SSL port 443)

AND IT WORKED FINE !

So my conclusion is : either the e-store plugin is faulty, either something is blocking at my hosting provider (Stablehost.com)

I tried with the latest version of the plugin as well as with the version I had on my blog, which is the previous version.

I also opened a ticket at Stablehost, but for the moment they have no clue what’s happening. They assured me that they don’t block the execution of fsockopen function for PHP.

With all these informations, I hope you can get closer to the problem.

Thanks for investigating further on your side.

Nicolas

[wpCommerce]

Hi, we will need to take a closer look at your site to investigate this issue. I have sent an email to your registered email address for site access. Let me know if you don’t receive it.

[nlarzill]

Hi,

My hosting provider moved my account to another server.

That solved the IPN issue.

This ticket can now be closed.

Thanks for your help.

Nicolas

[Author]

Posts