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 version 4.4, WordPress has a native responsive image support by including srcset and sizes attributes to the image markups. It’s a good function, no doubts.
However, it can cause problems which you are probably have, if you are reading this.
In my case, I convert my blog from a local WordPress installation using HTTrack. As for today, HTTrack can’t recognize those attributes, then, some images weren’t being showing for my readers.