Start With the Affected Account
Record the username, domain, exact error and time. Compare a healthy account before restarting Apache, Exim, DNS or database services for everyone.
Practical cPanel and WHM troubleshooting for resellers, agencies and IT teams across Bangladesh — account errors, mail that will not deliver, DNS, backups, PHP versions, quotas, dead services and client migrations.
Give us the server hostname, the cPanel or WHM version, the exact error, which account or service it hits, the time in BST, anything that changed recently, and any log output you can share with sensitive lines removed.
The same symptom can come from a user quota, a package limit, a DNS record or a server-wide service. Defining the impact boundary prevents an account problem from turning into unnecessary platform changes.
Record the username, domain, exact error and time. Compare a healthy account before restarting Apache, Exim, DNS or database services for everyone.
WHM reports are useful, but Linux logs, resource pressure and service state usually explain why a panel action failed or remained pending.
Before a repair, confirm account backups, configuration copies and the rollback for any package, PHP, DNS or mail change that may affect client sites.
cPanel and WHM hold your websites, DNS, mail, databases, SSL, users, packages, quotas, backups and service settings in one place. When you host other people's businesses, we work out exactly how far a change reaches before restarting anything.
First we establish whether the fault hits one domain, one cPanel user, a reseller under you, a single service, or every account on the box.
Whatever WHM reports gets checked against system, web, mail, DNS, SSL, database, backup and security evidence on the server itself.
Service restarts, package edits, DNS changes and firewall actions are weighed against the clients who did not report a problem.
Home directories, databases, mailboxes, DNS zones, SSL state, packages and ownership are all accounted for during a fix or a transfer.
The last check is the actual website, mailbox, SSL, login or scheduled job — not a green tick on a WHM status page.
The control panel is a useful window into the server, but when the interface cannot explain a failure we go straight to the Linux service sitting underneath it.
Sort out lifecycle and boundary problems around cPanel users, resellers under you, packages, quotas and filesystem access.
Get to the bottom of website and runtime failures involving panel-managed services and per-account settings.
Follow mail and trust problems through Exim, DNS zones, authentication records, certificate validation and network policy.
Check data movement and automated jobs properly, instead of assuming a job that finished produced something you can restore.
Service health, update posture, hostname and DNS, SSL, mail reputation signals, backups, resource pressure, firewall behaviour and account isolation can all be reviewed together and returned as a prioritised technical plan.
We fix the boundary first, match WHM output against evidence from the server, weigh the effect on neighbouring accounts, then verify the real service once the approved repair is in.
Which cPanel or WHM function breaks, for which account, and what the screen says. A screenshot of the actual error saves far more time than a summary of it.
We work out whether this lives in the account, the service or the server, agree what WHM access is needed, and keep every unrelated client account out of it.
Exim, Apache and cPanel error logs, service status, quotas, PHP handlers and AutoSSL output — read and reproduced before any config file is edited.
You get the cause — an EasyApache profile, a PHP-FPM pool, a DNS zone, mail routing or permissions — along with the repair, how far it reaches, and a quote where one applies.
After your approval we make the change, restart only the service involved, and confirm the function works for the account that raised it in the first place.
Clear approval boundary. Investigation and repair are separated where applicable. Broader changes, added scope, and material risk are explained before you authorise the work.
Start a scoped requestWHM reported domain-control validation failure for one account, over and over, while every other certificate on the server renewed without trouble.
dnsA record reaches target server
dcvchallenge path returned redirect
scopesingle cPanel account
findingrewrite rule captured validation path
repairexclude DCV path
verifycertificate issued and served
Take focused troubleshooting for one defined account or service problem, or ask for a wider review of how your cPanel server runs and where its risks sit.
For one account, website, mailbox, DNS, SSL, backup, transfer or service error.
Best forFor hosting servers that need a clear, prioritised plan for stability, security and recoverability.
Best forcPanel is a layer on top of a Linux server, and a good share of the faults you meet actually start in the services below it. We work at both levels, and we understand what changes at account, reseller and server scope really mean when clients are depending on you.
What we can do depends on your licence status, cPanel version, operating system support, third-party plugins, root access, provider restrictions and the backups available. Hostaccent is not an official cPanel partner and does not claim to be.
A cPanel symptom rarely stays inside cPanel: one failed AutoSSL renewal can involve a DNS record, the Exim queue, a firewall rule, or an EasyApache profile that got rebuilt during an update. Explore every specialist service without losing the wider production context.
These answers explain how the investigation works before you share access or approve a production change.
Ask about your environmentYes. We can review nameservers, DNS zones, A and CNAME records, MX and TXT records, propagation, and DNSSEC or CAA issues where the provider exposes the required controls. The domain can remain with its current registrar while we configure and verify the records.
Yes. Reseller support is a large part of what we do for Bangladeshi customers — account creation and limits, package configuration, email deliverability for your clients, backups, and the migrations that come with taking on a new client.
No. This is a paid technical service and the cPanel or WHM server can belong to any provider, or be your own. We work on the server you point us at, with the access level agreed in advance. If the underlying platform or licence turns out to be the constraint, we will explain that in the findings rather than pushing you to move.
Yes. We look at reseller limits and ownership, the package and its feature list, the username, DNS, the state of the filesystem, quotas, the licence, whatever the API returned, and any service error sitting behind the failure.
With credentials and account state, then the port, firewall rules, service health, the hostname and its certificate, any authentication restrictions in place, browser behaviour, and finally provider-level access. We may need you to prove ownership of the server first.
Yes. We check DNS, the domain-control validation path, redirects, proxy behaviour, web-server routing, CAA records, the certificate logs, hostname state and the virtual host in question — and only then run issuance again.
Yes. We look at routing, the queue itself, authentication, DNS alignment, reputation signals for the server, rate limits, filters, what the receiving provider replied, firewall policy and mailbox behaviour. Nobody can promise inbox placement, but the technical side can be made correct.
Yes. Installed packages, handlers, per-domain PHP versions, extensions, pools, memory and worker limits, how configuration inherits, web-server integration and whether the application actually supports the version you want — all of it is in scope.
Yes. Before we agree the scope we check source and destination compatibility, account data, databases, DNS, email, SSL, packages, anything tied to a specific IP, the transfer tooling, the cutover plan and how testing happens afterwards.
Yes. Schedules, destinations, authentication, storage capacity, retention, transport logs, archive integrity, permissions and restore behaviour all get inspected. A backup that appears in a list is not treated as usable until it has actually been validated.
Yes. Panel access, packages, server groups, API credentials, module logs, and account creation, suspension and termination can all be looked at here. Wider billing and automation faults belong with our WHMCS Technical Support service instead.
Some account-level issues need nothing more than cPanel access. Anything server-wide normally needs authorised WHM or SSH access. We explain why each level is necessary and suggest temporary credentials wherever that is practical.
Yes. We support authorised, compatible cPanel and WHM servers at third-party providers. Licence status, the network, the virtualisation layer, provider policy or missing root access can limit which changes we are able to make.
Send the exact symptom, the accounts affected, the time it started and anything that changed. We will establish whether it is account-level or server-wide before proposing any work.