How do I configure GRUB to see all of my memory?
You can specify the amount of memory on your system if your computer is not recognizing all of it. For example if your system says you only have 128 MB of RAM and you know for sure you have 256 MB, then you can specify that in your grub.conf file, located at /boot/grub/grub.conf
What you want to do is add the following syntax mem=M to the kernel line of your grub.conf file. So for instance if you were specifying your system had 256 MB in the grub.conf file, it would look something like this.
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Enterprise Linux AS (2.4.21-15.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-15.EL ro root=LABEL=/ mem=256M
initrd /initrd-2.4.21-15.EL.img
title Red Hat Enterprise Linux AS (2.4.21-9.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-9.EL ro root=LABEL=/ mem=256M
initrd /initrd-2.4.21-9.EL.img
Disable ping requests in Plesk
By default your server can be pinged by anyone, meaning it is discoverable. You can improve security by changing your firewall to only allow known IP addresses to ping your server.
If your static IP is 192.168.1.1 change the rules under Ping Service in Plesk’s default Firewall rules.
Allow incoming from 192.168.1.1
Deny incoming from all others
Using the built-in Plesk firewall
Although you could edit the firewall from the command-line it is much easier using Plesk’s firewall instead.
Just navigate to Modules > Firewall. If you have a static IP address you can create rules so that the server will only allow access from your IP address at your home and/or office.
By default the SSH standard port number is 22. If you look at your logs you might see a large number bad login attempts on that port. Changing this port number is a simple way to make your server more secure. To change the port number login as root and run the following command:
Find the line that says:
Change this line to another port number above 1024. Using a port number above 1024 prevents scans like nmap picking up ssh.
Save the sshd_config file and then restart sshd.
Using SFTP(Secure FTP) in Plesk
Secure FTP is more secure than FTP since it uses the SSH protocol. Shell access must be enabled for each Plesk user for each account.
In the setup page select /bin/bash(chrooted) under the Shell access to server with FTP user’s credentials. This user will now be able to login over SFTP. Remember to change the port in your FTP client. If you are sure you don’t want users to login over standard FTP you can also block this port via the Firewall module in Plesk
The following rules would apply:
Deny incoming from all on ports 21/tcp, 21/udp
You can further secure your FTP server if you have a static IP by allowing access only from that IP. If the static IP is 10.1.1.2 your rules would be:
Allow incoming from 10.1.1.2
Deny incoming from all others
hotmail and yahoo mail spam flagging issue
If you have more than one domain on your server it is better to use our SPF Record to fix this issue.
For example:
Server is sending mail as mail.serverbuddies.com but when the receiving mail server performs a reverse PTR lookup, it finds serverbuddies.com MISMATCH The solution would then be to tell qmail that it is sending mail as domain.com instead of mail.serverbuddies.com.
Here is the fix.
echo serverbuddies.com > /var/qmail/control/me