The plugin’s code is fine, I have been testing it during the last month, the two errors that you are mentioned are actually caused by the same thing which is the “[…] couldn’t connect to host”.
The plugin relies in an API service maintained by Sucuri, that error means that the plugin could not connect to that service, the second error message is irrelevant at the moment, it always appears in every PHP-based code when the application sends bytes before the HTTP headers are built.
I will contact the maintainer of the API service to see why it is failing, but again, the plugin’s code is fine but if anyone else experience the same issues do the same thing that @morbiusz did “[..] remove the plugin manually from the server” at least until I get an response from my co-worker about the issue with the API.
Hi Yorman
Thanks for your reply.
Problem seems to be gone now! I can access my sites again.
Does this has anything to do with what your co-worker did ?
No, my co-worker did nothing during this time span, the error “couldn’t connect to host” is temporary anyway, it is like when your Internet connection stops and you can not connect to any website, your web browser generally displays a message indicating that, something similar happens between servers from time to time.
Anyway, to prevent this issue again in the future I am going to modify the code that powers the plugin’s alerts to not display that error if the event is related with an user authentication, this will prevent the sending of extra bytes before the HTTP headers and subsequently fix the issues that you had.
I will leave this unresolved until I finish the code.
I finished the modification to prevent the error “headers already sent” during the user authentication process with commit 1183786 [1]. If you want to test the new code you can download the development version of the plugin [2] or you can wait until the next public release.
[1] https://plugins.trac.wordpress.org/changeset/1183786
[2] https://downloads.wordpress.org/plugin/sucuri-scanner.zip
