cPanel configure Apache to work the most stable way. However, with a few tricks, the default settings can be improved to gain performance and have a better resource usage.
I never allow users to connect directly to the clouds, since clouds from great providers like AWS or Google, doesn’t come with DDoS Protection. So, I have to build a protection.
Sometime ago I read a decent review about “DDoS Protected VPS Providers” on LowEndTalk (really, on LET):
It’s indeed very accurate based on my experiences so far. Today I trust 3 providers for my SSH/SFTP/MySQL tunnels: LunaNode from Montreal (OVH), RamNode from Atlanta (Staminus) and QuadraNet from Miami (In-House).
Everytime I had to setup a VPN, I used to do manually, with guides like these:
To make it easier, I was going to create a shell script like any sysadmin. However, before I did any movement, I went to Google to find if there is already an existing script.
Recently I had a problem with a customer trying to remove a addon domain on cPanel. Every time he tries to remove, he got different error messages, like “subdomain ‘shop.example.com’ does not exist for user ‘client’”.
Since cPanel couldn’t do it by itself, I went to the documentation to find where the user configurations are located. According to the documentation, the files are store in /var/cpanel.
Since the update 11.58, I noticed that cPanel NAT solution wasn’t working with Apache on Amazon Web Services and Google Cloud Engine.
Apache was putting the public IP on the VirtualHost. Bad bad boy.
As far as I’m concerned, you don’t want to change the public IP to the internal IP every time some httpd.conf edition is made.