Changing The IP In cPanel For Sending Emails

Currently, anyone running a server, is probably used to dealing with constant problems with blacklisted IPs. In many cases, the problem is greater when a single IP is shared by many accounts, which means that all its customers on a server, are sending e-mail from the same IP. All we need is a security for one of the accounts that runs a DarkMailer script because of which all customers receive errors when trying to send some e-mail.

In cPanel, you can change the IP address of the Exim without interrupting service and very easily. If you run a dedicated server, VPS or Cloud, can have a second IP, you can follow these steps and instead use the second IP for sending e-mails.

Step 1:

Sign in to WHM root access and go to Service Configuration “Exim Configuration Manager”. In the ‘Find’ field, look for ‘Reference’. Should enable the Reference / etc / mailips for outgoing SMTP connections.

See Image:

Step 2:

Sign in via SFTP and in the / etc / mailips, insert the following line:


Where is, you must enter the IP you want to use for sending e-mails.

It’s all done. You can save the change and will thus make submissions through the IP indicated.


Be sure to make an analysis to find out where your server SPAM were sent. If the problem is not corrected, it is very likely that your second IP may also get blocked as well.

Posted in Tutorials / Howtos? | Leave a comment

Add an email account on your Apple device

With evolution of smart devices, everyone has started using smartphones for all types of work whether it’s related to business or personal. Email is one of the most significant mediums of communication in business. It may not be always possible for entrepreneurs and decision makers to sit before the desktop or carry a laptop to check your business email address accounts. Rather, it’s more feasible to get your business email account configured on the smart devices. Since most entrepreneurs in the UK use iOS devices, we are sharing you a guide for setting up an email account on the iOS devices –

Step 1 » Go to Settings and move down to Mail, Contacts, Calendars.
Step 2 » Click on Add Account.
Step 3 » Tap Other.
Step 4 » Select Add Mail Account.
Step 5 » Name – Enter your name.

Email – Enter your email, for e.g., suppose that is being your domain hosted by WHUK.
Password – Enter the one that you selected for email account in the Control Panel.
Description – Enter a description, for e.g.

Step 6 » Tap Next.
Step 7 » Highlight the IMAP

Incoming Mail Server
Host Name – Enter
User Name – Enter your full email address e.g.
Password – Enter the one that you selected for email account in Control Panel.

Outgoing Mail Server
Host Name – Enter your host name, for e.g.
User Name – Enter your full email address e.g.
Password – Enter the one that you created in Control Panel.

Step 8 » Tap Next.
Step 9 » There is an Optional field but it is essential to fill it out.
Step 10 » Tap Save
Step 11 » Click on the mail you created now.
Step 12 » Click on the Account
Step 13 » Tap SMTP in the Outgoing Mail Server
Step 14 » Tap in the Primary Server

Host Name – Enter your host name, for e.g.
User Name – Enter your full email address e.g.
Password – Enter your password.

Step 15 » Set the Use SSL ON.
Step 16 » Set the Authentication to Password.
Step 17 » Enter 587 (or as defined in our configuration email sent to you) in the Server Port. To verify the information, tap Done and then Account.
Step 18 » Move down to Use SSL for Incoming Settings and slide it to ON.
To ensure that your mails are saved both on device as well as on the server, synchronize Mailbox Behaviors with the server.
Step 19 » Tap Drafts Mailbox.
Step 20 » Go to On the Server field and tap Drafts. Click on Advanced to go back and follow the same for other mailboxes. Set the Sent Mailbox to Sent in the On the Server field, and set the Deleted Trash Box to Trash in the On the Server
Step 21 » To complete the setup, tap Account and Done.

Congratulations! You have successfully configured an email account on your iOS device.

If you find any difficulty with this, please feel free to get in touch with us via. Live chat or email.

Posted in Sales FAQ | Tagged , , | Leave a comment

How to Transfer a Domain Name with least downtime?


» Sign up with your new webhost and do not cancel you existing old hosting account. Make sure that you don’t let them know that you will be cancelling.
» After you have the details for the new existing account and your website is working from the old host server. Now you can start the migration of your website data from old host to the new host via old host FTP and then download all the files. After this connect to the new host FTP and upload all the files.
» Make sure to backup any databases on the old webhost and then upload the backup files via FTP to new webhost. The databases restoration can be done via phpMyAdmin of cPanel or SSH. The emails from the old host can be archived by making connection of each email address with POP3 by doing so all the old email will be downloaded to your local machine/computer. The new host will be able to receive the new emails but the old emails as already downloaded to your local computer would be available only locally.
» If you are having cPanel as hosting control panel in both old and the new host, then if provided by the new host your old emails may also be transferred.
» When on both the hosting account you have a copy of your website, it is now time to change the DNS of your domain.
» After you have confirmed the files on both of the hosting account. You may then update the Nameservers that are provided by the new host in your domain control panel.
» After the change to the DNS has been made, it will take around 48 hours approximately for your website to load from the new hosting server. In the meantime there will be a global DNS propagation of your website and it would be loading randomly from the old or the new host servers.
» Once the 48 hours is over and the DNS you updated is fully functional, your website is loading from the new host. You may contact your old host and cancel your old hosting plan.

