Hosting Provider cPanel & AWS Complaints & Reviews

This is a long article…

Please keep in mind the intention is to extract issues some businesses may have, rather than negate the proper use of cPanel.

This article presents a ChatGPT discovery of complaints for both cPanel and Amazon AWS Linux services.

Research from ChatGPT 10/10/2025 – modified slightly for public publishing here. “Eg” examples have company names removed. Please keep in mind there will always be complaints and reviews, and some companies may offer a higher level of trust. The aim is to show some expressed views.

“Here are some of the major complaints, common pain points, and issues businesses and users have reported (forums, review sites, Reddit etc.) about Australian web‑hosting providers and companies using cPanel, or issues with cPanel hosts more broadly.”

Major Complaint Themes

Here are recurring complaints, grouped by type, with examples, with examples sites from ProducReview.com.au, ComplaintsBoard.com, WebHostingDownUnder.com.au, and Reddit.

Please note: I have clients using cPanel, and recommend VentraIP Australia for hosting in Australia. They have great support.

While this is balancing towards the negative side, the comments are realistic. For example, support call can be pleasant, but then we find this may not be so for serious issues and harder questions. Support can be delayed. Many support systems wish to give people a good feeling, which also makes it more difficult for negative feedback when things are not right. Often support calls are very simplistic giving an apparent illusion of having good support. If a company employs more highly skilled support staff who the public does not usually interact with, we can see some amazing things happen, but even so, it can still be give and take with our own manual IT skills to fix a real problem.

cPanel is generally seen as good for small websites, an entry level system, single click and install, small or simple tasks, cheap email, no scaling or other serious business concerns that require a non-cPanel service or where costs begin to escalate as a requirement to continue.

Several real‑life examples from Australian forums, complaints sites etc where businesses or individuals claim they lost revenue, clients, or reputation due to hosting / cPanel / provider‑related failures. These are useful to see what kinds of risks people have actually run into. In many cases the data are anecdotal, not independently audited, so please interpret with caution, however,  they illustrate common failure modes.

Note: There have been numerous forum entries in previous several years not shown up in these more recent searches.

---

Lessons & Common Patterns from These Examples

From the above, some frequent themes emerge:

1. Downtime kills bookings / sales quickly
   Especially for businesses relying on online bookings / transactions, even short (hours or a few days) outages lead to direct lost income (missed orders, missed bookings) and damage to customer trust (so longer‑term loss).

2. SEO / marketing investments are fragile
   Time and money invested in search ranking / ads can be undermined by site instability or downtime. If your site goes down, or content disappears, or pages return error codes, rankings drop; getting back those rankings is often not easy or cheap.

3. Data loss is very painful
   When backups are incomplete / restore is delayed / server migration fails, businesses can lose content, emails, customer records etc. That loss can lead to both direct revenue loss and indirect costs (rebuilding, customer service, reputation, refunds etc.).

4. Support failure compounds damage
   Users often complain that support delays, unclear communication, or ineffective fixes make the downtime / data loss worse. The cost isn’t just in the technical failure but in the time spent chasing resolution, trying to recover, etc.

5. Hidden costs, pricing / licensing changes matter
   Providers increasing costs (e.g. cPanel licensing) without commensurate increases in service can force businesses either to raise prices (losing customers) or eat the cost (eroding margins). Sometimes these changes tip small/reseller hosts into unsustainable positions.

6. Promises vs reality
   Promised uptime, SLAs, “unlimited” features, backup guarantees etc often show cracks in real‑life scenarios. Users regularly say the provider’s marketing / documentation didn’t match what they actually experienced.

---

Australian law (consumer protection law) can impose penalties when hosting/domain companies mislead customers. For example “Subscription Trap” and “Misleading Checkout Practices”.

Certain public claims of sites taken offline or content loss – no formal legal cases. Businesses and individuals may settle privately, out of court.

To win in legal proceedings, one must show that the provider breached contract or consumer law, that the breach caused the loss, and quantify the loss (with invoices, metrics, etc.). This often requires good documentation, which many small businesses don’t have or aren’t willing to disclose publicly, or other reasons.

If complaints are resolved under confidentiality or arbitration, they don’t enter the public record.

A Comparison to AWS Linux – ChatGPT

A number of issues provided by ChatGPT are unique and few to specific client experiences, not common or relevant across our “non-complex” services, and would generally apply to any service such as overuse of CPU and RAM.

Developers may build on an intentional learning curve to offer what their competitors do not.

A number of issues are simply from limited Unix/Linux experience or not applicable at all.

All hardware and software has a cycle of “burn-in”, life-time use, and sunset. WordPress sites that remain stale on cPanel platforms have presented difficulties when never updated.

Amazon AWS has an internal schedule for updating to new hardware architectures and software releases, supporting previous systems for several years.

Amazon AWS developers provide support to their clients. cPanel services typically provide feel-good or minimal support as people come up to speed on the cPanel interface. Clients on AWS may review their account page, and log into WordPress as normal.

