Eve

Hi there,

This isn’t really a plugin issue. The Malware Scanner is using results from sitecheck.sucuri.net. You can feel free to contact [email protected] if you feel there’s an issue with SiteCheck.

Thanks,
Eve

You’re very welcome! I really hope we can figure this out. Do you see any message at the top of the screen when you try to save alert settings? For example, I changed 2 settings and see:

Sucuri: A total of 2 alert events were changed

The API key gets saved in the same sucuri-setting.php file along with the alert settings. That’s why you had to re-add the key. Can you log out/back in and see the API key is still active? It’s odd that the API key can be saved yet the alert settings can’t.

Sorry, I’ve tried various things to reproduce what’s happening here with no luck. I’m missing some clue. This is a Linux server? What version of PHP?

It can’t hurt to try deleting and reinstalling.

Hi there,

The alert settings get saved in the sucuri-settings.php. You might try moving that file to a different directory and deleting the ‘live’ one. The file should get recreated by the plugin. Your alert settings won’t be saved, but they can be copied back and it could shed some light on what’s happening.

I hope that helps!

Hey,

It sounds like there’s definitely an issue with permissions here. Does the absolute path for the data storage in the settings match what you expect and are checking? Can you save other plugin changes? Do you see the dates/times changing for sucuri-lastlogins.php?

Any errors in the logs?

Regards,
Eve

Hi there,

Please make sure the file sucuri-blockedusers.php exists in /wp-content/uploads/sucuri and is writable.

I hope this helps!

Regards,
Eve

Hi there,

Are you sure the full path to the sucuri settings folder is correct for the new server location?

Regards,
Eve

Hi there,

Can you please check the permissions for the Sucuri plugin settings folder/files and make sure they’re writable?

/wp-content/uploads/sucuri

Likely the plugin isn’t able to save the data. I hope this helps!

Kind regards,
Eve

Hi there,

That’s right, the plugin API key is for a particular URL and needs to be able to communicate with the API service for normal operation. In other words, for the plugin to be fully functional, it needs to be online and have an API key generated for the domain.

I hope that helps!

Kind regards,
Eve

Hi there,

You should be able to check the error logs and find the cause. And, yes, lack of memory or a timeout are the likely causes.

Kind regards,
Eve

Hi puregphx,

I’m sorry for the trouble. I installed Clef and was able to log in and out of my site just fine with the Sucuri plugin installed. I wasn’t able to reproduce the error. Have you done any hardening or other security measures that might be coming into play here?

Have you checked error logs for the 500 server error?

Thanks,
Eve

Hi psytanium,

I’m glad I could help.

Kind regards,
Eve

Hi sarumbear,

By default, all the plugin data is stored in the files in that directory /wp-content/uploads/sucuri. If the directory and files are writable, you shouldn’t need to update the path manually.

It is possible to change the location of the Sucuri data storage path by defining a constant in the ‘wp-config.php’ file named “SUCURI_DATA_STORAGE” with the absolute path to the new directory.

Thanks,
Eve

Hi jesahs,

I’m sorry, I’m not quite sure what you mean here:

“I used the feature to reset all my plugins.”

The Sucuri plugin has a reset feature that only resets its settings.

It sounds like you need to reinstall the plugins that have errors. Please provide more details about how the Sucuri plugin is being used here.

Thanks!
Eve

Hi tclaffy,

The support for the plugin is provided here on the WordPress support forum so that everybody can benefit from the questions and answers. ??

You can manually remove the folders /wp-contents/plugins/sucuri-scanner and /wp-content/uploads/sucuri to remove all plugin data. Some hardening options might need to be manually undone, but there shouldn’t be anything restricting access to your admin area.

I wasn’t able to reproduce the problem. Have you tried clearing your browser cache or accessing the dashboard in a different browser after the plugin is deleted?

Kind regards,
Eve