Note: to reduce the time taken for propagation, after the website content is transferred, create an A record in the existing DNS. This will redirect all the visitors to the new web server, it is much quicker than time required for the propagation of the nameservers. For delivery of emails to the new servers make a MX record by doing so we avoid the waiting time for email delivery during propagation. It is wise to have MX records and A records pointing to the new hosting servers. After this is done the Nameservers can be changed according to you anytime.

Posted in Domain And DNS | Tagged , , | Leave a comment

Error Installing Modules Such As “json” “phpize\” failed

One of the customers recently faced difficulties with installing json in WHM under Software > Module Installer > PHP Pecl, where he encountered an error:

ERROR: `phpize\’ failed

The object is not in /usr/local/lib/php/extensions/no-debug-non-zts-20060


ERROR: `/root/tmp/pear/cache/json-1.2.1/configure’ failed

Hence with a view to helping everyone who may encounter such as issue, we are posting this post to our knowledgebase.


The error is mainly due to /tmp mounted as nonexec, hence inorder to troubleshoot it, you must follow the below procedure:

Step 1: Login to SSH

Step 2: Make tmp and var/tmp exec

mount -v -o remount,exec /tmp
mount -v -o remount,exec /var/tmp

Step 3: Install JSON using the command:

pecl install json

Step 4: Revert the changes you did in Step 2 by firing the commands:

mount -v -o remount,noexec /tmp
mount -v -o remount,noexec /var/tmp

Posted in Tutorials / Howtos? | Tagged , | Leave a comment

Information on Shellshock Unix Bug

Shellshock is a bug in the Bash system that is used to exert commands on Unix-based operating systems and relates to the processing of environmental variables. It is believed that the bug has existed for around 25 years, but has only just been discovered by Linux expert Stéphane Chazelas and poses a threat to any system that uses the Bash command line interface; this means that any servers running a Linux distribution could be vulnerable and require patching, as well as any Linux distributions used on the desktop, including Mac OSX as this is a Unix-based OS. The threat lies in the ability for hackers to create specially crafted environmental variables, with potential for the scope of the attack to be extended to include commands, which if achieved would allow hackers to run or install applications on a victim’s machine. Apache also stands to be vulnerable as CGI scripts are executed using shell commands and so it wouldn’t take much for a hacker to call a CGI script using some malicious code. A lot of this is just hypothetical for now since no attacks have been officially recorded thus far.

How does this compare to Heartbleed?

These two bugs focus on different targets. Heartbleed was a bug that lay at the heart of the OpenSSL, an application that is used to encrypt and secure a majority of Internet traffic. With Heartbleed, the security of Internet communications using the application was put at risk as it made it possible for hackers to decrypt what were thought to be secure connections, therefore giving them access to sensitive information. Shellshock on the other hand could prove to be more toxic as it targets Unix-based servers and their command-line interface (CLI) through which the systems are controlled. With much of the Internet running on Apache and with the chances of these Apache web servers running on a Linux base being high, Shellshock has the potential to be more damaging and widespread than Heartbleed.

How can I check if my Linux server or desktop machine is vulnerable?

By running the following Bash command, you will be able to identify if your Linux server is vulnerable:

env VAR='() { :;}; echo Bash is vulnerable!’ bash -c “echo Bash Test”

In the event that you see the following output, your system is vulnerable:

Bash is vulnerable!
Bash Test

You should then take the necessary steps to protect your server by applying the latest Bash patch. Our 24×7 support team is available to assist you with the process at all times.

What impact will Shellshock have on my Linux server?

Shellshock could leave your Linux server (cloud or dedicated) open to remote attack. It is important to ensure that your server is patched as quickly as possible in order to protect your information and so that a hacker doesn’t have the chance to attack. Particular attention should be paid to servers that are running Apache, specifically with the mod_cgi and mod_cgid modules included; particular installations of OpenSSH and some DHCP clients are also vulnerable. A patch has already been released and in order to take advantage of this, you should use the package manager that is included with your Linux distribution; this should be available for major distributions such as Ubuntu, CentOS, Redhat and Fedora. If you are unsure of how to do this then simply contact our 24×7 support team who will be able to patch your server for you.

Posted in Web Hosting Security | Leave a comment

How to check drive temperature? – Linux Command

