SteveB9990

Hi Serge,

Thanks for getting back to me.

The spam mail was outbound due to the plugin being turned off, thus my contact form was unprotected and was being used/abused by spammers. The plugin is now turned on again, and the spammers can no longer access the contact form.

Regarding the ‘technical issue’, I received one email advising me of the problem after I had turned the plugin back on again, but after I had spent a little time delving into the settings, the problem appears to have been solved.

Happy days!

Hi Alexander,

email sent ??

Nice to hear, because I’m totally fed up with forwarding files to you, or marking them as approved, only to get an email the very next day warning me about the very same files!!! Even when you’ve given them the green light, they still come back to haunt my dashboards!

Basically, it appears that somewhere along the line, you broke something which didn’t need fixing!

In short, it’s not the hosting.

The issues with Cleantalk just seem to grow by the day.

I was receiving errors, which I reported on here, and was asked to wait a few days. That was 1 week or so ago, but the errors just get worse by the day. The irony is that the very first critical error is ALWAYS spbcScannerH.php, which is used by … Cleantalk!

Furthermore, despite no updates or changes being made, the list of critical errors just grows by the day. Why? It’s almost like you’re making it up!

I’m fast reaching the point of dumping Cleantalk. How am I to know what actually IS critical, if you just keep making the list grow, and I can’t actually send the files for analysis, because the buttons don’t work???

I’m pretty certain that I won’t be renewing my subscriptions for anything if this nonsense carries on much longer. Like I said before, it’s almost like you’re making it up.

Anti-Spam ends in July 2021. Security ends in October 2023. SSL certs end in April 2022.

Hi,

Both plugins were up to date on both sites, and discovered that all was well on one of my sites without having to make any changes. My other site, on the same hosting package/platform was still giving errors, so …

I enabled allow_url_fopen using MultiPHP INI Editor via cPanel on both sites, but it made no difference whatsoever on the site which was giving most of the errors???? I’m still getting the error message(s) … 2020-08-05 05:59:10: Sending security logs: CONNECTION_ERROR: “cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received” … when I go to Settings > Security by CleanTalk, and still showing the ‘Critical’ PHP function, despite having approved it a squillion times!

BTW, both sites use exactly the same theme template, and utilise exactly the same plugins. Settings used anywhere and everywhere on both sites are also exactly the same.

CleanTalk Security and Anti-Spam are producing errors every time I login … and for no apparent reason. What I’m pretty sure of though, is that the errors appeared to begin at a point when updates occurred. Very annoying.

As it stands, I think I might well be looking for an alternative provider for the security of my sites, unless the issues are fixed very soon.

I’m having exactly the same issue, and have been receiving emails about it every day since July 23rd, despite approving the file marked as malware and forwarding said file for analysis … although I didn’t receive a response to that. I’ve just sent it again, several times, but I don’t get any form of message confirming that the file has been sent???

Anyway, it’s a security function generating the warning … wp-content/plugins/security-malware-firewall/lib/SpbcScannerH.php.

To add to the issue, for the last two days I’ve also been receiving error messages when I view the Security by Cleantalk page. The latest error says this … 2020-08-05 05:59:10: Sending security logs: CONNECTION_ERROR: “cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received”

I’m having the exact same problem, i.e. failed install due to missing style.css file, even though it is definitely there.

So far, I’ve received the same error message with at least 14 different themes!

At first I assumed that perhaps the themes file structure was wrong, but for it to occur with several different themes suggests that something else could be wrong?

BTW, I’m using WP V3.3.1.