CloudLinux with cPanel 11.50.0.29 (PV)
Cloud Linux | 6.8Linux/Unix, CentOS 2016.09.29 - 64-bit Amazon Machine Image (AMI)
The best for hosting provider
I tried Cloudlinux with cpanel and the product is excelent, very stable and easy to use, configuration is intuitive and easy, is a powerfull tool for create a web hosting provider instance.
- Leave a Comment |
- Mark review as helpful
not very useful.
you can not do the upgrade of cPanel because it has all the installed rpm and missing several scripts. There are many mistakes.
I've finished the instance and continue 'to use the classic Centos until there is a satisfactory version of CloudLinux for cPanel, so you can not use it in production.
Great, but here are some tips to getting it working
Warning: This is an image for cPanel DEDICATED servers. In other words it's ~$425 per year not $150 like the VPS licenses. I'm not sure that a VPS licence would work because they appear to be designed for Xen and other hypervisors (not AWS). But hey, prove me wrong and save some money!
NAT: Setup a VPC because you will likely want more than one IP and it will be a mission to rectify this after the fact. When installing just let it detect the NATted IP's and fix it later.
And by fix it, I mean upgrade to at least 11.39 because it then has NAT functionality without having to do a bunch of weird hackery in the background. When you run the build_cpnat script (or do it through the actual cPanel interface) it will bind local IP's to external IP's
Addendum: due to the marketplace image protection mechanism, it is impossible to mount your cPanel image as a secondary volume to another instance for the purpose of data recovery or simply chnaging a conf file!! My strong suggestion is to only make a 10-15gb ami in the first place and mount a second bigger volume as your /home directory. In the event of a server crash, you can restore from a snapshot of the sda1 device and just remount the secondary. Also, be sure to use an init script rather than fstab to mount the secondary drive. If, forwhatever, reason the volume is unmountable/damaged and it is configured to mount via fstab, then the whole instance will fail to boot. Use an init script!