Monitoring the drive temperature is a crucial aspect of server management, to ensure that the hardware delivers efficient performance. If the drives temperature exceeds the safe threshold limit, it may result in the drive to crash. Hence keeping a check on the temperature once a week (atleast) and monitoring its fluctuations can help bypass disasters.
To check the drive temperature, you must fire the following command as a root user:

smartctl -A /dev/hda

NOTE: In above command we have used hda due to the fact that the test server is configured with the “IDE controllers”, if your server is configured with the “SCSI controllers” device, replace the /dev/hda with the /dev/sda and Run the command.
Also make sure that you are using the individual partition label, for example.

smartctl -A /dev/hda1


smartctl -A /dev/sda1

Posted in Tutorials / Howtos? | Tagged , | Leave a comment

How to Update Contact Information or Whois Details for Domains with WHUK?

Having your domains contact information updated is vital. Frequent emails are sent to customers who have their domains registered with us, and we expect you to update the registrant, administrator, technical, and billing contact information for your domain(s). Some would also refer to this as the Whois information, it’s the same.

Well, if you don’t know how to update these details, here’s a guide.

Step 1: Log in to your web hosting dashboard.


Step 2: Go to Manage Domains under the Services tab
Step 3: Click View details for the domain you wish to change/update the details.


Step 4: Scroll down to the bottom of the page and click Contact Information for edit


Step 5: Evaluate the details for the fields and update where necessary.


Step 6: Save the updated details.


If you still need any assistance with updating the information for your domain, please feel free to contact our billing department by email ( or 24×7 live chat support, we’ll be glad to assist.

Posted in Domain And DNS | Tagged , , | Leave a comment

Bash Code Injection Vulnerability (CVE-2014-7169) – Fix and Solution

Be advised, it’s a temporary fix released by Red Hat Security Response Team. The team is working on a full fix for which they are expected to release the patch soon.

The Bash vulnerability is supposed to be of higher criticality than Heartbleed. It’s found in all versions of the bash package shipped by Red Hat, it’s unclear since when it’s been there. With the CVE-2014-7169 vulnerability, users may have the capability of arbitrary code execution. Certain services & applications allow remote unauthenticated attackers to provide environment variables, allowing them to exploit this issue.

Priority: Severe

The National Vulnerability Database has given a score of 10 i.e. highly severe, meaning it’s critical and the access complexity is Low. Hence, the vulnerability can be easily exploited by hackers if identified.

How to check if you have a vulnerable Bash version over your system ?

Run the below command to check :

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If the output is like:

env x=echo vulnerable bash -c echo this is a test

it clearly means you have a vulnerable Bash version running on your system.

In that case, apply the following patch to fix it.

Upgrade Bash using the yum command in ssh:

yum upgrade bash


Thus, if you run the above example with the patched version of Bash, you should get an output similar to:

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

Once the bash update is complete, reboot your system for the new bash package to take effect.

External References:

Posted in Tutorials / Howtos? | Tagged , | Leave a comment

Plesk 12 Demos – Parallels Web Hosting Control Panel


Parallels Plesk 12 offers an ideal hosting control panel for resellers, web admins and hosts offering web hosting solutions. Plesk needs no special explanation as people from the industry of server administration are well aware of its capabilities. With the recent release of Plesk 12, Parallels have further enhanced its features – which now allows users to convert resellers to customers and vice-versa on-the-fly. This version has a special inclusion of WordPress Toolkit for easing the task of management and security of WordPress sites.

Here are some resources to help you explore different areas of Plesk 12:

Login: admin
Password: panel

Login: admin
Password: panel

  • Plesk 12 Web Pro Edition – Power User Mode (Server + Site Management)

Login: admin
Password: panel

For Linux and Windows

  • Plesk 12 Web Host Edition – Service Provider Management

Login: admin
Password: panel

For Linux and Windows

Parallels has also provided a documentation which can be found here:

Information & image source :

Posted in Tutorials / Howtos? | Tagged , , | Leave a comment

Failed to connect to database: User admin already has more than ‘max_user_connections’ active connections

This is one of the common backup errors produced when the maximum number of  connections to the database is surpassed – after which this message is thrown “Failed to connect to database: User admin already has more than ‘max_user_connections’ active connections

In such a situation, unless any of the previously active connection is closed, no more connections can be established with the database. This may happen at occasions when there are too many requests made to the database OR a certain script consistently request for too many connections at any given point of time.

How to troubleshoot the backup error : Failed to connect to database?

Step 1 : RDP into the windows server.

Step 2 : Edit the file C:\Program Files\Parallels\Plesk\MySQL\Data\my.ini

Step 3 : Check the settings max_user_connections and increase the value or better remove the max_user_connections parameter and mysql default settings will be applied. This is how the file looks like :

my.ini screen grab

Posted in Tutorials / Howtos? | Tagged , | Leave a comment