• Really tired of this plugin, I have had multiple problems from it. Everything from valid users routinely locked out to it setting off rfxn’s malware detect.
    {CAV}MBL_5927227 : /var/www/vhosts/customerdomain/httpdocs/wp-content/uploads/sucuri/sucuri-auditqueue.php => /usr/local/maldetect/quarantine/sucuri-auditqueue.php.228973341

    This weekend was kind of the end of my rope. Out enjoying Saturday afternoon with my wife, not a chance we get very often. I get a call on Saturday afternoon from a paniced website owner, site down, 500 error, checked on my phone all wordpress sites down. Sure enough, it is Sucuri and every site is throwing a 500 error. Ended up going back into the office and stripping it off 40+ sites because every one of them was down. Log message if anyone is interested:
    mod_fcgid: stderr: PHP Fatal error: require_once(): Failed opening required ‘src/settings-hardening.php’ (include_path=’.:/opt/plesk/php/5.6/share/pear’) in /var/www/vhosts/customerdomain/httpdocs/wp-content/plugins/sucuri-scanner/sucuri.php on line 22

    Not sure if the whole issue was caused by Plesks auto update or what, but no settings-hardening.php in any of the sites and it sure wasn’t going to get created when it was throwing a 500 error! Poor release / patch management if you ask me, and thanks for letting it slip out on a weekend, and a holiday weekend as well!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thank you for your feedback.

    The file “settings-hardening.php” is available here [1] with the rest of the code. A normal WordPress plugin update would have downloaded the entire Zip archive which includes this and the other files and after the extraction WordPress would have activated the update.

    I am 100% sure that the problem that you are facing with your installation of Plesk cannot be fixed with a change in the release management from our side. I don’t know how Plesk handles an update, but it is possible that it was cloning the files one by one rather than downloading the entire update at once. You will have to check your Plesk configuration to know what happened.

    Unless this is a recurrent problem with other users, I will consider this ticket an isolated edge case triggered by a misconfiguration of a 3rd-party software used to replace the WordPress update mechanism. If that’s not the case, please let me know and I will investigate further.

    [1] https://plugins.svn.wordpress.org/sucuri-scanner/trunk/src/

    Hi,
    I’m getting close to the same result on one of my sites.

    From my error_log:
    [Wed Apr 11 11:54:07 2018] [warn] [client [my_ip] mod_fcgid: stderr: PHP Fatal error: require_once(): Failed opening required ‘src/template.lib.php’ (include_path=’.:/opt/plesk/php/7.1/share/pear’) in [domain_root]/wp-content/plugins/sucuri-scanner/sucuri.php on line 207

    This is causing a 500 error on any task that requires signing in (login.php) or anything that provides access to make edits to site content (user accounts, posts) via Formidable.

    I’ve been trying to trace the issue to see if it is a plugin, theme, or core conflict, or some combination of the three, but I am still encountering the issue when I strip the site down to using only the twentyseventeen theme and only have the securi plugin active.

    I’ve been experiencing the login issue on both the live site where this plugin is installed, as well as on a local version of the same site; also note this is where the stripped down version mentioned in the prior paragraph is located. Fortunately, this seems to be the only site that is experiencing this issue.

    Thoughts?

    […] require_once(): Failed opening required ‘src/template.lib.php’

    This is not a bug in the code.

    What this error is saying is that the file in quotes doesn’t exists.

    Please upload the plugin to the web server one more time and verify that all the files listed in the Subversion repository here [1] are present in the plugin’s directory here [2]. Don’t forget to upload all the files in the sub-directories, specially the ones listed here [3]. Even if you already know all this, I want to make sure that we are both clear on what needs to be done before we move to the next step.

    Fortunately, this seems to be the only site that is experiencing this issue.

    This is also proof that there is no bug in the code.

    If you have installed the plugin in multiple websites, and the error is only affecting one, this is reason enough to believe that the problem is actually in the web server where the errors are being triggered. Something in your Plesk installation is either deleting this PHP file or preventing the PHP interpreter to load it.

    Make sure that all the files exist.

    If the error persists, contact your hosting provider.

    I am fairly certain that the problem is caused by a misconfiguration of the server.

    [1] https://plugins.svn.wordpress.org/sucuri-scanner/trunk/
    [2] /wp-content/plugins/sucuri-scanner/
    [3] https://plugins.svn.wordpress.org/sucuri-scanner/trunk/src/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fed Up with Sucuri’ is closed to new replies.