Hosting
cPanel, WordPress, and Webmail: A Beginner Setup Guide
بواسطة NamePo Editorial Team6 دقيقة قراءةWordPressEmail
مشاركة وAI
وجدت هذا مفيداً؟
شاركه مع فريقك أو اطلب رأياً ثانياً من ChatGPT أو Gemini أو Perplexity أو Claude أو Copilot.
Hosting
وجدت هذا مفيداً؟
شاركه مع فريقك أو اطلب رأياً ثانياً من ChatGPT أو Gemini أو Perplexity أو Claude أو Copilot.
باختصار
ملخص بواسطة NamePo للاستشهاد من محركات البحث والذكاء الاصطناعي.
This is a setup guide, not a sales page. It assumes you already bought (or are about to buy) NamePo shared hosting. The goal is a working WordPress site, a mailbox, and a way to read that mailbox in the browser.
If you wanted a WordPress-only stack without cPanel, stop and read WordPress hosting vs shared hosting first.
Checkout creates an order. Provisioning creates the cPanel user. Those are not the same moment. When the welcome mail or client area shows the hosting service as active, open cPanel from my.namepo.com. If the button is missing, the account is not ready — a ticket is faster than retrying DNS.
Bookmark the cPanel URL from the client area. Do not invent cpanel.yourdomain.com until DNS for that hostname actually points here. A 404 or a certificate warning on a guessed hostname is not a broken server; it is a hostname that does not exist yet.
WordPress and mail both fail in confusing ways if DNS still points at a previous host.
@ (and www if you use it) to the hosting IP shown in cPanel.DNS cache is not instant. Check from more than one resolver before you declare “it does not work”. Lower the TTL a day before a planned cutover if you control the zone.
Nameservers vs records: changing nameservers at the registrar hands the whole zone to NamePo DNS. Changing only an A record at the current DNS host keeps mail and other records where they are. Pick one model. Mixing both is how people lose email for a weekend.
On LiteSpeed/cPanel stacks, AutoSSL or the SSL section issues a certificate once the hostname resolves here. Install WordPress on HTTPS. Mixing http admin cookies and https front-end is a classic first-week bug.
If AutoSSL is pending, wait until the domain resolves to this account. Issuing a certificate for a hostname that still points at the old host will not magically follow you.
Force HTTPS in WordPress (Settings → General, both URLs on https://) after the certificate is valid, not before. A redirect loop usually means the site URL and the certificate do not agree.
Two honest paths:
public_html or a subdirectory.Do not install twice into the same document root. Do not use admin as the username. Save the password in a manager; cPanel password reset will not magically know your wp-admin password.
Then:
If you install into a subdirectory (/blog) by accident, either live with that URL or move the files and update the site URL — do not leave two copies fighting.
In cPanel → Email Accounts:
hello@yourdomain (or a real name).Webmail is Roundcube or a similar client in the browser. Phone apps need IMAP/SMTP settings from the same email page. If you need a full groupware suite (calendar, Drive), that is NamePo professional email / OX — a different product, not “webmail with extra icons”.
Send a test to Gmail or Outlook and read the headers. If it lands in spam, fix SPF/DKIM in cPanel Email Deliverability before you announce the address to customers.
cPanel backups and JetBackup (where enabled) are how you recover from a bad plugin. WordPress core updates are still your job unless you are on managed WordPress. Schedule a mental rule: update plugins on a weekday, not before a launch.
Download one full backup to your laptop once so you know the restore path exists. A backup you have never tried is a rumour.
| Symptom | Usual cause | What to check | | --- | --- | --- | | Site still shows the old host | DNS not cut over or cached | Nameservers at registrar; A record IP | | wp-admin redirect loop | Site URL http vs https | General settings + SSL issued | | Mail sends, never arrives | MX still at old host | MX lookup; Email Deliverability | | “This site can’t be reached” | Account not provisioned or wrong hostname | Client area service status | | White screen after install | Plugin/theme fatal | Disable plugins via File Manager |
File Manager is not a toy. You will use it to drop a maintenance.html, to delete a rogue plugin folder, and to confirm wp-config.php is in the document root you think it is.
| Step | Done when | | --- | --- | | Service active | cPanel opens from the client area | | DNS | Site hostname resolves to this account | | TLS | Browser padlock on the site URL | | WordPress | wp-admin login works | | Mail | Webmail sends and receives a test to an external inbox |
That is the beginner path. Everything else — SEO, WooCommerce, object cache — is optional until this table is green.