Erroneous Debug Log

  • Resolved mikepalmer

    (@mikepalmer)


    7 months, 3 weeks ago

    Litespeed Cache has started creating erroneous debug logs in the wp-content folder of all my websites despite debug being turned off. An example of the text in the debug log is as follows:

    07/23/24 04:01:13 – init with cfg result :

    Wordfence is flagging this up in its scan as a critical issue:

    Publicly accessible config, backup, or log file found: wp-content/debug.log

    The timestamp is the same as that of the creation of the following two files in wp-content:

    .litespeed_conf.dat and object-cache.php.

    I am guessing that I should just ignore the critical issue in the Wordfence scan, but why is the debug file being created?

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

  • I’ve had the exact same problem! What is going on and do I need to do anything to fix it?

    Plugin Support qtwrk

    (@qtwrk)

    for .litespeed_conf.dat it will give 403 error if accessed, object-cache.php won’t be executed on direct access

    for wp-content/debug.log , it’s actually the default wordpress debug log path , 

            RewriteCond %{REQUEST_URI} debug\.log
            RewriteRule .* - [F,L]

    you can put a rewrite rule like this to forbid access it though.

    Thread Starter mikepalmer

    (@mikepalmer)

    @qtwrk thank you. That stops the scan from flagging up the issue.

    Hello,
    Same problem here.
    We can forbid access, but the file size keeps growing and growing. Is it possible to avoid the wp-content/debug.log file to be generated ?

    Plugin Support qtwrk

    (@qtwrk)

    from our plugin , you need to go to toolbox -> debug setting -> set debug log to OFF , then it will stop writing log into this file

    if you still see it grows, then it’s wp writing , you need to disable wp debug log

    @qtwrk

    We are having the same issue and got notified by our security monitor.

    Our WP_DEBUG is always disabled, and we just checked again to confirm. After the recent update of the LiteSpeed Cache plugin, it started generating logs even though the setting under Toolbox -> Debug Settings -> Debug Log is set to OFF (which is the default setting). When we disable the LiteSpeed Cache plugin, the debug logs are not generated.

    Upon tracing what is writing to the log, it points directly to the LiteSpeed Cache plugin.

    Could you please investigate this bug as it poses a security issue? Our monitoring systems keep flagging it.

    • This reply was modified 7 months, 3 weeks ago by ro4x.
    Plugin Support qtwrk

    (@qtwrk)

    please create your own topic @ro4x , and share what is the content in debug.log it generates when you set our plugin’s debug log to OFF

    Thread Starter mikepalmer

    (@mikepalmer)

    @qtwrk Actually I specified the content in my original post. A debug file is created with a single line as follows:

    07/23/24 04:01:13 – init with cfg result :

    Date and timestamp will obviously be different.

    Plugin Support qtwrk

    (@qtwrk)

    I looked at the source code again , that log is generated when debug log is enabled

    please make sure you set debug log to OFF in our plugin.

    I’ve encountered the same problem. “Debug Log” is set to “OFF” but after the update to the most recent version of the plugin (6.3) the file /wp-content/debug.log was created and subsequently flagged by my security monitor.

    Plugin Support qtwrk

    (@qtwrk)

    per forum guideline, please create your @james4311 own topic for your issue.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Erroneous Debug Log’ is closed to new replies.