Load all possible TLDs into WHMCS supported by eNom.
If you have WHMCS installed and you do not want to go through the painful process of typing all the TLDs one by one and set their pricing by hand, there is a solution.
The Amazon CloudFront wildcard cache invalidation is supported at last.
For a long time this was not available and was a much requested feature, even forcing users to head over to different content delivery network providers. At least for me.
This is great news and will certainly make CDN management via Amazon CloudFront so much easier.
If you have a WHM installation, you may receive several emails (one for each service) from your WHM installation regarding expiring SSL certificates.
The subject of the email may state:
The SSL certificate for cpanel on xxx will expire in less than 30 days
And the message may state something like:
Your server’s SSL certificate for cpanel will expire in less than 30 days. You need to install a new certificate as soon as possible. You can install a new certificate using WHM’s “Manage Service SSL Certificates” interface: https://xxx:2087/scripts2/manageservicecrts (Main >> Service Configuration >> Manage Service SSL Certificates).
The services that use valid SSL or even self-signed certificates include the FTP server, IMAP server (Dovecot by default), SMTP server (Exim by default) and then the cPanel/WHM/Webmail interfaces themselves. So 4 emails in total.
If you are using an actual, valid SSL certificate, you will have to renew it through your SSL certificate provider in order to take care of this.
In most cases though, the SSL certificates are self-signed through cPanel/WHM themselves so you can go to WHM > Service Configuration > Manage SSL certificates and click “Reset Certificate” for each of the 4 services and cPanel will automatically generate a new, self-signed certificate for you.
All set and done!
Setting up Amazon EC2 is quick and easy, you can build a server within less than an hour.
I initially used a great guide posted by Rob Scott which shows how to setup a VPC with security group, an EC2 instance and then how to install WHM on it. I used the guide as reference to my own way of doing it though and it gave me the foundation I needed, especially being unfamiliar with AWS.
The guide tells you how to use Route53 for the DNS which I didn’t follow. I wanted to setup my own, private nameservers. The main reasons were aesthetic (the looks of it in WHOIS) and also so that I could point all my domains to the same two nameservers and never have to change them. If an IP ever had to be swapped out, I could just change the IP at the registrar but the nameservers would remain the same.
Several of my websites were hacked yesterday.
The site would load and display for a moment and then the entire window would show white with the text “By Iskorpitx“. Because the site loaded, I knew that it was something within the core of WordPress itself or a plugin or a theme which has been hacked which causes this.
At last, the migration of my one server to Amazon AWS is done and I’m extremely happy!
The migration took a while as I had to build up momentum and determine what is the quickest and most efficient way of moving accounts over. In the end the quickest way was to package each account into a tarball (tar.gz) which contained all the files, databases, mailboxes and configurations which can then be restored on the new server accordingly.