Advantage Web intends to help a developer with a learning curve, and has documented a full array of the necessary AWS services used with WordPress, along with scripts for supporting automated backups and checks.

The following content is provided for fairness in comparison to the ChatGPT summaries on cPanel. There are no real concerns for a client. The dynamics of a Linux on-demand service are however different at first to a cPanel experience.

ChatGPT 15^th October 2025:

Here’s a summary of common complaints, pain points, and issues that businesses and users report (on Reddit, review sites, forums etc.) when using Amazon EC2 on Linux for hosting websites. Some are due to misunderstandings or configuration mistakes; others are inherent trade‑offs.

Major and Frequent Issues

1. Cost & Pricing Surprises (n/a)

• Various users say EC2 can get expensive if not monitored closely. It’s easy to unintentionally rack up costs due to unused instances, data transfer, storage I/O, etc.

Refer https://www.capterra.com/p/219781/EC2/reviews/

Mitigation: only use required services and use a budget alert. No Advantage Web clients have experienced “bill shock”. Close monitoring is not required.

• Region cost variability: same instance type / storage in different AWS regions often has different pricing. Users sometimes mis‑estimate this.

Mitigation: Not applicable.

• Free / low tier instances often have severe limits (CPU, network, bursting capacity). Some users say that free trials or low‑cost instances are “very basic and slow” and insufficient for even moderately demanding sites.

Mitigation: Not applicable. Free 12 month instances on older hardware are not used. Small Business works well on t3a x_86 or t4 ARM micro or small.

2. Complexity of Setup & Learning Curve (n/a to end users)

• AWS has a lot of moving parts. To properly host a website, you need to understand EC2, VPC, security groups, IAM roles, load balancers, etc. Many users find this overwhelming if they only need a simple web server.

Mitigation: This is why Advantage Web provides these services.

• Documentation is good overall but sometimes misleading, out‑of‑date, or assumes prior AWS knowledge. Some reviews mention having to decipher AWS terminology and navigation in the console.

Mitigation: Advantage Web has documented required services for developers and is able to assist a developer come up to speed with an in-house Linux person. I am not aware of anyone’s documentation remaining up-to-date across the board or not having issues. This is why we have problem solving skills.

3. Performance & Resource Issues (n/a)

• Burst‑type instances (like t2, t3) have CPU credit models. When CPU credits are exhausted, performance drops suddenly. Users on Reddit have reported instances being fine for a while then slowing / becoming unreachable. Reddit

Mitigation: Use correct sizing. Not known as anyone’s experience on Advantage Web sites. The use of CPU credit is not meant to be regular use. Unlimited CPU access for these peak loads is possible but can present “bill shock”.

• Memory leaks or resource saturation: some sites crash or become unreachable after running for a while, often because something (web server, application, or container) is consuming memory or hitting some limit. CloudWatch CPU metrics may look “okay” even while memory is being eaten up. Reddit+1

Mitigation: Not a known issue on WordPress sites. Memory leaks should be traced using error logs, journalctl, and dmesg as a starting place, and reasonable use of php and mysql configurations.

4. Reliability / Instance Health & Downtime (n/a)

• Instance status check failures: sometimes EC2 instances fail one of AWS’s health / system / instance status checks. This can lead to the instance becoming unreachable, even though everything appeared configured properly. Reddit+2Repost+2

Mitigation: This is an abnormal configuration. An Alert can be configured for a failure if really needed.

• Instances going “down” temporarily (network unreachable, SSH inaccessible) for reasons that aren’t always obvious (network / AWS underlying host, instance health, bursting limits, etc.) Reddit+2Reddit+2

Mitigation: Advantage Web has not come across this specific user help request, but has extensive problem-solving skills as proven in the workforce. In general, it is best to build a new instance from scratch. If hardware is not faulty, the issue is with overloading or the particular web app used. Such problems would show up on any platform.

5. Networking, Security & Configuration Pitfalls (n/a)

• Misconfigured security groups / firewall rules / network ACLs are a frequent cause of sites being inaccessible. Open ports, inbound/outbound rules, VPC/subnet routing errors, etc. Stack Overflow+2configzen.com+2

Mitigation: Security rules are very straight forward. It is a matter of having experience with Amazon.

• SSH / key‑pair / IAM issues: wrong permissions, losing access, worrying about root vs user access. forwardmotiontx.com+2Reddit+2

Mitigation: These are basic Linux (or Unix) configurations, and are set up automatically by Amazon. We also create a second emergency user login for access from the serial console in Amazon, and have system backups.

• DNS / IP issues: public IP changes when stopping & starting instances (unless using elastic IP), which can cause loss of connectivity, broken DNS, etc. Capterra+2Reddit+2

Mitigation: An assigned IP4 static IP address (which we use from EC2/ElasticIP) remains constant, always.

6. Monitoring, Logging & Diagnostics (n/a)

• Basic monitoring (e.g. memory usage) isn’t always enabled by default. Some users only see CPU or network, but can’t track when processes are leaking memory or swapping heavily. Reddit+1
• Logs are sometimes difficult to trace through, or logs may be lost after instance crashes (if not stored/rotated properly). Reddit

