|
bmachuel
|
April 5, 2017 at 7:49 am
Hi there,
Since yesterday there has been two registrations on our website, and both of them have triggered an error 500 at the end of the PayPal payment process (after being taken to the PayPal website and filling-in the credit card form, when pressing the “pay now” button). The error page is displayed immediately after pressing the button.
Before that, the error 500 had never happened since the opening of registrations in October 2016.
I have looked for information in the logs (in Payment methods>Log) but there is nothing there that I can intuitively link to the error. Could you please explain how to use this information (unless there is a more simple solution)?
Many thanks,
Benoit Machuel
|
|
Tony
|
April 5, 2017 at 8:20 am
Hi there,
What version of Event Espresso is the site currently running? It depends on what error is being thrown on the site but in 4.9.36 we added some additional error checking for payment methods so if you not on that version I’d recommend updating.
I have looked for information in the logs (in Payment methods>Log) but there is nothing there that I can intuitively link to the error. Could you please explain how to use this information (unless there is a more simple solution)?
There’s a lot of information in those logs and it really depends on what your troubleshooting as to how you use them, we can’t really provide information on how you use the logs as its different for every case.
For example if cURL isn’t correctly configured on the server, the connection would be refused by your payment provided and the payment log would show that response.
An error 500 usually means a fatal error is being thrown which kills the script meaning it can’t write any useful information to the log, or its already written to the log and then the error has happened. For those errors you need to take a look within the servers error logs around the time of the transaction to see what error is being thrown.
|
