Error Processing Checkout. Please Try Again

Hello @microbe

Can you replicate this issue using a sandbox account? This would significantly speed up the analysis. You can also conduct this test on a staging site.

Furthermore, we would like to examine the plugin log files along with system report to gain more insight into this issue. Please note that log files are generated only if the “Logging” feature is activated in your plugin settings. To enable Logging:

• Go to the “Connection” tab in your plugin settings and activate “Logging.”
• Every transaction will now generate a log entry, which you can access by navigating to WooCommerce > Status > Logs.
• Select the most recent “woocommerce-paypal-payments” file corresponding to the date of the transaction in question.
• There is also a system report in the Status section.

It’s important to understand that if “Logging” wasn’t enabled before, there will be no previous records of the transactions. In that situation, we’ll need to wait for upcoming failed orders to generate new log entries.

Please provide those log entries on our?PrivateBin. After uploading, send us the link, so we can review them in detail.

If you do not wish to share this information publicly, we suggest you contact us directly for further assistance. We may need to examine your system report or logs to better understand what’s happening. You can open a ticket with our service desk. Here’s how you can request support: Request Support. Please make sure to include the URL of this thread in your ticket for reference.

Kind regards,
Krystian

Thank you log files sent to your bin.

I have just enabled logging, but I notice that there was a fatal error report related to an out of date customised “Customer processing order email” template in the theme directory. I have updated this and will monitor.

Hello?@microbe

Thank you log files sent to your bin.

We also need the link to this file. Keep in mind that we don’t have direct access to PrivateBin resources.

Thanks in advance.

Kind regards,
Krystian

Error log link:

https://privatebin.inpsyde.com/?a5362e9691403dd2#Eq64hhqzga5FCN5P7VE3LwRLP7r2ceECuvtbfrsSME4Y

Hello?@microbe

The logs you sent us don’t seem to come from our plugin, so it’s difficult for me to address their contents directly.

Let’s go back to the starting point – could you try replicating this issue with a sandbox account? Doing so could really help speed up our analysis. You might also want to perform this test on a staging site. A recording of the entire issue would also be very useful.

Otherwise, the only other option might be to wait for new logs to be generated when one of your customers encounters the issue again. However, I’d recommend trying to reproduce the behavior first.

Recently, we encountered a similar issue that turned out to be caused by a conflict with another plugin. This is why we need a system report, as it might help us identify the problematic plugin among the ones you’re using.

You can get it by navigating to the?WooCommerce / Status?section of your site. Once there, click on the?Get system report?button and then copy it by clicking on the?Copy for support?button.

Please provide those log entries on our?PrivateBin. After uploading, please paste here the link, so we can review them in detail.

Kind regards,
Krystian

System Status: https://privatebin.inpsyde.com/?608c69c050b5e2be#6kE5W8nbYxJ133jqoJ8hFBSoiQUqZkk4T7duwL8Et5gr

Hello?@microbe

Based on the list of plugins, I don’t see any that could likely cause this issue. The “CookieYes | GDPR Cookie Consent” plugin is a theoretical possibility, but the outcome should be different.

Could you try to replicate the problem and send us a recording? If you’re able to replicate it, I recommend checking if the issue persists when all plugins except WooCommerce and PayPal Payments are disabled. I suspect it might be a conflict.

Looking forward to your response.

Kind regards,
Krystian

To close this off. The issue has been identified as an error in a customised template. Thanks for you help with this, it did help me greatly in isolating and fixing the issue.

Hello?@microbe

I’m glad you were able to fix the problem, and thank you for letting us know what caused it.

If you have any questions, just let us know.

Kind regards,
Krystian