General Information


CloudLinux – A better way to host

CloudLinuxIf you are like millions of other website owners, you probably started out on shared hosting. You’ve been through the ups and the downs that are associated with small budget hosting. Your website was thrown onto a server with a thousand other websites, all doing different things. Websites may be hacked and infected, they may have adult content, they could be spammers, they could be designed to infect visitors with malware, or it could just be an honest person trying to make a living… the truth is, no one ever knows who their neighbor is, not even the hosting companies. All it takes is one bad apple to spoil the bunch, or in this case, one bad website to take down an entire server. Enter CloudLinux!
 

One of the biggest benefits of CloudLinux is that it takes your website and puts it in its own container via a component called CageFS. In short, this means that the security of a site on the same server cannot affect the security of another, nor can it affect the server as a whole. Let’s think of the apples again except this time, each apple is inside of a sealed container. If one apple goes bad, it no longer affects all the other apples. The same is true with sites on CloudLinux. If a site is hacked or infected, it no longer has the potential to impact it’s neighboring sites. This results in a much happier environment for our sites. The Operating System kernel has been hardened and security patches are released a lot more often. Combined with KernelCare, security patches are applied instantly without having to wait for reboots.
 

The CloudLinux operating system enables the ability to set limits based upon the package that the site is on. The limits include CPU, memory, disk performance, and running processes. These limits are not put in place to punish a website owner for having a busy site, they are there to make sure every site is using the resources their package was designed for and to protect the servers from being overloaded. These limits also help us to identify issues with sites very quickly because we monitor and get alerts any time a site hits their resource limits. Maybe the site is missing a cache plugin, has uncompressed images, has 500+ request per page load, or maybe it has a bad script that’s running for 20 seconds, or is stuck in an infinite loop. Once these issues are fixed, the site loads faster and the owner is a much happier customer. Because these limits are set per website, and the site is in its own container, a website maxing out its resources cannot affect another website, nor can it affect the performance of the server. Let’s look at a typical scenario: Site X uses up all available resources on a shared hosting server. Either the server crashes or all sites are running slow or are inaccessible. On one of our servers, Site X is using up all available resources for their account. The website is running slow but all other websites are moving at normal speed and the server is running fine. On the shared hosting server, the site is quickly turned off or terminated for abuse without warning. On our server, it just means the site can continue moving at a slower speed, or upgrade to a higher package since it needs more resources than what the package is designed for. The server keeps 30 days’ worth of logs and inside of each cPanel, the resources usage and limits are shown and can be used to gauge how a site is running under its current package.

There are many more benefits of CloudLinux and you can read about them here.
 
CloudLinux


Truth About Forwarded Mail

We’ll admit, cPanel’s webmail interface lacks a lot of features and the user interface is very basic. Because of these and other reasons, users like to forward their mail to Gmail, AOL, Yahoo, or other email providers. There are a few things you should know before you forward your email.

  • All emails, including spam, get forwarded to the account. Spam filtration does not get applied to messages that are forwarded. Because of this, the receiving email server will view our server as sending spam. This can cause an interruption to your mail flow if the server gets blacklisted.
  • Marking Spam on a forwarded message does not mark the original sender as spam. Most email servers do not see the original recipient, they only sees the last email server the message came from. For those that do, they associate the IP address of our server to that recipient, meaning, our IP can get a bad reputation, even though our server wasn’t the originating server.
  • Because of the previous points, you can no longer filter out spam messages efficiently without filtering out the good emails. Good spam filters will look at both the sender and the IP address of the mail server to determine if a message is spam or not.

You may ask then, is there a better way to get my email? Of course! One way is to use Microsoft Outlook. Most email services will allow for POP or IMAP so that you can have all of your emails in Outlook. This will consolidate all of your different emails into one program so you can easily see your business emails and your personal emails. I encourage anyone that is using their email for business to strongly consider switching their email to Microsoft Exchange Online or Office 365. For as little as $4 / month, you can have the same enterprise email service that all of the large companies do. The good news is, it’s a lot simpler to sign up for and use than you might think. If you are interested and need help, don’t hesitate to call and we’ll be happy to assist.