Real Global Solutions

I am new at web design, and in the process of trying to find a good web hosting service. I plan on having lots of videos and photos on my sites, and was wondering what kind of features are the most important for me to be looking for when searching for a web host. Are some servers faster than others? If so, which are the fastest? And is it better to go with a windows or linux server? Are there any other important features that I need to look for? Thanks in advance for any suggestions!

We need to bring something to your attention. Users of Fedora Core 5, 6, CentOS 5 or Red Hat Enterprise Linux 5 are in for a rather sour and unpleasing treat.

Unfortunately, this is the reason for this blog post - and this is the reason we had such a tough time installing Fantastico, it just didn’t want to install! Well, I quickly learned of this “bug”, and I found a fix. The problem was the wget feature, and its version. Apparently, the newer ones (already installed on most servers) do not work as they’re supposed to. We’ll be replacing whatever version we have - with a known working version; wget-1.10.2-3.2.1

So, here are the install instructions. Simply pull out SSH, and run the following command as root:

For 32-bit:

rpm -qa wget ;
wget ftp://ftp.funet.fi/pub/mirrors/ftp.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/wget-1.10.2-3.2.1.i386.rpm
chattr -ia /usr/bin/wget
rpm -e wget ;
rpm -ivh –force wget-1.10.2-3.2.1.i386.rpm ;
rpm -qa wget ;

For 64-bit:

rpm -qa wget ;
wget http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/x86_64/os/Fedora/wget-1.10.2-15.fc7.x86_64.rpm ;
chattr -ia /usr/bin/wget
rpm -e wget ;
rpm -ivh –force wget-1.10.2-15.fc7.x86_64.rpm ;
rpm -qa wget ;

Lastly, we’re going to add wget to yum.conf so that the OS doesn’t reinstall another version of wget over our working version - through one of its updates.

Let’s get to it:

nano /etc/yum.conf

Find the line exclude= and add “wget*” at the end (on the same line). Please ensure that wget* is not on its own line - this will seriously break yum.

If you’re an end user receiving this error, there’s nothing you can do about it. You’ll have to contact support, and wait for the host to resolve the issue. The fix is simple, however some may not be aware of it. In fact, many of our VPS customers have been asking us about this very issue.

So, the problem occurs in cPanel, under the “Cron Jobs” feature. The user is presented with the following error:

/usr/bin/crontab permissions are wrong (0755). Please set to 4755

To resolve the issue on most Redhat/CentOS/Fedora servers, simply run the following as root:

chmod 4755 /usr/bin/crontab

This tutorial explains a simple, straightforward method for migrating cPanel accounts from one server to another. You can use this method to transfer accounts from an old server to a new one, help customers from another host move to your host, etc. This does not even require root access on one end of the migration. Basically, this is a more reliable method than the “Transfer Account from another Server” tool in WHM, which rarely works.

Requirements:
- cPanel on both servers
- WHM access on the new server (one that the accounts are being moved to)
- root access on the new server

Definitions
The server you are transferring the accounts from = “old server”
The server you are transferring the accounts to = “new server”

Instructions
1. Log into WHM of your new server and create a new account called “restore”, or anything you like for that matter. Remember the FTP address, username (’restore’, in this example), and account password. We will need these for later.

2. Log into the cPanel account you are wanting to transfer on the old server.

3. Click on “Backup >> Generate/Download a Full Backup”.

4. Once here, select the backup destination to be “Remote FTP Server”.

5. Enter your email address for verification, followed by all of the FTP account information for “restore”, which we created on the new server.

-Remote Server: new server’s address
-Remote User: restore
-Remote Password: restore’s password
-Port: 21

Then, click “Generate Backup”. This may take some time to backup the files, depending on how large the account is. You should receive an email provided in the above info once it is complete.

6. Now, log into SSH on your new server.

7. Type in the following commands:

cd /home/restore/public_html ( please double check this link)

ls

After running the list command above (ls), you should see the tar file of the account on the old server. This means that you have successfully sent the file via FTP to your new server.

8. Now move the tar file to your new server’s /home directory with the following command:

mv tar_file_name /home

9. Now, log into WHM on your new server and navigate to “Backup >> Restore a Full Backup/cpmove file”

Once here, you should see the old account’s username under “Possible cpmove archives found:”.
If you do not, log back into SSH and be sure that the account’s tar file has been moved into /home.

10. Type in the account name in the text field in WHM, which is proceeded by “Enter the username for the account you wish to restore:”.

11. Click “Restore”.

12. Repeat process for additional accounts.