Critical Error on plugin update 1.3.2

Hey @web4studio2019 ,

Thanks for trying that out. I’m still wondering if there might be something with the SSL or some data that might be in GoDaddy Payments somehow.

You mentioned admin access earlier on. Would that be a possibility? Is the staging site on GoDaddy?

Cheers,
Steve

Hi

Yes its a cpanel hosting package at godaddy. How can i send you the login credentials safely?

Many thx

Hey @web4studio2019,

For the staging site, can you please?add and account using the e-mail?[email protected]?so I can recover the account password and access the site to take a look?

Cheers,
Steve

Done / [email protected]

Hey @web4studio2019,

The password reset link doesn’t appear to work on the staging site.

Would it be possible to send a password for the account you created to the same support@ e-mail address via QuickForget?

Cheers,
Steve

You’ve got mail ??

Hey @web4studio2019 ,

Thanks! ??</img>
I logged in and installed the previous version, which installed and activated without issues. I then ran a test transaction using a test card number to see if it would connect through and send an invalid card response.

I received an “OpenSSL unable to sign data” error on Checkout with this test. I ran some SSL tests against the domain and they are seeing a certificate that is self-signed/untrusted. I tried with the site set to https as well. The certificate was created Nov 22. Do you happen to know if it was created and applied to the staging site around that time, or any other information on it?

Cheers,
Steve

Hi Steve

Regarding SSL i have no idea. What we can do for now?

Hey @web4studio2019

Hope your weekend was good!

How did you go about creating the staging site? Was this originally on a GoDaddy WordPress/WooCommerce Managed plan?

I’m wondering if there might be some references to a previous SSL Certificate from the move to staging. There are ways to install an SSL Certificate on the staging site, which might help with the OpenSLL errors when trying to authenticate. This would be a bit out of our support policy, but I can send some ideas to get you started on this.

Cheers,
Steve

Hi

Yes it was a MWP –> CPanel hosting.

Now the SSL is active.

Pls check again. The solutions is not to update the plugin for now?

Many thx

Nadine

Hey @web4studio2019,

The SSL tests correct now, but I was still seeing the OpenSSL errors with the previous version when attempting to place a test transaction.

With the earlier version active, I was able to check the settings for the plugin. It looked like the Private Key was shorter than it should be, so I swapped over some other credentials from one of my test accounts and the Open SSL error went away on Checkout. It seems that the Private Key is incorrect, and therefore wasn’t able to authenticate, as well as causing the issues with the update.

I put your original credentials back in place. What you will want to do next is:

• Login to your GoDaddy Payments dashboard and go to Advanced Tools > Business Settings > Contact Info.
• Copy your Application ID and Private Key in the Poynt Collect API Settings section.
• In your WooCommerce store, go to WooCommerce > Settings > Payments > GoDaddy Payments and paste these credentials in the Application ID and Private Key fields.
• Click Save Changes.

Once this is done, can you please let me know and I can test out another transaction to see if the OpenSSL error is resolved, then attempt to update the plugin.

Cheers,
Steve

Hi

I did also updated to PHP 8.1

Many thx

Hey @web4studio2019 ,

Thanks for getting back on this!

I logged in and checked the Private Key at WooCommerce > Settings > Payments > GoDaddy Payments and it still looks to be rather short. The Private Key should be several lines and the Private Key is only showing 30 or so characters.

Are you getting the Private Key from your GoDaddy Payments account directly? Would you please let me know if I can access the account to take a look at the settings?

Cheers,
Steve

Hi

Yes directly from GoDaddy Poynt Settings. I think i can’t regenerate a private key. Because it will generate a problem with the live site. Right?

Which account you wann access? GD?

The plugin update today caused a PHP Fatal error; had to disable the plugin by re-naming the plugin directory. Running PHP 8.1 on a Divi site.  

Update today caused [02-Feb-2023 15:54:45 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home//public_html/wp-content/plugins/godaddy-payments/vendor/composer/platform_check.php' (include_path='.:/opt/cpanel/ea-php81/root/usr/share/pear') in /home//public_html/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php:25
Stack trace:

0 /home//public_html/wp-content/plugins/godaddy-payments/vendor/autoload.php(7): ComposerAutoloaderInit3fb05797026c18af4559e5e459e1ddca::getLoader()

1 /home//public_html/wp-content/plugins/godaddy-payments/godaddy-payments.php(105): require_once('/home//…')

2 /home//public_html/wp-includes/class-wp-hook.php(308): GD_Poynt_For_WooCommerce_Loader->initPlugin('')

3 /home//public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)

4 /home//public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

5 /home//public_html/wp-settings.php(480): do_action('plugins_loaded')

6 /home//public_html/wp-config.php(119): require_once('/home//…')

7 /home//public_html/wp-load.php(50): require_once('/home//…')

8 /home//public_html/wp-admin/admin.php(34): require_once('/home//…')

9 /home//public_html/wp-admin/index.php(10): require_once('/home//…')

10 {main}

thrown in /home//public_html/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php on line 25