Know which account controls what
cPanel usually manages the hosting account, while the domain registrar manages ownership of the domain and may also manage DNS. Email could be hosted in cPanel or by a separate provider such as Microsoft or Google.
Write down where each service is controlled. During an outage, this prevents unnecessary changes to the wrong system.
- Domain registrar
- DNS provider
- Web hosting/cPanel
- Business email provider
- SSL source if not automatic
File Manager and the document root
The public website normally lives in a document root such as public_html or a domain-specific directory. Keep only files required by the site in the public path.
Old ZIP archives, database exports, debug scripts, and backup copies should not be left publicly accessible. When replacing the site, take a backup and preserve configuration intentionally rather than uploading several generations into the live directory.
- Know the live document root.
- Avoid editing production files without a backup.
- Remove old archives after deployment.
Databases and users
MySQL Databases and phpMyAdmin are commonly used to manage database names, users, privileges, and tables. A database user should have the privileges the application requires, and credentials must match the production configuration.
Schema changes need the same care as code changes. An application can produce HTTP 500 errors if the code expects a column or table that was never added to the live database.
- Back up before structural changes.
- Confirm the selected database before running SQL.
- Keep development and production schema changes documented.
Resource usage and error logs
Disk space is only one hosting resource. cPanel environments may also limit CPU, memory, entry processes, I/O, database connections, or file counts. A site can fail while plenty of disk space remains.
Use Resource Usage and Errors information to identify what is actually being exhausted. Pair the timestamp with application error logs before upgrading a plan.
- Check the exact resource limit.
- Look for traffic spikes or background tasks.
- Investigate slow queries and repeated failures.
SSL, redirects, and security
Use HTTPS for the entire public site and make sure certificates renew correctly. Avoid creating redirect loops by configuring HTTPS in multiple layers without understanding how the host or proxy already handles it.
Protect cPanel with multi-factor authentication, use strong unique passwords, and remove unnecessary FTP accounts. If SSH or SFTP is available, prefer encrypted file transfer methods.
- Enable two-factor authentication.
- Review additional FTP or email accounts.
- Keep recovery email and phone information current.
Backup before every risky change
cPanel may provide automated backups, but you should still understand how to restore. Before editing PHP code, changing a database schema, or replacing a site package, take a fresh backup of files and the relevant database.
A backup that has never been tested should be treated as unverified. For important systems, periodically restore to a safe location or confirm the host's recovery procedure.
- Back up files and database together.
- Record the time of the backup.
- Do not overwrite the only working copy while troubleshooting.