cPanel vs. HAProxy Community Edition vs. NGINX

I personally use it for any website hosting I do for me and others. There are a few others but I have stuck with the old tried and true and it always works for me and I know how to get around it so it has become a breeze for me. For those who are extremely new to websites and hosting or to those with very little technical know how cPanel could be very overwhelming and they might want to do like a managed WordPress hosting where they don't really have to see or deal with cPanel. I also probably wouldn't use it for straight email hosting. If you have thousands of cPanel accounts it may get very expensive and that could be a factor.

Incentivized

It prevents a single server failure from being a downtime event by adding redundancy to every layer of your architecture. A load balancer facilitates redundancy for the backend layer (web/app servers), but for a true high availability setup, you need to have redundant load balancers as well. So it is well suited for all production related servers and less suited for individual servers that do not require redundancy.

Incentivized

Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.

Incentivized

• The dashboard is very intuitive. Even beginners can figure out how to do things without very much help.
• The online community is very helpful and the online documentation makes administering any tasks a lot easier.
• User creation and administration for FTP access is also very simple.

• Low-Cost Load Balancer
• Intelligent Request Routing based on URL and/or URI
• Extremely flexible load balancing and healthchecks, can do almost anything including HTTP, HTTPS, PostgreSQL, etc.
• SSL Termination

Incentivized

• Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
• Great at serving static content.
• Scales very well. Easy to host multiple Nginx servers to promote high availability.
• Open-Source (no cost)!

Incentivized

• The costs can be a limiting factor for some businesses if you are not using a web hosting company that uses it. I have been experimenting with Cloud hosting, which can be very daunting for the novice. There is an option to install it on the cloud but it is expensive.

Incentivized

• A few, rare times each year, HAProxy CPU utilization spikes to 100% and server has to be rebooted - this may be related to HAProxy OR it could be an external factor causing this.

Incentivized

• Customer support can be strangely condescending, perhaps it's a language issue?
• I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
• It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
• It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
• I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.

Great value for the product

Incentivized

Although it can be a little bit bloated with a lot of options and configurations, it's very straightforward to use and maintain. So it's a great option even if you don't have large experience in hosting configuration. The WHM tool is more suited to heavy users since it requires more expertise, so it has a steep learning curve to better understand how to use it.

Incentivized

It is very easy to use. I was able to find a lot of documents for it on the internet. Very good community support. There are lots of examples available to try. We mostly use a command-line user interface to interact with it. The CLI is also super easy to use and very easy to interact with

Incentivized

This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers

Incentivized

The support comes in the form of an extensive library of how to articles and community input. For most situations this will give you plenty of information and resources to trouble shoot. Live support really then would need to default to the hosting provider who provides the cPanel for your use.

Incentivized

We haven't used customer support. We mostly used the community version. We build a multi-node HAProxy cluster with HA to the proxy itself using opensource plugins available. With the support available on the internet and the documents available we don't need to use much customer support.

Incentivized

Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.

Incentivized

The direct server management tool access provided by cPanel hosting accounts is far superior to any shared or "standard" web site hosting packaged offered by any of the numerous web host providers I have used and or evaluated over the 20+ years of my experience working in the internet industry.

Incentivized

We chose HA Proxy because it is cheaper than a hardware balancer, it is an open-source solution with a large community behind it and with constant updates. It also allows custom scripts according to needs.HA Proxy is a solution used in many internet sites like GitHub, Reddit, Twitter, and Tuenti.

Incentivized

I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives

Incentivized

• cPanel makes back end server administration easy. This saves time and overall effort.
• cPanel is readily available with most hosting packages. It integrates with both Apache and Nginx.
• cPanel allows you to perform some of the same functions as WHM, but with an easier interface.

Incentivized

• Significantly lower investment vs competitors. In the case of F5s we have Virtual Editions so we're paying for the hardware to run it on top of the several thousand dollar licenses that are required for each pair and we currently have a pair of F5s per client so there's a huge potential for cost savings there.
• Requires our network engineers to learn a new skill or our Systems engineers to take on the responsibility of managing the load balancers. It's not a huge difference either way, but it does impact the way we have done business in the past.

Incentivized

• By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
• Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
• Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.

Incentivized