Title: Erroneous Debug Log
Last modified: July 24, 2024

---

# Erroneous Debug Log

 *  Resolved [mikepalmer](https://wordpress.org/support/users/mikepalmer/)
 * (@mikepalmer)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/)
 * 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)

 *  [whoplaros](https://wordpress.org/support/users/whoplaros/)
 * (@whoplaros)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17909460)
 * I’ve had the exact same problem! What is going on and do I need to do anything
   to fix it?
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17909736)
 * 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,
 *     ```wp-block-code
               RewriteCond %{REQUEST_URI} debug\.log        RewriteRule .* - [F,L]
       ```
   
 * you can put a rewrite rule like this to forbid access it though.
 *  Thread Starter [mikepalmer](https://wordpress.org/support/users/mikepalmer/)
 * (@mikepalmer)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17909886)
 * [@qtwrk](https://wordpress.org/support/users/qtwrk/) thank you. That stops the
   scan from flagging up the issue.
 *  [Digijazzy](https://wordpress.org/support/users/digijazzy/)
 * (@digijazzy)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17909919)
 * 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](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17909934)
 * 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
 *  [ro4x](https://wordpress.org/support/users/ro4x/)
 * (@ro4x)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17911779)
 * [@qtwrk](https://wordpress.org/support/users/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 1 year, 10 months ago by [ro4x](https://wordpress.org/support/users/ro4x/).
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17913128)
 * please create your own topic [@ro4x](https://wordpress.org/support/users/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](https://wordpress.org/support/users/mikepalmer/)
 * (@mikepalmer)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17913196)
 * [@qtwrk](https://wordpress.org/support/users/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](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17913221)
 * 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.
 *  [james4311](https://wordpress.org/support/users/james4311/)
 * (@james4311)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17920226)
 * 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](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17920423)
 * per forum guideline, please create your [@james4311](https://wordpress.org/support/users/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.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 11 replies
 * 6 participants
 * Last reply from: [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * Last activity: [1 year, 10 months ago](https://wordpress.org/support/topic/erroneous-debug-log/#post-17920423)
 * Status: resolved