Archive for October, 2007



Install wordpress blog

Tuesday, October 23rd, 2007

There are many websites who use blogs on their website, I thought someone would be interested in knowing how to get a blog installed for their personal or business website. I would recommend wordpress blog – it’s the best blog I have ever used. And the installation procedure is very simple, just go through the following steps:

First of all make sure that your web hosting company supports PHP 4.2 or greater, MySQL 4.0 or greater and the mod_rewrite apache module.

You can download a zip or tar.gz of wordpress from http://wordpress.org/download/ then unzip the files. Now, you can create database from your web hosts control panel when this is done you will find a file named wp-config-sample.php which is to be renamed as wp-config.php, edit it and add your database details over there. And, now upload the files to your web space provided by your web hosting company.

Now, you are ready just type in the browser http://yourdomain.com/blog-directory/wp-admin/install.php fill in the Site name and email address and you’re done. It will provide you admin login and password. Where yourdomai.com means your website name.

Happy blogging!

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Access webmail access without cPanel login

Thursday, October 11th, 2007

A group of people working in an organization require to access webmail without cPanel login. Is it possible? YES, it is possible.

If you’re the manager and don’t want to share the cPanel login with other people in working in your organization and still need them to access the webmail they can achieve this by doing the following:

http://www.yourdomain.com/webmail or you can also login with webmail port number http://www.yourdomain.com:2095/

Where www.yourdomain.com is your website/domain name.

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Secure root password for server

Thursday, October 11th, 2007

Access to root password of the server is something to take care of, I would suggest you to keep your password as strong as possible so no one can guess it. If anyone gets access to your web servers root password – they could do anything on the server.

Password that you set for a root account should be case sensitive, alphanumeric and special characters. As for case sensitive the word you, You, YoU are all different.

Few passwords would be:

$tr0nGp@ss!@# [Strongpass123]
R00t3yP@$$&^% [rootmypass765]
!H@v3@6mW [I have a BMW]

You can create of some more complex passwords.

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


SSH welcome message (motd) configuration

Tuesday, October 9th, 2007

It’s always better to get your web server secure in all aspects, for this we suggest you to add a warning message so whenever any person logs in the server, the message is viewable to him.

To implement this on your dedicated server, you need to edit the motd file with the command nano /etc/motd , then you can enter your message within the file and save it.

A simple warning text that you can add in motd file:

This server belongs to “Some web hosting company”. Unauthorized access to this web server is fully investigated as your IP and login information have been recorded and an email is sent to our System Administrator.

Isn’t it simple!

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Disable recursion on DNS server

Monday, October 8th, 2007

For Windows dedicated hosting server the steps are as follows:

Login in your windows server as Administrator – you need to Open DNS the, from the console tree – right-click the applicable DNS server, after that click on Properties. In the Advanced tab under Server options, you can select the Disable recursion check box, and then click OK

You’ve done this on your windows server now we will do it on linux server.

For Linux dedicated hosting server the steps are as follows:

Kindly login in your dedicated web server as root, now you’re requested to edit the BIND configuration file which can be done by the command nano /etc/named.conf , each server has PRIMARY-IP and a SECONDARY-IP which are the name servers on the dedicated web server.

Add this in the BIND configuration file:

acl “trusted” {
PRIMARY-IP;
SECONDARY-IP;
127.0.0.1;
};

allow-recursion { trusted; };
allow-notify { trusted; };
allow-transfer { trusted; };

Remember to restart the named daemon on the dedicated server by the command service named restart

You’ve now done with closing open DNS recursion on your dedicated hosting server!

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Secure ssh on your dedicated web server

Monday, October 8th, 2007

 

If you’re looking to secure ssh on your dedicated web server, here are the steps that you need to follow to get your web server secured.

You need to login into your dedicated sever with root access. As you know the default port number of a web server is 22, and this known by any person on the earth who knows about Linux web servers. Now, we will switch the default port number (22) of SSH to something random. This will prevent server login attempts done on the default port number. For this you’ll have to edit the sshd_config which can be done by the command – nano /etc/ssh/sshd_config now find the line #Port 22, uncomment it and replace 22 by some random port number.

You need to take care to add this random port number to your firewall allow list. If you fail to do so, you’ll NOT have access to the server.

Now, we will have to change the protocol in the sshd.config, so you can edit it again with the command – nano /etc/ssh/sshd_config and find the line #Protocol 2, 1 and change it to Protocol 2.

Remember to restart sshd daemon once you have saved the configuration file. Your dedicated server ssh is secured now!

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.