If by any chance you are hosting your site in a Windows server then I have to tell you that we discovered an incompatibility between the plugin and the Curl extension installed in most IIS servers. Somehow (I have not investigated this much) the server is removing the very last parameter in every HTTP request executed by the site, which in this specific case is the “k” parameter that has the API key, so when the request reaches the Sucuri server where the API service is hosted the key is not present and it considers the action as invalid and consequently reports that error message “Key not set”.
In the other hand, if you are hosting your site in a different system (Unix, BSD, MacOS, other) then this may be a generalized bug and I will have to investigated with more patience.
Right now we have no patch for this issue, but one of my co-workers (who knows more about Windows than me) is investigating and trying to fix it, if he succeeds we will release an update with the new code. I will leave this ticket as un-resolved until we find the solution.
Thread Starter
voneff
(@voneff)
Hello Yorman,
thank you very much for getting back to me so quickly!
I checked back: Sucuri itself puts out the info under “Site Info” that the OS is “Linux (32 Bit)”.
Therefore, Windows can’t be the issue.
Thank you for looking into this. If you need more info from let me know!
Cheers
Alex
I see, it may be a generalized error, maybe something specific to the server environment. I will start collecting information in some web servers that I own to see if I am able to reproduce the issue. I will update this ticket when I have more information.
I finished working on this with changeset 1165881 [1] where I added an option in the settings page to test the ability of the site to send HTTP requests with valid data and get the expected response. This can be used to check if the issue is with the plugin itself or the HTTP transport protocol configured in the server.
[1] https://plugins.trac.ww.wp.xz.cn/changeset/1165881
Get_logs: Key not set.
Same problem here.
Newest Wordpres & newest plugin versions
It obviousely brings the error messages only on a certain hoster (Hosteurope.de)
Sucuri: (1452195870) Get_logs: Key not set.. if Display audit report disabled
Sucuri: (1452200217) Get_logs: Key not set..
Sucuri: (1452200219) Get_logs: Key not set.. if Display audit report enabled
Sucuri: (1452200367) Get_logs: Key not set.. if Display audit report disabled again
Sucuri: (1452200422) Get_logs: Key not set..
Sucuri: (1452200425) Get_logs: Key not set.. if Display audit report enabled again
So obviousely the bracketed numbers come from a sequential numbering …
Linux wp349 3.15.8-xenu-static-x86_64-he+1 #6 SMP Wed Aug 20 13:24:06 UTC 2014 x86_64
PHP Version 5.3.29
“This can be used to check if the issue is with the plugin itself or the HTTP transport protocol configured in the server.”
I can’t get it how to “check” or use this check?!?
br
Heinz
btw
I’ve already removed the original api key.
Recovering it failod as I never got an email with the key.
So I generated a new one
