Customer documentation
Backups & fixes
Back up cPanel sites, prepare migrations, protect credentials, and collect the right details for support.
Backups and migrations
Before major edits
Download files and export databases before plugin updates, code changes, or DNS moves.
Before migration
Collect files, databases, email needs, DNS records, and any cron jobs before moving a site.
Before deleting
Confirm backups work before removing old files, archives, or mail.
When support helps
Include domain, source host, target service, and what you already exported.
What to back up
Files
Download public_html and any addon domain or subdomain document roots that serve the site.
Databases
Export each database used by the site, especially WordPress or PHP app databases.
Email
If email is hosted in cPanel, preserve mailboxes or confirm whether mail needs migration.
DNS
Record A, CNAME, MX, TXT, SPF, DKIM, DMARC, and important subdomain records before nameserver changes.
Cron jobs
Copy scheduled task commands and timing before migration.
Config files
Save .htaccess, wp-config.php, app config files, and any custom PHP settings.
Restore checklist
- 1Confirm which site, folder, and database need to be restored.
- 2Back up the current broken state before replacing it, in case you need to recover recent changes.
- 3Restore files to the correct document root.
- 4Restore the database only if the app needs database rollback.
- 5Confirm config files still point to the right database and domain.
- 6Clear caches and test the exact URL that was failing.
- 7Open support if restore fails and include the backup date, domain, folder path, and database name.
Safe cPanel habits
Back up before major edits
Download or create backups before changing files, DNS, databases, or plugins.
Protect credentials
Do not send passwords in screenshots or public chat. Use portal tickets for account-specific help.
Know the document root
Most simple sites use public_html. Addon domains and app folders may use different roots.
Open tickets with context
Include domain, service, exact error, recent changes, and any relevant log line.
Metrics, errors, and logs
Bandwidth
Use bandwidth data to see whether traffic spikes align with slowdowns or limits.
Disk usage
Check storage before uploads, backups, email growth, or database imports.
Errors
Use cPanel error tools or error_log files when pages return 500, blank screens, or PHP warnings.
Visitors
Visitor tools can help confirm whether traffic is reaching the hosting account.
Raw logs
Useful when support needs request-level evidence, but avoid sharing logs publicly.
Cron jobs and scheduled tasks
Cron jobs run commands on a schedule. They are useful for app maintenance, queues, reports, and recurring cleanup, but a bad cron job can overload a hosting account.
Command
The exact command cPanel runs, such as a PHP script or app CLI command.
Schedule
How often the command runs. Start less frequently unless the app requires more.
Email output
Cron output can send email every run. Disable or redirect noisy output when appropriate.
Working path
Use full paths when possible so the command runs from the expected location.
Troubleshooting
If cron does nothing, check the command path, PHP version, permissions, and whether output contains an error.
cPanel troubleshooting
Wrong page loads
Check the document root, confirm files are in public_html or the configured folder, and clear app cache.
HTTPS fails
Confirm DNS points to the hosting account, wait for propagation, then check SSL/TLS or AutoSSL.
Database fails
Confirm database name, database user, password, host, and user privileges.
Email fails
Check Email Routing, MX records, mailbox quota, spam filters, and whether the domain uses external mail.
Storage full
Remove old backups, logs, archives, unused mail, or open a ticket to discuss limits.
Support checklist
- Include the domain, service tracking ID, and cPanel username.
- Describe the exact cPanel tool or page involved.
- Copy the exact visible error text, but do not include passwords or secret tokens.
- List recent changes: DNS edits, file uploads, plugin updates, database imports, or email routing changes.
- Attach screenshots only after hiding passwords, API keys, and private customer information.