Support

June 1, 2020 at 5:22 am

@nysn

I have no idea what they have done on their servers to cause this but it is obviously an issue with their set up somewhere. I can’t reproduce it on my own servers so can’t narrow it down further to give more details.

You can link them to this thread as it provides all the details they would need to troubleshoot this, including a script to show the exact issue.

June 1, 2020 at 7:24 am

I’ve split your thread from the original as the error on your test is completely different.

The error you are getting is:

L_SHORTMESSAGE0=Security%20error&L_LONGMESSAGE0=Security%20header%20is%20not%20valid

99.9% of the time the API credentials are incorrect when you get that error.

So, lets first confirm you are using a PayPal Pro account? (If you don’t pay a monthly fee to PayPal that is separate from your transaction fees to use ‘Website payments pro’ then you don’t have a PayPal Pro account).

If you are 100& sure you have a PayPal Pro account then check your credentials are correct:

https://eventespresso.com/wiki/paypal-pro-payment-gateway/#locate

Remember that test script uses Sandbox credentials and NOT live credentials. So if your testing using that, use Sandbox creds.

June 1, 2020 at 8:14 am

My account and details are proper. it is deducting money from credit card and credited to paypal as well but still it displays this error http://prntscr.com/srpp2x

This error, is the same as the original thread and it is not the same error thrown on your site with my test script which you mentioned HERE.

When testing the script you must use PayPal Sandbox credentials set on lines 3-5. This is due to the fact that it is against most payment merchants TOS to test payments on live and PayPay will still charge you the transaction fee even after a refund, so we don’t run tests on live creds at all.

The ‘Security header is not valid’ error you are getting on the script can happen for a few reasons but as mentioned 99.9% of the time the credentials are incorrect and that will be the case here if you are using live credentials within that script (or no credentials at all).

—-

So, the error from the screenshot is the same error from the previous thread and as you can see in the other thread its a GoDaddy issue. The user in that thread moved from GoDaddy to another host and it instantly worked meaning this isn’t something within EE.

If your account is charging the cards and you get the ‘No Response from PayPal error’ message when hosted by GoDaddy it is likely you are running into the same issue and you’ll need to contact GoDaddy support from them to investigate.

June 2, 2020 at 4:36 am

I understand you’re stuck in the middle, but as far as I am aware there isn’t anything I can do to ‘fix’ this on our end, I’ve already gone through all troubleshooting steps for this with the previous report and the replies you are getting from GoDaddy are pretty much exactly the same. If GoDaddy can show me something different I’ll happily test it and apply a fix to EE if needed but you need someone at GoDaddy higher than level 1 tech support to troubleshoot this rather than them simply brushing it off and stating nothing is wrong and it must be a plugin issue.

They (GoDaddy) simply stating the server is working as is and its the plugin at fault is their canned response. Unless they can see an Error 5XX thrown somewhere they simply pass it off as a plugin issue.

As shown in the other thread, this code is working on other hosting platforms but GoDaddy… meaning it is a GoDaddy issue.

The script I created to test this runs completely outside of both WordPress and Event Espresso simply using cURL to connect with PayPal and that still fails with the exact same problem, again meaning its a server/GoDaddy issue and nothing to do with the plugin. There is nothing special going on with these requests, they are simple cURL GET requests.

All of the details they need are in the other thread here:

https://eventespresso.com/topic/paypal-pro-no-response-received-from-paypal-pro-3/#post-311964

Now, one thing we haven’t done is actually confirm this is the same issue. The screenshot you sent looks like it is, but it’s possibly not. So, if you’d like to send me FTP credentials over I’ll run the script I created using my sandbox credentials and see if its the same error is thrown (I’m 99% sure it will be).

If you’d like me to do that, you can send the credentials using this form:

https://eventespresso.com/send-login-details/

June 3, 2020 at 3:33 am

My Developer posted all required things.

Sorry but I don’t follow, posted where? To GoDaddy?

Today we got another issue for one of the user which is nothing in your Event queue . http://prntscr.com/sss9lk

That can happen if the EE critical pages are cached.

Are you using the GoDaddy Managed WordPress hosting package? If so they force caching on all pages and that will need to be disabled. Take a look here:

https://eventespresso.com/topic/incompatible-with-godaddy-managed-wordpress-hosting/

Personally, my recommendation would be to move away from using GoDaddy and/or the managed WordPress package. I’ve posted details on why a few times so rather than retype it all out, I’ll like to one of those posts HERE.

June 3, 2020 at 6:20 am

Right now all of the cURL tests are passing and function as expected, if you test a PayPal Pro payment now does it work?

Looking through your payment logs you’re getting this on some but not all payments, is that right?

The logs show the same error (error 28 on cURL requests to PayPal) when this fails so I still stand by this being a GoDaddy issue but if it’s intermittent it’s going be harder to troubleshoot.

June 3, 2020 at 8:38 am

Then yes, it’s the same issue, only for your site its intermittent and I have no idea why. The code within EE doesn’t change between transactions so it’s not the code, I don’t know why this issue is appearing on GoDaddy servers but it’s pretty clear the issue is upstream from Event Espresso.

So again, personally I would move away from GoDaddy and use something like WPEnding. Although I would also likely move away from using PayPal Pro as it has the highest possible PCI requirements for you to follow.

June 5, 2020 at 6:44 am

did you get our credentials ?

Yes, I got your credentials, that’s how I could run the test script using sandbox credentials above and look through your payment logs.

As mentioned above all of the tests are currently passing and nothing on our end has changed, this is an issue with GoDaddy and not something I can dig into any further than I already have.

Do you suggest any other hosting platform ?because I do see in your forum many complained about WP engine as well.

99% of the time people post an issue with WPEnging it is simply becuase they haven’t contacted them to exclude EE’s pages from the sever side caching they have in place. We have some documentation on how to set up WPEngine here:

https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/

Am I 100% certain moving hosts will fix the above? No, because I can’t reproduce it to know what the problem is. But, I can tell you that all of the reports of this issue so far have been from GoDaddy servers and nothing from WPEngine.

June 15, 2020 at 6:02 am

I don’t have any other hosting recommendations.

The host you use is a personal choice and depends on many different factors ranging from cost, location, traffic, type of hosting, personal experience with a specific host etc. That is why you don’t find many recommendations for specific hosts from Event Espresso as we really don’t have any host-specific requirements.

However, between your previous post and the one above I’ve been working with another user using a dedicated server from GoDaddy and we were able to do some additional troubleshooting there. On their server, the issue with connecting to PayPal was due to using the latest version of cURL (7.70.0), they dropped back to 7.69.X and the connection worked fine.

Can you check which version is installed on our site?

You can do that using a plugin such as PHP Info: https://wordpress.org/plugins/php-info-wp/

Or manually running phpinfo() on your server.

Then search for cURL and find the version number.