I don’t have any other comparable support requests, so I’m not inclined to think that it’s due to PayPal changes, although that’s always a possibility.
That error generally comes if you’re getting an HTTP error when attempting to contact PayPal.
Have you added any plug-ins recently or changed hosts?
Thread Starter
giuze
(@giuze)
I did some updates but I don’t see how it would interfere with your plug-in. I don’t have other plug-in that has paypal payments options.
I could see that PayPal use other IP Adresses and those might be blocked so I also contacted my host.
Thread Starter
giuze
(@giuze)
Hello, I tried to figure out what could cause this timeout.
The strange thing is that the error says:
WP_Error Object
(
[errors] => Array
(
[http_request_failed] => Array
(
[0] => cURL error 28: Connection timed out after 10001 milliseconds
)
)
[error_data] => Array
(
)
)
And the max_execution_time of php was 60 seconds and even increased to 240 by my host right now. I still have a 10s timeout.
Do you have any idea what can cause that timeout to be so “short”?
Thread Starter
giuze
(@giuze)
Hello, in Paypal.php, changing the url on line 12
from https://www.paypal.com/cgi-bin/webscr to https://ipnpb.paypal.com/cgi-bin/webscr solved the problem.
I think you should include that in the next update.
Best Regards
Thread Starter
giuze
(@giuze)
It says on this page that use of the ipnpb address is strongly recommended
Interesting. The target date for that changeover, I understand, is June 2018, so it’s interesting that you’re having this experience now. I’ll have to do some testing, since I’ll really need to know why you’re having this problem before I can consider making the change – either so I can detect what scenario makes it required or to confirm that it will work for all users.
Thread Starter
giuze
(@giuze)
The target is june 2017, but it was for https use, they are not really talking about ipnpb.paypal.com vs http://www.paypal.com expect that they really recommend that use.
Thread Starter
giuze
(@giuze)
I followed a few links and end up here:
https://www.paypal-notice.com/en/IPN-Verification-Postback-to-HTTPS/
Under technical Details it is interesting to see:
The ipnpb.paypal.com and ipnpb.sandbox.paypal.com endpoints accept only HTTPS connections. If you currently use http://www.paypal.com, you should move to ipnpb.paypal.com when you update your code to use HTTPS.
It is a bit contradictory as just after they mention http://www.paypal.com instead of ipnpb.paypal.com
They really put the accent on using https but not much on using the ipnpb address!
Thread Starter
giuze
(@giuze)
Hi, just wanted to let you know that I got many tickets sold today and the ipn worked immediately and didn’t had any error since I changed that link.
Thread Starter
giuze
(@giuze)
I could see you changed the address in the new release, thank you
