The issue seems to have resolved itself. Same key in use as before.
Maybe it was a one-time issue. Please let us know if the issue returns.
The issue returned. Same cURL error, 77.
I removed and added the same key back and synced with cloud. This fixed it.
Hello,
Thank you for your update.
If the issue returns, please do the following:
- Check if our IPs are available from your web server: https://cleantalk.org/help/cleantalk-servers-ip-addresses (points 1-3).
- Check if CURL support and allow_url_fopen (in php.ini) options are available and enabled on your web server.
Thank you.
Hello,
I have not blocked any IPs for outbound connections from the server so #1 doesn’t apply.
For #2 we should be good there too:
Statistics
- Last spam check request to https://moderate9.cleantalk.org server was at Feb 23 2026 10:56:53.
- Average request time for past 7 days: 0.239 seconds.
- Last time SpamFireWall was triggered for 47.128.16.111 IP at Feb 23 2026 10:54:22
- SpamFireWall was updated Feb 23 2026 10:31:02. Now contains 18504 entries.
- SpamFireWall sent unknown events at Feb 23 2026 10:29:56.Plugin version 6.73.1
Server requirements check
- PHP version: 5.6+ (check)
- cURL support: enabled (check)
- allow_url_fopen: enabled (check)
- PHP memory_limit: 128M+ (check)
- max_execution_time: 30+ (check)
- secondscURL multi-request functions: enabled (check)
Connections
There are no failed connections to server.
Hello @dave-lozier
Please, contact our support team via our private ticket system: https://cleantalk.org/my/support/open. We will be able to gather some more information from you concerning this issue and will review our logs.
Hi, I am facing the same issue. I did not change anything; the key is still valid. But this morning it says “Feb 23 2026 22:04:06: Error occurred while checking account status. cURL error 77: error setting certificate file:”
Hello @vaibhavb2004, @dave-lozier
Please try to switch the “Use WordPress HTTP API” option:
WordPress Admin Page → Settings → Anti-Spam by CleanTalk → Advanced settings → change the “Use WordPress HTTP API” option → Save Changes.
Did it help?
Hi @katereji – The “Use WordPress HTTP API” setting was “ON” so I set it to “OFF”.
Initially there was no difference, it was working either way. But now I got the cURL error again with the setting “OFF”. I believe the path for the cert file is incorrect?
Feb 24 2026 04:36:04: Error occurred while executing CleanTalk Cron job. cURL error 77: error setting certificate file: /home/norsklithium.com/public_html/wp-includes/Requests/src/../certificates/cacert.pem
The directory /home/norsklithium.com/public_html/wp-includes/Requests/certificates/ and file /home/norsklithium.com/public_html/wp-includes/Requests/certificates/cacert.pem does not exist.
@katereji – I think I found the issue. We run our cron jobs using wp-cli which was using a different PHP package than what our web server uses. I corrected this so hopefully we’ll not see the error going forward.
Thank you!
Thank you for letting us know, @dave-lozier
Please contact us if you encounter this or other errors in the future.
Hello.
We haven’t heard back from you in a few days, so I’m going to mark this thread as “resolved”.
If you have any further questions, you can start a new thread or contact us via our private Ticket System: https://cleantalk.org/my/support/open.
