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

  • Details: https://www.pulpnest.in/wp-content/debug.log is publicly accessible and may expose source code or sensitive information about your site. Files such as this one are commonly checked for by scanners and should be made inaccessible. Alternately, some can be removed if you are certain your site does not need them. Sites using the nginx web server may need manual configuration changes to protect such files

    The page I need help with: [log in to see the link]

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

  • What’s your question, really?

    The debug file is only created when you turn on WordPress debugging AND you add the WP_DEBUG_LOG constant which creates the debug.log file. WordPress never does this by default, and you should not have debugging turned on on a production site anyway.

    Note that the WP_DEBUG_LOG definition also allows you to set any location of the output file.

    So if you’re not actively debugging your site, turn off debugging. And if debugging is turned OFF already, delete the debug.log file.

    Debugging in WordPress

    Thread Starter pulpnest cahndigarh

    (@sunilkanojiain)

    and this file debug.purge.log

    Thread Starter pulpnest cahndigarh

    (@sunilkanojiain)

    how to turn off WordPress debugging?

    how to turn off WordPress debugging?

    In a nutshell, check your wp-config.php and if you find:

    define( 'WP_DEBUG', true );

    Change it to:

    define( 'WP_DEBUG', false);

    But I’ll highly recommend you read the entirety of the official support article on WordPress debugging I provided above.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Publicly accessible config, backup, or log file found: wp-content/debug.log’ is closed to new replies.