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
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.
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.
- Edit /etc/sysconfig/network-scripts/ifcfg-eth0
Change the IPADDR and GATEWAY lines to match the new IP and Gateway for the new ip
- Edit /etc/sysconfig/network
Change the GATEWAY line here if it does not exist in the ifcfg-* file.
- Edit /etc/ips
Remove the new primary IP from this file if it is present
Add the old primary IP to this file
- Edit /var/cpanel/mainip
Replace the old primary IP with the new primary IP
- Edit /etc/hosts
Replace the old primary IP with the new one if needed. The hostname’s dns will need to be updated too
- 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.)
- Restart the ipaliases script to bring up the additional IPs: service ipaliases restart
- Run ifconfig and make sure all IPs show up correctly
- Update the cpanel license to the new primary IP
- Then run /usr/local/cpanel/cpkeyclt to update the CPanel license
- Then run the migration Wizard inside CPanel to update Apache and the website settings.
In a perfect world that will do it.
The firewall blocks passive mode FTP transfers.
To fix this error you need to:
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.
It’s three steps:
sh cldeploy -i