• Resolved blkcatgal

    (@blkcatgal)


    Hello.
    I have been getting the following message: Sucuri: (1459784066) Get_logs: SSL connect error. And the audit logs are not available. This has been happening off and on for some time now. Also, sometimes when the audit logs are available, it appears all events are not listed.

    And just lately, when I’ve tried to publish or update a post, I got this message:
    Sucuri: (1459926037) Send_log: SSL connect error.

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/54/2776154/html/wp-content/plugins/sucuri-scanner/sucuri.php:7307) in /home/content/54/2776154/html/wp-admin/post.php on line 197

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/54/2776154/html/wp-content/plugins/sucuri-scanner/sucuri.php:7307) in /home/content/54/2776154/html/wp-includes/pluggable.php on line 1228

    When I went back and tried again, the post published.

    Could you explain what is going on and how this can be fixed? Thank you.

    https://wordpress.org/plugins/sucuri-scanner/

Viewing 2 replies - 1 through 2 (of 2 total)
  • The error is produced by an incompatibility between the OpenSSL library installed in the server where your website is being hosted and the SSL certificate associated to the domain where the Sucuri API service is running.

    There is no easy way to fix this, there are three possible ways to fix this: (1) is to recompile the OpenSSL library in your server to support the encryption used in the SSL certificate of the wordpress.sucuri.net website, (2) is to re-issue the SSL certificate, and (3) is to force the plugin to send the HTTP requests via HTTP instead of HTTPS. All of the options might result in a new problem but the last one is the easiest one and that is what I am going to do right now.

    I will add a new option in the plugin’ settings to allow the admin of the website to force the HTTP requests to go through plain HTTP (which is not recommended) and talk with my co-workers in the infrastructure department to see if we can do something in the server to facilitate the communication.

    Task finished with this commit [1]. Once the admin of the projects reviews the changes in the code and merges this pull-request [2] it will be released in a new version of the plugin so you can have the fix for this problem. Alternatively, you can choose to install the development version of the code from here [3].

    [1] https://github.com/cixtor/sucuri-wordpress-plugin/commit/dd2edbd
    [2] https://github.com/Sucuri/sucuri-wordpress-plugin/pull/7
    [3] https://github.com/cixtor/sucuri-wordpress-plugin/archive/master.zip

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Problem with getting audit logs’ is closed to new replies.