What this guide helps you do
A practical first-hour walkthrough for domains, SSL, email, files, databases, backups and account security. The first hour in cPanel should be about understanding the account before changing anything. Identify the primary domain, verify that DNS points where you expect, confirm the PHP version, inspect disk usage, and locate the backup tools supplied by the host. cPanel is an account control panel, not a replacement for server-level WHM or root access, so the exact controls visible depend on your hosting package and provider. This guide is written for production-minded administrators and site owners: make a backup before material changes, keep credentials private, and prefer the controls supplied by your own hosting provider when its environment differs from a generic example.
Before you begin
Record the domain, server or station you are changing and the current working state. If the task touches DNS, SSH, firewall rules, databases, stream credentials or application configuration, make sure you have a recovery path first. Screens and menu names can vary between cPanel, AzuraCast, VDO Panel and Linux releases, so follow the purpose of each step rather than forcing an old screenshot onto a newer version.
Step 1: Open Domains and confirm the primary domain and any addon domains or subdomains. Record which document root belongs to each site before uploading files.
Open Domains and confirm the primary domain and any addon domains or subdomains. Record which document root belongs to each site before uploading files.
Step 2: Open SSL/TLS Status and verify that the public hostnames you use are protected. If AutoSSL is available, let the host-managed process issue certificates rather than uploading random certificate files manually.
Open SSL/TLS Status and verify that the public hostnames you use are protected. If AutoSSL is available, let the host-managed process issue certificates rather than uploading random certificate files manually.
Step 3: Open Email Accounts and confirm only the mailboxes you actually need exist. Use strong passwords, check quota settings, and avoid creating catch-all mailboxes unless there is a clear operational reason.
Open Email Accounts and confirm only the mailboxes you actually need exist. Use strong passwords, check quota settings, and avoid creating catch-all mailboxes unless there is a clear operational reason.
Step 4: Review File Manager, MySQL Databases and MultiPHP Manager so you know where application files, database users and runtime versions are managed. Do not change a live PHP version until the application has been tested.
Review File Manager, MySQL Databases and MultiPHP Manager so you know where application files, database users and runtime versions are managed. Do not change a live PHP version until the application has been tested.
Step 5: Find Backup or Backup Wizard and understand what can be downloaded or restored. A backup you have never tested is not yet a recovery plan.
Find Backup or Backup Wizard and understand what can be downloaded or restored. A backup you have never tested is not yet a recovery plan.
Verification checklist
Before leaving the account, verify HTTPS loads without warnings, the correct website appears on the primary domain, email can send and receive, disk usage is healthy, and you know where current backups are stored. Always test from the user side as well as the administrator side. A control panel saying “active” is useful evidence, but it is not the same as an external browser, player or SSH client proving that the full path works.
Troubleshooting method
When the result is not what you expected, avoid changing several unrelated settings at once. Identify the last known-good point, collect the exact error message and determine which layer is failing: DNS, network, authentication, service process, application configuration, web/stream delivery or browser/player. Check timestamps and logs around the failure. If you need to escalate to hosting support, include the affected hostname or station, the time of the test, what you expected, what happened instead and the checks you already completed. Do not include passwords, API keys or private stream keys in a public ticket or screenshot.
Keep the system maintainable
Document the final configuration after it works. Note the important URLs, service names, backup locations, renewal/expiry dependencies and any change that would surprise another administrator. Revisit the setup after major platform upgrades because defaults, supported runtimes and interface labels evolve. A reliable environment is not one that was configured once; it is one whose current state is understood, monitored and recoverable.
Where to go next
Use the related guides below to expand the setup rather than solving the same problem from scratch. If the platform has outgrown shared hosting or you need managed implementation, the service recommendation at the bottom of this guide links to the most relevant hosting, streaming, development or optimisation option on this site.
Interface labels and supported versions can change. Use the controls and documentation supplied with your current hosting environment, and keep a backup or recovery path before material changes.