Error processing cards

Hello there,

Thank you for reaching out about our plugin, GoDaddy Payments for WooCommerce! I’m happy to assist you with this. ??

Thank you for providing screenshots of the issues you are seeing! I understand that on the form you are getting an “OpenSSL” error, but you are also getting a fatal error when attempting to save changes to the plugin’s setting. While CloudFlare’s CDN and caching can cause issues for gateways at times, I would like to tackle some initial testing. Since you are getting a critical error, that is usually at the code level rather than the API level of the plugin so debug mode for the plugin may not help us just yet.

I would like to enable WP Debug mode to get some more information from your site to help determine the cause of this issue.

You would need to edit the wp-config.php file. Near the bottom of this file you’ll find a line that looks like the following:
define( ‘WP_DEBUG’, true );

What we’d need to see here is the following three lines:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);

If you already have those three lines in your wp-config.php file, would you please ensure that WP_DEBUG and WP_DEBUG_LOG are set to true and WP_DEBUG_DISPLAY is set to false?

Alternatively, you can try installing a plugin such as the free Debug plugin. I’d like to note that plugins aren’t able to enable debug mode in all server environments so editing the wp-config.php file is the preferred method.
1) Once debug mode is turned on WordPress will start logging all PHP errors to a file called wp-content/debug.log.
2) Run through duplicating the error by attempting to place an order.
3) Then check the debug.log, and if anything recorded in it, send it on over to us for review.

Could you give the WordPress Debug Mode a try and let me know if it logs anything for us to review?

Best wishes,

Zach B

Hey there,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Zach B ??

Hello

Still getting?OpenSSL unable to sign data error.

I have disabled Jetpack and still.

please find the error log at https://hydronicsdepot.com/debug.log

• This reply was modified 1 month, 4 weeks ago by gtaheatca.

Also, I have updated all plugins and templates

Hey gtaheatca,

I’m sorry for the delay in responding to you. We’re currently experiencing a very high volume of support requests and are working hard to help as quickly as possible.

Thank you for reaching back out to us for assistance, but I’m sorry to hear that you are still having issues. I appreciate you sending over the debug log and letting us know that all the plugins and theme are updated. Thanks for lettings us know about disabling Jetpack as well.

After reviewing the logs, it seems there are a lot of PHP errors. May I ask what version of PHP you are using?
Thanks ??

All the best,
Amber

Hey gtaheatca,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Kayla ??

Hello

No it has not been resolved and I sent you an email last week I have not gotten any response. Here is the error log

https://hydronicsdepot.com/debug.log

Hi @gtaheatca!

David here, stepping in, and?I’m sorry to hear that you are still having issues with this on your WooCommerce store. I’m happy to help! ??

I want to thank you for providing a link to your debug.log file. This is truly helpful!

I was able to locate the following message:
[02-Oct-2024 13:08:49 UTC] PHP Warning: openssl_sign(): supplied key param cannot be coerced into a private key in /home/u245370445/domains/hydronicsdepot.com/public_html/wp-content/plugins/godaddy-payments/vendor/firebase/php-jwt/src/JWT.php on line 242

I have taken a look at this, and found that it may be an issue with the private key that you are using in your WooCommerce settings for GoDaddy Payments. This can break if a site migrates servers or a domain is changed.

To see if this is the case, you can perform the following steps to reset it.

1. Log in to your GoDaddy Payments dashboard and go to Business Settings > Contact Info.
2. Copy your Application ID and Private Key in the Poynt Collect API Settings section. (Re)generate the Private Key.
3. In your WooCommerce store, go to WooCommerce > Settings > Payments > GoDaddy Payments and (re)paste these credentials in the Application ID and Private Key fields.
4. Click Save Changes.

Can you give this a try and let me know if it works?

Thanks,
David

Hey gtaheatca,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Jesse ??