TypeError: reset(): Argument #1 ($array) must be of type array

  • Resolved 7thcircle

    (@7thcircle)


    11 months, 1 week ago

    When I attempt to login to my sites I am seeing this error with the latest version of your plugin

    2025/06/21 15:00:38 [error] 861772#861772: *31404 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught TypeError: reset(): Argument #1 ($array) must be of type array, string given in /var/www/example .com/htdocs/wp-content/plugins/cleantalk-spam-protect/lib/Cleantalk/ApbctWP/FindSpam/LoginIPKeeper.php:33
    Stack trace: 0 /var/www/example .com/htdocs/wp-content/plugins/cleantalk-spam-protect/lib/Cleantalk/ApbctWP/FindSpam/LoginIPKeeper.php(33): reset() 1 /var/www/example .com/htdocs/wp-content/plugins/cleantalk-spam-protect/cleantalk.php(183): Cleantalk\ApbctWP\FindSpam\LoginIPKeeper->addUserIP() 2 /var/www/example .com/htdocs/wp-includes/class-wp-hook.php(324): apbct_wp_login_actions() 3 /var/www/example .com/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 4 /var/www/example .com/htdocs/wp-includes/plugin.php(517): WP_Hook->do_action() 5 /var/www/example .com/htdocs/wp-includes/user.php(138): do_action() 6 /var/www/fotografi” while reading response header from upstream, client: 47.189.136.91, server: http://www.example .com, request: “POST /wp-login.php HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php/php83-fpm-example .com.sock:”, host: “www.example .com”, referrer: “https://www.example .com/wp-login.php”

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support eugenecleantalk

    (@eugenecleantalk)

    11 months, 1 week ago

    Hello.

    Thanks for the stacktrace of the error. We will look into it and get back to you within 3 business days.

    Plugin Support sergecleantalk

    (@sergecleantalk)

    11 months ago

    Hello,

    We’ve made fixes. You can use this fixed version; all fixes will be included in the next stable release.

    https://github.com/CleanTalk/wordpress-antispam/releases/download/fix-version/cleantalk-spam-protect.zip

    • Go to WordPress Administrator Panel —> Plugins.
    • Find the plugin “Anti-Spam by CleanTalk” —> Deactivate.
    • After the automatic page refreshing find the plugin again “Anti-Spam by CleanTalk” —> Delete. Confirm files deletion.
    • Download the plugin archive from the link.
    • Go to Plugins —> Add New —> Upload Plugin.
    • Choose the downloaded archive and press “Install Now”.
    • After the installation, activate the plugin, make sure that the access key matches the key from your CleanTalk Dashboard.

    Did it help?

    Thread Starter 7thcircle

    (@7thcircle)

    11 months ago

    The update seems to have solved the issue with the error but I am now seeing spam comments coming through even though I have not had them in the past and since I have post comments disabled in the plugin.

    Plugin Support eugenecleantalk

    (@eugenecleantalk)

    11 months ago

    Am I correct that your Service # is 1640806? You can find the Service # here: your CleanTalk dashboard → the “Settings” button under your site name.

    We will analyze the requests you marked as spam and respond within 3 business days.

    Thread Starter 7thcircle

    (@7thcircle)

    11 months ago

    That is one of them. This one 1640816 is better to look at since I have comments disabled on it and I have gone in a marked items as spam today.

    FYI…. The request that you marked, belongs to a trusted network and is used by search engines such as Google, Bing, Yahoo, Baidu, etc. As example: 172.70.47.159, 172.70.46.200, 172.70.46.126, 172.70.47.160, 172.70.46.220, 172.70.46.26

    • This reply was modified 11 months ago by 7thcircle.
    Plugin Support dimitrycleantalk

    (@dimitrycleantalk)

    11 months ago

    Hello @7thcircle,

    We’ve analyzed your requests. Currently, all your requests are coming through CloudFlare’s CDN, which means CloudFlare does not forward the real visitor IP by default. To resolve this, you’ll need to adjust a setting in your CloudFlare dashboard. Please enable the options listed here: https://developers.cloudflare.com/fundamentals/reference/http-headers/

    And you may need to disable the “Remove Visitor IP Headers” transform rule: https://developers.cloudflare.com/rules/transform/managed-transforms/reference/#remove-visitor-ip-headers

    After updating the settings, you can:

    • Make a test request and verify that your real IP is displayed in your Anti-Spam logs.
    • Or let us know, and we’ll check it for you.

    If you don’t know how to set up CloudFlare, please contact your hosting support.

    Did it help you?

      Thread Starter 7thcircle

      (@7thcircle)

      11 months ago

      While there may be an issue with the Cloudflare configuration, that should have no impact on the actual issue.

      As stated, the issue is that I have selected the option to disable comments on posts and with the patched version that option is not being honored. There is no need to mark a comment as spam if it not accepted in the first place.

      Plugin Support amagsumov

      (@amagsumov)

      11 months ago

      Hello @7thcircle,

      We checked the ‘Disable comments for all posts‘ option with the fix version, and it works. It appears that the option is currently disabled in the plugin on your site. Could you please check this?

      Thread Starter 7thcircle

      (@7thcircle)

      11 months ago

      I have it set to disable comments on posts on several sites and I saw comments come through on them.

      Plugin Support dimitrycleantalk

      (@dimitrycleantalk)

      11 months ago

      Hello @7thcircle,

      I’ve checked your service 1640806 and I see some comments on your blog. For this service you have enabled “Disable comments for all pages” and “Disable comments for all media”, but not “Disable comments for all posts“, for this reason you can see comments.

      For service 1640816 I don’t see any new comments because you have enabled all three options for this service.

      Could you please recheck this issue? If you have a recent example, please provide the service # and mark the requests in your Anti-Spam logs.

      Thank you.

      Plugin Support dimitrycleantalk

      (@dimitrycleantalk)

      10 months, 3 weeks ago

      Hello.
      We haven’t heard back from you in a few days, so I’m going to mark this topic as “resolved”.
      If you have any further questions, you can start a new topic or contact us via our private Ticket System: https://cleantalk.org/my/support/open.

    Viewing 11 replies - 1 through 11 (of 11 total)

    The topic ‘TypeError: reset(): Argument #1 ($array) must be of type array’ is closed to new replies.