Block Access to debug.log with JetHost Total Care
When WordPress debugging is enabled, error messages and warnings may be saved to a file called debug.log. That’s useful for troubleshooting, but if this file is publicly accessible, it can reveal sensitive site information. The JetHost Total Care block access to debug.log feature protects that file with a single click – no coding or .htaccess edits needed.
Why You Might Want to Block Access to debug.log
The debug.log file can contain paths, plugin names, database issues, and other technical details that don’t belong in public view. If someone knows where to look, they might be able to access that file and learn things about your site you’d rather keep private.
Blocking access to debug.log helps you:
JetHost Total Care lets you disable it directly from your WordPress dashboard.
What Is the debug.log File in WordPress?
When WP_DEBUG_LOG is enabled, WordPress writes error output to a file called debug.log, usually located inside the /wp-content/ directory. This file logs all PHP errors, notices, and warnings generated while the site is running.
While the file is helpful during development, it becomes a liability if left accessible in production.
How to Block Access with JetHost Total Care
To control autosave using JetHost Total Care:
1. Log in to your WordPress dashboard.
2. Open the JetHost Total Care section from the sidebar.
3. In the tab Security, look for the setting labeled Disable Database Error Reporting.
4. Toggle the switch to turn it on.
JetHost Total Care saves the change automatically when you toggle the setting.
What Happens After You Apply the Setting
Once enabled, JetHost Total Care blocks public access to the debug log file. If someone tries to visit the file directly in the browser, the request will be denied. You can still view the log through file access or hosting tools, but it stays hidden from the outside.
This helps maintain a clean, secure front end while preserving useful logs for troubleshooting.
JetHost Experts Tip
If you use WP_DEBUG_LOG, always pair it with this setting. Keeping debug.log open to the web is one of the most common security oversights in WordPress sites under development.
Need More Help?
The JetHost Total Care block access to debug.log feature adds quiet protection for a file that’s easy to forget but often targeted. It’s a small but important step toward a safer WordPress setup. Check out more WordPress security tutorials to keep your site clean, stable, and under control.