cPanel Proxy
This script is made for people who use cPanel. Its purpose is to give access to cPanel (including webmail and WHM) at port 80 by acting like a proxy. (For people behind strict firewalls.) It can be installed by server owner, reseller or end-users.
Installation instructions:
- Create subdomain “cpanel.yourdomain.com” (You’ll probably need access to cPanel for this, so install it before you need it!)
- Download and unzip cPanelProxy.zip (if you haven’t already) from http://cpanelproxy.net/
- Upload the files to the subdomains directory, probably “public_html/cpanel” in FTP. Be sure to remember .htaccess!
Needed files: cpanelproxy.php .htaccess php.ini
Install for webmail and whm:
- Repeat with “webmail” in stead of “cpanel” in subdomain and directory.
- Repeat with “whm” in stead of “cpanel” in subdomain and directory.
Auto Installer:
- A new feature on the website makes it easier to install cPanel Proxy, and you can even do it thru your firewall. All you need to do is to enter your cPanel login information, at the auto installer will take care of the rest. http://cpanelproxy.net/autoinstaller
How to move an account from one Cpanel server to another Cpanel server via Backend (Shell)
Basic steps
1. Create a .tar file (backup) of the account in the old server.
2. Copy it to the new server using scp.
3. Untar (restore) in the new server.
1. Create a .tar file (backup) of the account in the old server.
To create a tar package of the account you have a Cpanel script.
/scripts/pkgacct ‘username’
Executing this script will create a username.tar.gz file in your /home directory. You can copy this to the new server.
2. Copy it to the new server using SCP
scp user@IP:/home/username.tar.gz user@IP:/home/
3. Untar (restore) in the new server
Login to the new server using ssh and execute the script.
$ cd /home ; /scripts/restorepkg ‘username’
Apache failed to start with the “No space left on device” error.
If you receive the following error while restarting Apache in the server, you need to do the following steps.
These errors means that there is no available IPC (inter-process communication) resources in the system, such as semaphores or shared memory segments. You need to check IPC resources which are used in the server using ‘ipcs’ command:
$ ipcs -a
…
—— Semaphore Arrays ——–
key semid owner perms nsems
0×00000000 201293824 apache 600 1
You will be able to see a lot of semaphores under Apache . You need to kill those processes using the following script and restart apache.
$ ipcs -s | grep apache | perl -e ‘while (<STDIN>) {@a=split(/\s+/); print `ipcrm sem $a[1]`}’
How do I reset my root password on Debian Server Using GRUB ?
Reboot your Server/Desktop.
1)Press Escape to see your boot menu while booting your server.
2)Choose the kernel you want to boot.
3)Press “e” for edit.
4)Type in the following line after a space on the kernel line.
5)Press enter key and then press “b” to boot that kernel, this will take you into single user mode+
6)Now Mount your Server in Read-Write mode using mount command
7)Reset your root password.
Do I need MX records for my domain?
Technically, a domain does not require MX records to receive email. By default, a sending mail server should attempt to deliver mail to the host itself if no MX record is present. For example, if a sending server is trying to deliver mail to user@example.com, and example.com has no MX records, it will try connecting to any mail server at example.com itself.
However, it is highly recommended to create MX records for your domain, even if they seem redundant or unnecessary; in the above example, example.com should still have at least one MX record set to domain.com itself to help ensure delivery, like so:
example.com 43200 MX 10 example.com
Some non-RFC-compliant servers will fail to deliver email for domains that lack MX records
