Set Up a New Hosting Site in cPanel or Plesk
Start with the right account details
To set up a new hosting site in cPanel or Plesk, start with the details you received after purchase: server address, control panel login, primary domain, and nameserver values. If you are moving from another host, keep the old DNS active until the new site is ready. That gives you room to test before visitors hit the new server.
If you are still comparing plans, Hostperl’s VPS hosting makes more sense once you need isolated resources, finer PHP control, or heavier email and database workloads. For smaller brochure sites, shared hosting is still the quickest way to get online.
- Panel URL: usually
https://your-server-name:2083for cPanel orhttps://your-server-name:8443for Plesk - Main domain: the site you want to host first
- DNS access: where you manage nameservers and records
- SSL plan: Let’s Encrypt or a paid certificate
Set up a new hosting site in cPanel or Plesk
In cPanel, you usually create an account or addon domain first, then check that the document root points to the right folder. In Plesk, add the domain under Websites & Domains and confirm the hosting type is set correctly. Both panels can look ready before the important settings are actually in place, so verify the path before you upload files.
For a clean launch, use a simple checklist:
- Add the domain in the panel.
- Set the document root for the site.
- Confirm the PHP version your app expects.
- Create the database and database user if the site needs one.
- Upload the site files or restore the backup.
If the site is a WordPress build, Hostperl’s shared hosting plans are a practical fit for many small sites because email, SSL, and panel access are already set up for first-time launches.
Point DNS only after the site responds correctly
DNS changes should be the last visible step, not the first. Before you switch nameservers, use the server preview link or hosts-file testing to check the site on the new server. That helps you catch missing images, bad redirects, or a database connection error before visitors see them.
For migrations, Hostperl’s guide on moving a website between hosting panels is useful if your old site already lives in cPanel, Plesk, or DirectAdmin. If you want to test the move before a public switch, follow how to test a hosting migration before you switch first. It saves support time later.
Update these records carefully:
Arecord for the root domainAAAArecord only if your server and network actually use IPv6CNAMEforwwwif you prefer that setupMXrecords if email stays on the same host
Install SSL before you announce the site
Browsers still punish half-finished launches. If your site loads over HTTP first, users see warning screens and password forms can be exposed unnecessarily. Turn on SSL before you send traffic to the new domain.
In cPanel, open SSL/TLS Status and issue a certificate for the domain and www. In Plesk, use the built-in Let’s Encrypt extension or install the certificate under Hosting Settings. After installation, check that the site redirects to HTTPS and that there is only one canonical version of the domain.
Use this quick test from a browser and a terminal:
curl -I https://yourdomain.com
curl -I http://yourdomain.comThe first command should return a normal 200, 301, or 302 response. The second should redirect to HTTPS, not stay on plain HTTP.
Configure email so your first messages do not vanish
New hosting customers often assume email works automatically as soon as the mailbox exists. It does not. You still need SPF, DKIM, and the right MX record in place. Without them, Outlook and Gmail may send your messages to spam or reject them outright.
For a practical setup, follow Hostperl’s email deliverability guide for shared plans. If your account sits on cPanel, the related cPanel email deliverability fix walks through the same essentials from a support angle.
Check these items before you send your first invoice or welcome email:
- Mailbox created for the correct domain
- SPF record includes your mail server
- DKIM is enabled in the panel
- MX points to the host that sends mail
- Reverse DNS matches the sending server if you use a VPS or dedicated server
Restore files and database without breaking the site
If you are launching from a backup, upload the site files first, then import the database. That order keeps the application structure intact and makes troubleshooting easier. WordPress, Joomla, and most PHP apps expect their files and database to agree on table prefixes, site URLs, and user credentials.
After import, edit the configuration file for your app. In WordPress that means wp-config.php. On other systems, it may be .env, config.php, or a control-panel field. If the site loads but shows a database error, check the host, username, password, and database name before you look anywhere else.
For a cleaner migration path, see how to move hosting sites without downtime. It covers the handoff between old and new servers in a way that matches real support work.
Choose the right panel settings for the site type
cPanel and Plesk both do the job, but they do not feel the same in daily use. cPanel is familiar to many shared hosting customers and resellers. Plesk often feels cleaner for multi-site management and mixed stacks. If you are deciding before setup, Hostperl’s comparison cPanel vs Plesk vs DirectAdmin for hosting buyers is worth a read.
Choose based on the work you need to do:
- One WordPress site with email: shared hosting and a simple panel are enough
- Several client sites: Plesk or cPanel on a VPS is easier to manage
- Heavier traffic or custom server tuning: move to VPS or dedicated hosting
If your account is already outgrowing shared hosting, Hostperl’s shared-to-VPS migration guide explains the next step without turning it into a rebuild project.
Run a final launch check
Before you announce the site, open the homepage, login page, contact form, and one internal page. Then send a test email from the domain to a Gmail or Outlook account. That catches the most common launch problems: missing CSS, mixed-content warnings, broken forms, and mail that lands in junk.
Use this short checklist:
- HTTPS works on both root and
www - The site shows the expected content on mobile and desktop
- Email sends and receives from the new domain
- DNS points to the new server
- Backups are enabled before traffic grows
At this stage, you should also confirm the restore point. If the host offers backups, know where they live and how to request a restore. That matters the first time a plugin update breaks a live site at 9 a.m.
If you want help setting up a new site cleanly, Hostperl can handle the practical parts that usually slow launches down: account setup, panel checks, DNS, SSL, and email alignment. For sites that need more room to grow, start with managed VPS hosting or move a launch site onto shared hosting for a simpler start.
FAQ
Should I set up the site in cPanel or Plesk first?
Use the panel your host already provides. If you are choosing new hosting, pick the one that fits your workflow and support needs, not the one with the longest feature list.
Do I need SSL before changing DNS?
Yes. Install SSL first, confirm the site loads over HTTPS, then point DNS. That avoids browser warnings during the switch.
Why does the site show a database error after migration?
Usually the database name, username, password, or host value is wrong in the app config. Recheck those fields before changing anything else.
Can I keep email on the old host while the website moves?
Yes, as long as MX records stay pointed at the old mail server until you are ready to move mail too. That is often the safest path for business accounts.
When should I move from shared hosting to VPS?
Move when you need more control, more consistent performance, or multiple sites that are starting to feel cramped on a shared plan.
