Geen API-sleutel verschaft

Hi @tastymouse,

This error usually appears when the connection to Mollie can’t be established as the result of a missing API key. This is not an error I would expect with an already configured plugin unless there are any connection issues on your server.
It looks like the payment methods are loading in the checkout now, so it should be working.

Are there any security plugins that could interfere with external connections?
We’d be interested in the full Mollie log with these entries.
You can share it either here in the forums or privately with us from here:
https://mollie.inpsyde.com/docs/request-support/

Thanks!

Kind regards,
Niklas

Hi @niklasinpsyde,

I sent the logfiles through
https://mollie.inpsyde.com/docs/request-support/

Thanks, Tom

This error usually appears when Mollie is active without having an API key set, or when the connection to Mollie is blocked for some reason.
In our investigation, we didn’t find a reason for this to randomly occur but are keeping an eye on this in our internal support ticket in case it happens again.
Since there is not much more to add here, for now, I will mark this thread resolved and provide an eventual status update later on, if appripriate.

Kind regards,
Niklas

Just wanted to let you know that all of a sudden on a working live site of one of my clients this error occurred. This resulted in the admin emails ‘New order’ not being sent. The error notice says the error occurred during a status change. Since status changes trigger emails this makes sense. The question is why does this error happen out of the blue? Should I re-enter the Mollie API key as the notice suggests? How can an API key that has functioned properly suddenly be missing?

I paste the error notice from the Order Notices below:

Fout tijdens statuswijziging. [2022-02-14T10:18:46+0000] Geen API-sleutel geleverd. Plaats je Mollie API-sleutels hieronder.

I noticed that in version 7.0.2. you rolled back the code to version 6.7.0. Could it be that the above described error was caused by the version 7.0.1. that was launched on 14-2-2022, since we started to see the error as of that version. And if this is what happened, will 7.0.2. fix this error?

Hi,

We also encountered this error since upgrading to 7.0.1.

In addition the logs contain errors like:

2022/02/15 22:08:15 [error] 885546#885546: *623867 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: Argument 2 passed to Mollie\WooCommerce\Gateway\MolliePaymentGateway::onOrderReceivedText() must be an instance of WC_Order, null given, called in /var/www/html/REDACTED/wp-includes/class-wp-hook.php on line 307 and defined in /var/www/html/REDACTED/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/MolliePaymentGateway.php:1099
Stack trace:
#0 /var/www/html/REDACTED/wp-includes/class-wp-hook.php(307): Mollie\WooCommerce\Gateway\MolliePaymentGateway->onOrderReceivedText()
#1 /var/www/html/REDACTED/wp-includes/plugin.php(189): WP_Hook->apply_filters()
#2 /var/www/html/REDACTED/wp-content/plugins/woocommerce/templates/checkout/thankyou.php(84): apply_filters()
#3 /var/www/html/REDACTED/wp-content/plugins/woocommerce/includes/wc-core-functions.php(345): include('/var/www/html/k...')
#4 /var/www/html/REDACTED/wp-content/plugins/woocommerce/includes/shortcodes/class-wc-shortcode-checko" while reading response header from upstream, client: REDACTED, server: REDACTED, request: "GET /afrekenen/order-received/REDACTED/ HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/7.4-fpm.sock:", host: "REDACTED"

Also order statuses are not updated after marking them complete because the API key would be missing.

Fout tijdens statuswijziging. [2022-02-15T15:33:04+0000] Geen API-sleutel geleverd. Plaats je Mollie API-sleutels hieronder.

Something seems to be very broken in this update.

• This reply was modified 2 years, 9 months ago by koningsvh.
• This reply was modified 2 years, 9 months ago by koningsvh. Reason: Fixed version number

Installing 7.0.2. fixed the issue.

@wpwebbouw Thanks for letting us know.

Hi everyone,

There was a bug in version 7.0.1 that could cause a similar error to the one originally reported in this thread, but the cause of the problem is actually a different one.
Version 7.0.2 is rolling back the code to the state of version 6.7.0 to prevent this and so we can take a bit more time to address eventual concerns that were brought up.
We regret the trouble but highly appreciate the feedback.

Kind regards,
Niklas