Strange debug.log from your plugins

Hi There

I get some strange lines in my debug.log and it looks like its comes from one of your plugins... but i only have hummingbird running so it has to be this one becaus i dont think the dashboard does anything... but the debug log does not give much information it looks like this... any idea

[16-Mar-2017 17:46:21 UTC] [2017-03-16 18:46:21] - WPHB API: Sending request to
[16-Mar-2017 17:46:21 UTC] [2017-03-16 18:46:21] - WPHB API: Arguments:
[16-Mar-2017 17:46:21 UTC] [2017-03-16 18:46:21] - Array
[headers] => Array
[Authorization] => Basic 3217557c797b51f5097cc52ef67f6300d58caa15

[sslverify] =>
[method] => GET
[timeout] => 20

[16-Mar-2017 17:46:24 UTC] [2017-03-16 18:46:24] - WPHB API: Response:
[16-Mar-2017 17:46:24 UTC] [2017-03-16 18:46:24] - Array
[headers] => Requests_Utility_CaseInsensitiveDictionary Object
[data:protected] => Array
[date] => Thu, 16 Mar 2017 17:46:24 GMT
[content-type] => application/json; charset=UTF-8
[set-cookie] => Array
[0] => __cfduid=d54c0464b45131b4bd7781802042532141489686381; expires=Fri, 16-Mar-18 17:46:21 GMT; path=/;; HttpOnly
[1] => VN=1; expires=Fri, 16-Mar-2018 17:46:21 GMT; Max-Age=31536000; path=/
[2] => VNS=1; path=/
[3] => abv=b; expires=Thu, 16-Mar-2017 17:44:41 GMT; Max-Age=-100; path=/

[x-robots-tag] => noindex
[link] => <>; rel=""
[x-content-type-options] => Array
[0] => nosniff
[1] => nosniff

[access-control-expose-headers] => X-WP-Total, X-WP-TotalPages
[access-control-allow-headers] => Authorization, Content-Type
[allow] => GET
[content-security-policy] => default-src https: data: wss: blob: 'unsafe-eval' 'unsafe-inline'
[strict-transport-security] => max-age=31536000
[x-xss-protection] => 1; mode=block
[server] => cloudflare-nginx

  • Adam Czajczyk
    • Support Gorilla

    Hello Daniel,

    I hope you're well today and thank you for your question!

    The lines that you are referring to come from our Hummingbird. The plugin is logging its activity as this is often very helpful in case of any issues with it and helps debug/troubleshoot the problems. This is actually what the debug.log file is for.

    2MB isn't much actually but I can understand your concerns. Please note however that WP debugging shouldn't be turned on for a regular production site and by default it's not. It should be used during development or for troubleshooting and then those lines would be expected. Otherwise it's best to simply disable debugging by changing

    define('WP_DEBUG', true);

    line in "wp-config.php" file to

    define('WP_DEBUG', false);

    If you have any additional questions, let me know please.

    Best regards,

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.