Safely free up valuable hosting storage space by removing obsolete error logs without affecting website data.
Large error_log files can consume valuable hosting storage over time. If you have already reviewed the errors and no longer need the log history, you can safely remove it from your hosting account via the 1-grid Customer Zone without deleting your core website files or databases.
Before You Begin
Before deleting an error log file, make sure you meet the following requirements:
- Access to your 1-grid hosting account
- You no longer need the information inside the log for active troubleshooting
- You have reviewed or downloaded a local copy if you might need the error history later
💡 Important: Deleting an error log removes the historical record of those specific errors. It does not fix the underlying website, application, or PHP configuration issue that generated them.
Delete Your Error Log
1. Open Your Hosting Account
Log in to your 1-grid Customer Zone and open the specific web hosting service package associated with your target website. Launch the native hosting control panel available for your account.
2. Open File Manager
Navigate to and open the File Manager utility, then locate the specific website directory containing your error_log file. Depending on your configuration, this file typically sits directly inside the root folder where your application runs.
3. Review the Error Log
Before deleting the file, right-click and view or open the error_log contents to confirm you are finished investigating any active faults. Download a backup copy to your local machine if retention is required.
4. Delete the Error Log
Select the target error_log file, click Delete, and confirm the prompt when requested.
📝 Note: Only the selected log file is purged. Your website code, database structures, and other operational data remain untouched.
5. Check Your Website
Open your live website in a separate browser tab to verify everything functions properly. Check your disk metrics via Understanding Hosting Disk Usage to confirm the reclaimed space. If a fresh error_log file immediately regenerates, your application is still experiencing active PHP or script errors.
What Happens Next?
Clearing an error_log resets your current error history, but it does not patch code-level errors. If your storage usage spikes again rapidly, consult our related articles below for some more information.
You’re Ready!
Removing obsolete log files is a quick and straightforward way to optimise your server storage metrics. Just remember to verify log contents before running deletions, especially if you are actively debugging site performance.
Related Articles
- How to Run Cron Jobs in cPanel
- How to Delete Cron Jobs in cPanel on 1-grid Hosting
- Understanding Hosting Disk Usage
- cPanel: How to Use the Disk Space Usage Tool
Need Help?
If you are uncertain whether a particular log file can be dropped safely, or if your application faults persist after clearing storage, contact us. Our Support team is here to help.
To help us investigate efficiently, please have the following ready:
- Your domain name
- Your active hosting package
- A screenshot or excerpt of the error log contents
- Any active error messages visible on your site
- A brief description of current website behaviour