Centos 6 and above now has an easy to use command to change the hostname of your server.

Simple type:

hostname (newhostnamehere)

Replace (newhostnamehere) with what you want the hostname to be.

It’s nice when things are actually simple, good job job guys.

Some people call this rooting a server. Basically if you lost your root password and need to get int this is your only option. You will need to be in front for the server or with a KVN plugged in.

Make sure to follow each step exactly:

Reboot your computer / Turn your computer on.
Hold down the Shift key at the start of the boot process to enable the GNU GRUB boot menu (if it does not show)
Press ESC at the GNU GRUB prompt.
Press e for edit.
Use the Arrow keys to highlight the line that begins with kernel and press the e key.
Go to the very end of the line and add rw init=/bin/bash
Press Enter and then press b to boot your system.
Your system will boot up to a passwordless root shell.
Type in passwd yourusername
Set your new password.
Restart your system.

There is no plug ins in WordPress to bulk fix your permissions. That is why this little script was made. The trick is you have to run it from the root of the server which in most cases your hosting company has to do.

It’s really easy to run and 100% safe.

Here is how:

1. Download the script anywhere on the server

wget http://ezlinuxadmin.com/downloads/fixperms.sh

2. Run the script from the same folder it’s downloaded

This will fix one account
sh ./fixperms.sh -a username

This will fix all accounts
sh ./fixperms.sh -all

That’s it, enjoy!

If just doing a general YUM update does not update your Cloud Linux you are not alone. In fact sometimes the LVE manager never installs at all.

Don’t worry though, it’s just one line of code and about 5 minutes to fix.

yum install lvemanager --enablerepo=cloudlinux-updates-testing

If that still does not work try to do a forced CPanel update and then run again.

If that doesn’t work send a message to CPanel or Cliud Linux to ge their stuff to work.

Good luck!

CryptPHP PHP malware has a become a nightmare for WordPress owners. Hacking millions of websites with it and getting web hosts listed in CBL effecting other web hosting accounts that did nothing wrong. It’s a vicious loop unfortunately that blacklists like CBL and Sorbs don’t care about using scrutiny or rational. Their philosophy is to just block everything if there is an issue despite websites being blocked that did nothing wrong. Hopefully someday blacklist will focus on the domains that cause issues not the IPs. That way good sites will not blocked for doing nothing wrong. Most IP people and the net know that Sorbs blocks million of good websites with no regard, I was chocked though to see CBL jump on the same list of block first ask later.

Anyways… to find the CryptPHP hack A.K.A. social.png hack. You need to run search command from root on your server.

This will find it:

for r in `locate social | grep png`; do file $r; done | grep PHP

But removing it will not fix the issue, if it’s on the site than the site has been hacked and needs to be removed. The only things that can be salvaged is the images and databases.

Here is a little information on having your WordPress Hacked

To compress a file or folder with tar run this:
tar -cvf archive-name.tar directory_name

To extract a file or folder with tar run this:
tar -xvf archive-name.tar

If you want to change the language the user root uses by command in Centos you need to run this:

export LANG=en_GB.UTF-8

This is for English if you want another language you need to change this to your language; en_GB

Some scripts like WordPress and Joomla can leave a big error_log files that no one will ever look at. Try opening a 30mb log file with Word and see what happens. In most cases you can just remove this file with a simple command.

To remove all error_log files for CPanel accounts that are live use:

find /home/ -type f -name error_log -delete

To remove all error_log files from backups use:

find /backup/ -type f -name error_log -delete

This will take a while to complete because it will look through every file, it also runs pretty smooth so just sit back and let it work it’s magic.

Changing a server to a new IP is a nightmare, there is so many places that need to update. If possible always just set up a new server and transfer everything to it. If that’s too hard than here is how to do the migration the best possible way.

1. Edit /etc/sysconfig/network-scripts/ifcfg-eth0
   Change the IPADDR and GATEWAY lines to match the new IP and Gateway for the new ip
2. Edit /etc/sysconfig/network
   Change the GATEWAY line here if it does not exist in the ifcfg-* file.
3. Edit /etc/ips
   Remove the new primary IP from this file if it is present
   Add the old primary IP to this file
4. Edit /var/cpanel/mainip
   Replace the old primary IP with the new primary IP
5. Edit /etc/hosts
   Replace the old primary IP with the new one if needed. The hostname’s dns will need to be updated too
6. Restart the network service to make the new IP the primary: service network restart
   (Note: You’re probably going to be disconnected at this point, and have to log in to ssh using the new primary ip.)
7. Restart the ipaliases script to bring up the additional IPs: service ipaliases restart
8. Run ifconfig and make sure all IPs show up correctly
9. Update the cpanel license to the new primary IP
10. Then run /usr/local/cpanel/cpkeyclt to update the CPanel license
11. Then run the migration Wizard inside CPanel to update Apache and the website settings.

In a perfect world that will do it.

Good luck!

The firewall blocks passive mode FTP transfers.

To fix this error you need to:

open: /etc/pureftpd.conf

Find: PassivePortRange in /etc/pureftpd.conf

Remove the # and add this to the line: PassivePortRange 30000 35000

See TCP_IN in /etc/csf/csf.conf and add the passive port range to it

TCP_IN = “##,##,##,###,###,###,30000:35000”

Notice in TCP_IN you see 30000:35000 , that’s a range of ports. And based upon what you set for the PassivePortRange in /etc/pureftpd.conf, you should modify TCP_IN in /etc/csf/csf.conf to allow those inbound ports.

Next you need to restart both PureFTP and CSF after making the changes.