Mitigation: This depends on one’s Unix or Linux experience. WordPress should not be leaking memory. We are able to reload RAM and SWAP DISK without interrupting transactions or visitors, and have various scripts to monitor or add for specific situations.

7. Scaling & Maintenance Pain (n/a)

• Scaling out for high traffic requires architectural work (load balancers, auto‑scaling groups, stateless apps) not just throwing more power at a single EC2 instance. Some users expect EC2 by itself to handle traffic spikes simply. G2+1

Mitigation: This is not an issue for small business, tradies, and individuals. If load balancing is required, this is a much larger and higher costed architecture. If RAM and CPU are overused, the monitoring stats will show it, meaning the next tier up is needed. These are not major costs for a business. If complex architectures are needed, this is not the fault of the AWS services, and would require expensive development from various high-level developers in Australia.

• Maintenance overhead: patching OS, handling backups, ensuring security updates, managing disk I/O and storage growth. Users hosting websites often expect “just upload and go”, but with EC2 you’re responsible for much of the stack. Capterra+1

Mitigation: True. We build scripts to automate maintenance and WordPress backups, or log in manually to do the same. As WordPress is its own application, users can log in to WordPress the same as any other hosting platform with https://mydomain.com/wp-admin etc. Any provider offering a VPS is the same, but some provide a management interface. If using Linux, one should know how to do everything by command line anyway.

8. User Interface / Usability Frustrations (n/a)

• Some reviews complain that searching for AMIs, instance types, or just navigating all the many options in AWS console is clunky or unintuitive. Capterra
• Lack of transparency about usage metrics (how much you’re being charged for what) is a recurring gripe. It can be hard to estimate total monthly cost especially on complex deployments. Capterra+1

Mitigation: With AWS experience these are not issues. Navigation is readily learnt. Billing is not a concern on the types of “non-complex” systems we are building, and is listed with line items in the account’s billing section. On-Demand pricing is a little strange at first, but has shown no issues long-term for any clients.

Issues Raised by Reddit / Real‑User Stories (Examples)

Here are a few concrete stories / complaints that illustrate the above:

• “Website goes unreachable several times a day; SSH inaccessible; metrics look normal.” A Reddit user reported frequent downtimes with no obvious CPU / memory spikes. Suggests network issues, maybe host health or underlying AWS infrastructure issues. Reddit

Mitigation: Technology can have unexpected issues, which is why we have problem solving skills. Nothing should be going down each day. If there are hardware failures, the raw boot up logs may show the problem. One can quickly rebuild from a snapshot onto another slice of hardware. Hardware can have failures that are not logged – that is the nature of it. Most failures are indicated. AWS has proprietary systems with built in redundancies. This does not mean a network interface cannot suddenly blow up on anyone’s service. This Reddit issue is not normal and means there is a definite problem to resolve.

Underlying Causes

Many of these pains stem from:

• Using the wrong instance type (too small, burst‑type when sustained performance needed)
• Not configuring for reliability (no monitoring, no health checks, no auto‑recovery)
• Lack of familiarity with AWS concepts (security groups, VPCs, IAM, networking)
• Overlooking limits or trade‑offs (e.g. public IP changes, burst limits, instance storage IOPS vs network speed)
• Infrequent maintenance or updating

Mitigation: These are common sense issues a developer should not be grappling with or pose any concern to a client.

 

Here are some Best Practices for using Amazon AWS Linux

• Choose the right size of Instance Type.
• Check the IP4 address is not blacklisted.
• Choose x_86 or ARM architecture, always with GP3 hard disk and swap space settings.
• Understand both the EC2 monitoring tools and Linux OS tools.
• A developer to build their expertise over time and have problem solving skills.
• The developer to choose the appropriate AWS Services – Advantage Web supplies these in documentation. This keeps us in scope and have correct pricing available at low costs for many who are currently not able to find developers with these AWS skills.
• Understand best practice memory configurations for PHP, PHP-FPM, MYSQL (mariadb), SWAP SPACE.
• Implement modified Nginx configurations for increased security.
• Implement correct use of open ports, and iptables for added protections.
• Develop or use existing SHELL SCRIPTS for automated maintenance and email warnings via postfix, such as a server running or not.
• Understand default monitoring tools.
• Understand how to detect and fix any hardware failures or suspicious behaviour at installation.
• This implies full disaster recovery capability and ongoing backups.
• Complex systems such as load balancing and high availability may be handled by larger developer businesses in Australia, or be developed via test systems in order to add to one’s portfolio.
• Awareness of redundancy configurations for S3 object storage, such as via the sync command, or use of EFS.
• Where live transaction data recovery is vital, needing more than one primary database, this is a higher-level service not addressed in this offering, but not necessarily out of scope. If this is further developed it will be added to the docs.advantageweb.au documentation.
• EC2 gives full control of the “stack”.
• You are responsible for a coverage of items as shown by this website and AWeb’s documentation.