Hello, @awebster6112
Please, reactivate the Anti-Spam plugin with the “Complete deactivation” option enabled and then activate it again.
1. Enter the Antispam by Cleantalk plugin settings. (WordPress Dashboard -> Settings -> Antispam by Cleantalk -> Advanced settings)
2. Check the last settings “Complete deactivation” and save changes.
3. Deactivate the plugin on the “Plugins” page in WordPress Dashboard.
4. Then activate it.
5. Proceed to the plugin’s settings. (See item 1.)
Did it help?
Just wanted to chime in and say that this has started happening with CleanTalk on a large number of sites that I host and it’s creating high server loads / degraded performance.
@amagsumov that did not help. I followed your steps and the same issue continued to happen as soon as the plugin was enabled. I followed the steps a second time, and this time deleted the plugin. I re-installed the plugin and immediately upon activation, the site’s log began to fill as before.
“GET /?spbc_remote_call_token=TOKEN_NUMBER&spbc_remote_call_action=sfw_update__worker&plugin_name=apbct&test=test HTTP/1.1”
Hello @anotherdave @awebster6112
Thank you for your feedback.
Please give us 1-2 days for investigations.
You can try to rollback to 5.159.9 version until we fix the issue.
The downloaded link to 5.159.9:
https://downloads.wordpress.org/plugin/cleantalk-spam-protect.5.159.9.zip
-
This reply was modified 4 years, 6 months ago by
amagsumov.
Hello,
I’m sorry about the issue. We have fixed the problem.
Please, reinstall the plugin. ( Download link: https://github.com/CleanTalk/wordpress-antispam/releases/download/fix-version/cleantalk-spam-protect.zip )
The version will be the same: 5.160.
Here is an instruction you may find useful:
1. Go to the WordPress Administrator Panel —> Plugins.
2. Find the plugin “Spam Protection by CleanTalk” —> Deactivate.
3. After the automatic page refresh, find the plugin again “Spam Protection by CleanTalk” —> Delete. Confirm “Yes, delete these files”.
5. Go to Plugins —> Add New —> Upload Plugin.
4. Download the plugin archive from the link above.
6. Choose the downloaded archive and press “Install Now”.
Contact us if you have any questions.
@safronik the version at that link still causes the same problem.
spbc_remote_call_token=TOKEN_NUMBER&spbc_remote_call_action=sfw_update__worker&plugin_name=apbct
spbc_remote_call_token=TOKEN_NUMBER&spbc_remote_call_action=sfw_update__worker&plugin_name=apbct
spbc_remote_call_token=TOKEN_NUMBER&spbc_remote_call_action=sfw_update__worker&plugin_name=apbct&test=test
spbc_remote_call_token=TOKEN_NUMBER&spbc_remote_call_action=sfw_update__worker&plugin_name=apbct&test=test
I also followed the instruction to install the version downloaded in github (version 5.160.1-dev) and it is also still doing the same thing with the repetitive errors in the logs and excessive server load.
Had to disable the plugin for now. Checking my other sites that use the CleanTalk plugin as they might have to be disabled as well. Hopefully this can be fixed very soon.
Thank you for your feedback, @awebster6112, @probc.
Please, roll back to the previous stable version:
https://downloads.wordpress.org/plugin/cleantalk-spam-protect.5.159.9.zip
We will troubleshoot the issue in one business day, please wait.
@probc @awebster6112
Hello, we have made a fix that should help. There will no more than 600 such calls per the SpamFirewall update.
Please, download and isntall thwe version from here: https://github.com/CleanTalk/wordpress-antispam/releases/download/dev-version/cleantalk-spam-protect.zip (the version should be 5.160.2-dev)
You could use the instrustions froim here: https://wordpress.org/support/topic/plugin-keeps-calling-spbc_remote_call_token-hundreds-of-times-a-second/#post-14734241 (previous post)
Please, let us know if it helps and Thank you for the feedback!
@probc @awebster6112 hello.
I’m sorry about the issue. We have fixed it in 5.160.1 version.
Please, delete a dev/fix version (if already installed it from the github) and install 5.160.1 from the Wordrpess catalog.
Thank you so much for the cooperation!
We haven’t heard back from you in a while, so I’m going to mark this thread as “resolved”.
If you have any further questions, you can start a new thread.
