Force Users To Use Single Php.ini Under suPHP

If you have a dedicated server and use it to sell shared hosting and you want to force users To use single php.ini Under suPHP then this article is for you. Today I am going to explain how you can force your users to use same php.ini under suPHP by disallowing .htaccess override. Limiting php.ini use will add security to your server and will disallow users to use custom php.ini file by overriding default php settings set by server administrator (root).

How to make it work:

Its very simple to enable this function in server using suPHP. Just by enabling phprc_paths in /opt/suphp/etc/suphp.conf will do the work for you. See the steps below:

Code:

vi /opt/suphp/etc/suphp.conf

Find the code below and press I to insert text.

[phprc_paths]
;Uncommenting these will force all requests to that handler to use the php.ini
;in the specified directory regardless of suPHP_ConfigPath settings.
;application/x-httpd-php=/usr/local/lib/
;application/x-httpd-php4=/usr/local/php4/lib/
;application/x-httpd-php5=/usr/local/lib/
Remove ( ; ) from the last three lines ie.

application/x-httpd-php=/usr/local/lib/
application/x-httpd-php4=/usr/local/php4/lib/
application/x-httpd-php5=/usr/local/lib/
Now press ESCAPE button and enter :wq to save the file.

Restart Apache

Code:

/sbin/service httpd restart

Now Users wont be able to override your default php.ini file.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

Article Source: Force specific php.ini in suPHP

Choosing the Best Domain Name

“What is in a ‘Domain Name‘? A rose by any other word would smell as sweet.” It is obvious that William Shakespeare knew nothing about the world of Web hosting, by those lines found in Romeo and Juliet. In the Web hosting world a domain name is very important to your company, image, or presence Online. Often a domain name might make or break you. So, what is in a name?

First let me expell the biggest myth in picking a domain name. The old rule saying that the holy grail of domain names is to find a three letter one you can use (such as abc.com or xyz.com) is a misconception. Just about any domain name has the destiny to be great, it is all in how you tie it in with your Web site. I will get more into that in a moment.

Don’t pick a domain name out of the blue that has nothing to do with your Web site at all. If you sell bikes, then having the domain name airplanes.com doesn’t make much sense. Picking oddball names can often confuse a visitor because it becomes harder to relate your Web site with the domain name.

For that same reason, do not make your domain name too complicated either. Which are you more likely to remember, mikesbikes.com or heylookatmeihaveabikesite.com. Short domain names is not the way to go either. You must find something that relates to your Web site, with a few good key words.

Key word placement in a domain name can be one more helpful step in trying to get your rankings up on any of the big search engines out there today. If you are selling Web hosting, having the domain name mikeswebhosting.com is going to do better in the search engines than mikessites.com. Once again, with mikeswebhosting.com you know you are getting Web hosting by a guy named Mike. It’s all there in the domain name. With the other, you aren’t sure what you will be going to till you get there.

A rule I have broken in some of my examples here is do not use words that need hyphens or apostrophes in them. A good domain name should be able to be typed out simply. Adding too many modifiers that should but are not there might make your visitors forget where to put them, or leave out a letter or two. Instead of using mikessite.com use mikemcmikeson.com.

There is obviously more in a name than William Shakespeare thought, a domain name at least. Using these few rules of thumb along with doing good research though will provide you with a domain name that not only looks cool, but leads more traffic to your Web site.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

Design an Eye Catching Website

We all know that these days every one can design a website but the question remains how to design eye catching website . I have read many books ,articles and tutorials about web design and have realized that every web designer has his own way of designing websites.

After I read all of that and made extensive research , I decided to write something about it and to share some of my experience with you. This is my first article and I must say I’m not a writer but I hope you will find it very informative. Of course I wrote about something which you might already know about but I believe there is always someone out there who needs such information and tips and benefits from them. In the article I have gathered and explained some good tips (Do’s and Don’t's) which will give you an astonishing results if you follow them well.

Below are the tips for designing an eye catching website which you will be proud of .

1 Consistency : It is always better to keep your design from page to page consistent so that the visitor knows that he is still in the same site and didn’t jump to another site.

The page or site color scheme and navigation should be the same throughout the site.

2 Navigation : Always keep your navigation simple . Tell the visitor which page he is on . This can be done in many ways and the way which I think is the best way is to remove the link from the page which he is on .

For example, Let’s suppose that you have the following navigation text on your home page …

Home — About Us — Contact Us — Services — Order

Then suppose that the visitor clicked on the services page .

When the services page is loaded then the link which says services will not be a link instead it will be a normal text with different color. That helps the visitor know which page he is on. If you are using graphic buttons then You can provide a different version of the button and make it without a link.

3 Use Browser Safe Colors : What are browser safe colors anyway? Browser safe colors are 216 colors which remain the same when displayed on any computer or browser.

Colors which are not browser safe may dither when displayed some computers ,meaning if a computer can’t display a color 100% it will then display the nearest color to it instead. So make sure that you use browser safe colors throughout your site.

4 Minimize the use of Graphics : A site with a lot of graphics will take forever to load. Even though graphics make sites better but it is always better to minimize the use of them for many reasons including but not limited to the following :

- A lot of Graphics make your site or pages take forever to load which will make the visitor of your website close the page or hit the back button .

- Search Engine Spiders have problems with graphics because they will not be able to index any page that has a lot of graphics .

- Of course you can use small, yet fast loading graphics instead of the big ones . Also You can use them as a table or cell background but make sure that the text is readable before the background image is loaded.

Don’t forget to use the ALT tag for all of your images!

5 Flash : Flash is is much like the graphics . Even though Flash brings your site to life but avoid using a lot of it on your site because that will make it load forever .

You can use small Flash animations and also You should give the url of the Flash Plug-in for the visitors who haven’t got the Flash Player on their computer. After all You want people to be able to see your Flash animations. So don’t over use it because they say Flash is evil.

6 Frames : Frames are not good for many things including but not limited to the following :

- Search engines have problems with them .
- The links can be opened into the wrong frame.
- Distracting scroll bars are displayed when the content doesn’t fit it.
- Many other things but There are many reasons which make us sometimes use Frames on our websites which some are the following

Frames enable us to manage sites easily. Suppose you want to update the header of your website ,if you designed it with just an html then You will have to update all of the pages on the site but Frames made that easy by just updating one page and You will not have to update the rest. There are many alternatives to the frames . You can use PHP Includes to include the desired file to the desired location. You can use this code to do so.

The filename.php will be the file name which you want to include, but The page which you are going to insert the code must be saved as yourpage.php and have .php file extension. Also You can use Extended Server Side Includes which is like the PHP by using the following code. The page which you are going to insert the code must be saved as yourpage.shtml and have .shtml file extension. So avoid using Frames on any part of your site.

7 Organize Your site files well : It is good to organize your site files well and divide them into categories for easy file management.

For example suppose you have a lot of products and then you can organize them as follows

products/product1/ or products/nameofproduct/

So the url of the product will be like http://yourcompanyname.com/products/product1 or http://yourcompanyname.com/products/nameofproduct/

In that way You can organize your web files easily .

8 Use Limited Colors only : Avoid using many colors on your site . Limit your colors to four or six .

9 Links : Your links should be descriptive . And should be readable . Also Use one color for all of your major links .

These were some tips which is necessary to use for designing an eye catching website.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

After all We all want to design great sites .

Scripting and Security

It is so easy to forget about security when you first start out scripting your own interactive content; so long as it does what you want it to, does it really matter that someone with a bit of knowledge can see the script configuration files? Yes it does! Once hackers know a bit more about the server environment, they can use that to try known exploits that will open the server so they can get access to it; and once they get it, only they know what they will do with the information!

Fortunately there are a few simple, but often overlooked, techniques that you can use to minimize the risk of exposing your server through poor scripting. I’m going to discuss a few here.

Identifying Entry Points

The most common way of getting access to a server is through a script that processes data from an outside source (either another script or user input); so your first priority should be to secure any scripts that process any tainted data (the name given to data that isn’t generated by the script).

Other security issues can arise from people “discovering” data files that are used for running a script. Basic password protection through the use of .htaccess or putting these kind of data directories and files out of reach should be enough to thwart the curious visitor looking for an easy way to get some control over the site.

The more determined someone is to get access to your server, the more they will probe your site looking for scripts, software or server configurations that have known security issues. In some cases all it takes is for a certain combination of letters and symbols passed in a query string to fool the server into passing scripts as plain text. It would be a good idea to keep your scripts and software up to date; while the new versions of the software may still be buggy, the more commonly known exploits of older software should be fixed.

FormMail is a very well known script; however recently there was a bug discovered that allowed anyone who knew about the exploit to use the script to send out spam mail. While the problem has since been fixed, there will still be a lot of servers that are running the old version and so run the risk of having their IP addresses put on the mail blacklist.

Never Assume that Data is Safe

Be careful not to fall into the trap of assuming that your online forms will be used the way they were designed; even the naive visitors that fill in forms for the fun of it with various symbols can break open a script. To reduce problems caused by unexpected data, you should make sure that data is preprocessed before using it as valid input.

There are two places where you can check the input that comes from your visitors; on the client side, and on the server side. While both have their benefits and drawbacks, you should be careful not to rely entirely on client side validation as it could easily be bypassed.

Client Side Validation

To validate data on the client side you have to ensure that there is support for the scripting language (either JavaScript or VBScript) and that it is enabled on the visitors’ browser. Where you can be sure that either is available; then it can save a round trip to the script should any data be invalid. The problem of dealing with browsers that cannot handle the client side scripts still remains, although careful planning of form field sizes and data options can reduce the number of invalid field entries.

Server Side Validation

The best thing about validating the input on the server is that your visitors don’t need to meet any specific browser requirements. Of course validating on the server side can be much more demanding on server resources, but it does help to catch any invalid data that comes into the script directly or happens to make it past any client side filters you created.

Dangerous Data Types

Its all very well knowing that certain user input can be dangerous, but exactly what kind of data can be hostile if run directly by your scripts? Well, there is no easy answer, as it will depend on what your script is doing with the data, but there are some data types or patterns you can look out for.

HTML Code – may not seem like a threat in itself, but if your script is set up to allow HTML code of any form, be sure to strip out any comments; otherwise it might be possible for visitors to start scripts with a SSI call with some undesirable effects.

Symbols and Special Characters – could easily be mistaken as part of an escape character or variable with unexpected results. More likely to break a script than expose a server.

File Paths – be very careful to restrict the directories and paths you allow your script to access; filter out all requests to back out of a directory (../) as this is a popular way of getting access to otherwise inaccessible directories.

Keeping it under wraps

Another good idea is to hide as much of the data transferred between your visitors and the server as possible. Writing your script so that it will only accept valid data from a form that uses the POST method, not only keeps the information out of the URL that your users see, but makes more work for those people that try to break into a script by passing data through the URL. For extra protection you could even make it so that your script checks that the form used is actually on your own site; be aware however that the HTTP_REFERRER header that is commonly used to achieve this sort of protection can be forged.

Conclusion

While there are other more complex ways of gaining access to a server, I hope that I have made you aware of some of the more common ways that undesirables will try to get access to your server. By taking the extra time in pre-processing any tainted data, you can go quite a long way in making scripts more secure.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

Apache Vs Internet Information Server (IIS)

Apapche and IIS can compete neck to neck sometimes. If you’ve been lurking in the various forums and newsgroups devoted to webmastering, you could hardly fail to notice the heated debate going on at this time. No, it’s not which is the best browser. This debate is about web servers. More precisely, which one is better: Apache or Internet Information Server (IIS).
To tell you the truth, I’ve used them both (and a few others as well) and the simple plain truth of the matter is these two web server platforms are really functionally equivalent.

Ease Of Use

IIS is much easier for the novice as operators can maintain it from easy-to-use screens and forms. Windows 2000, on the other hand, costs a lot more than other operating systems such as Linux, FreeBSD and Unix.

Straight Apache requires a huge learning curve to learn how to operate and administer. Everything is configured in extremely obscure text files, and these configurations are done by hand (although you can purchase add-on utilities to enable entry of much of this information from screens and forms.)

Security

The security model of IIS is one of the best ever designed, based as it is upon NTFS (the security model of Windows NT and Windows 2000). This model is far superior to the anything provided with Apache for non-Windows systems. Of course, on Windows, Apache can use NTFS as well.

Of course, IIS has been plagued with a number of vulnerabilities lately, and these are a concern. It’s common to patch IIS at least monthly, and to install a new service release (a collection of patches) twice a year. Most of the bugs were worked out of Apache (prior to version 2) long ago. Of course, with the release of version two of Apache you can expect a number of security and other flaws to surface – these are a normal part of a product’s life cycle.

Customization

IIS does NOT have the equivalent of HTACCESS. The HTACCESS file in Apache is used to individually configure virtual sites (web sites) without restarting the web server. However, on IIS you have a very flexible method of configuration with ISAPI filters and other similar methods. Both methods (HTACCESS and ISAPI filters) are very obscure and for advanced webmasters.

Efficiency

According to several reports that I’ve come across lately IIS is more efficient than Apache. My own testing has led me to conclude the performance of the two is roughly the same for static pages. PHP (the server side scripting platform common on Apache) tends to be more efficient than ASP (the server side scripting system for IIS) according to many sources, although I have tested neither for speed.

Hardware Requirements

I have run both web server platforms on large and small boxes of many different configurations, and I’ve found they require much the same hardware. This is not surprising, since the two platforms basically do the same thing.

When you configure Windows and IIS, it’s a good idea to strip the operating system of unneeded functions. This reduces the size box you need (as well as increasing security).

I’ve run both platforms on 64mb of memory with a single 5600 RPM IDE drive and 200mhtrz processors with reasonable response time (all things considered). I’ve also run them on dual 2gigahertz systems with 15k RPM SCSI raid 10 drives with incredible performance. The two platforms are equivalent in hardware needs.

Large Server Farms

Microsoft has worked hard on load balancing, so there are more options available for IIS and Windows 2000 for this than other operating systems. In fact, Windows 2000 clustering (the ability to run several servers using the same disks) is very advanced and makes disaster recovery a breeze.

Disaster Recovery

IIS backup solutions (those which are provided with Windows 2000) are surprisingly weak. There is no way to back up the metabase (all of the IIS configuration parameters) from one machine and restore it to another (which makes disaster recovery difficult). On the other hand, with Apache it’s just a matter of saving all of the configuration text files.

Language and other support

IIS and Apache both support CGI, SSI and PERL (ActivePerl on IIS is excellent). IIS natively supports ASP and I’m sure you could find PHP if you looked (I have not). Apache tends towards PHP, although you can install something like Chilisoft ASP if you want.

CGI, SSI and PERL are performance hogs and security nightmares in both web platforms.

Stability

Both web platforms are rock solid stable. I have run apache servers which have stayed up for longer than a year without a reboot, and my IIS servers have run for years with the only rebooting required is the occasional service pack and security patch. Neither web platform (or OS for that matter) has even once crashed due to a bug.

Operating System Integration

IIS and Windows 2000 is a more “integrated” environment than Apache, since IIS is targeted specifically for the operating system. This has the advantage that the GUI and controls of IIS look and feel the same as every other tool on Windows.

On the other hand, you can find Apache for just about any platform, including Lunix, Unix, BSD, and even such things as OpenVMS. If you need to be able to move between platforms, then Apache is a great choice.

Email

SMTP on IIS is primitive but functional. This is because it is only provided to allow scripts and such to send email from the server. If you need additional email support, you are expected to use Exchange or some other email system.

Apache does not support SMTP (sendmail), although a version is usually provided on the target system. The provided email solution is full featured – but you must be very sure to check the configuration to be sure your system is not an open relay.

The IIS SMTP module is configured through the standard Windows 2000 entry system, while Sendmail requires configuration file editing. IIS SMTP is absolutely trivial to maintain; Sendmail can be a challenge.

DNS

DNS on Windows 2000 is far, far superior to anything available on Unix or Linux. Bind (he DNS for Unix and similar systems) has traditionally suffered from a huge number of security vulnerabilities) and is very involved to maintain.

My own experience with DNS servers indicates the best solution is a dedicated DNS application box. These are inexpensive (for a business), easy-to-configure and much more secure than either the Windows 2000 version or the Unix version.

Search Engines

There is NO difference as far as search engines are concerned between Apache and IIS (or any other web server, for that matter).

Conclusions

I’m sure I could write for hours and hours about this subject. Basically, IIS and Apache do the same thing. They have a vastly different design philosophy, however, and the underlying operating systems have even wider differences.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

Looking for a good host – quick tips

Here are some general but very simple guidelines I wish I had followed when I started:

*Adequate plans. Do they have what you need? You don’t want to sign up for a plan and then go and build your site in a fashion that isn’t supported by the host. (Example, if you require ColdFusion, check that CF is supported )

*Server status, can you ping their servers? What speed are you getting?

* Forums: ask around about hosts you have interest in. If the host site itself has user forums, browse around there.

* Service. (most important IMO) Do they have a toll free number? What are their hours of service? If they have phone support, is it outsourced or on the same premises as your server? In my case, live 24/7 support was essential.

* how long have they been open? Do a who-is search, was the domain registered yesterday? Do they have a client list? Companies that have been open longer obviously have the experience and reputation and resources needed to survive in the industry.

Send them an email, see how long it takes for them to respond to get an impression on wait times between getting responses.

I guess it would help you to get a good host.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

How to to setup Unix/Linux SSH key authentication

Its easy to setup a Unix/Linux SSH key authentication, heres how. We normally setup ssk key authentication to automate some of the jobs. If you have more than few hundred of servers and if you need to login reguarly, then better to have SSH key setup. You don’t need to enter password all the time.

* Creating keys
* Distributing public keys
* Testing ssh accesses
* Troubleshooting

1. Creating keys

Keys are created with the command ssh-keygen:
# ssh-keygen -t -b -C “comment” -f

where:
* key-type is dsa or rsa (dsa is the most commonly used these days)
* key-len is the length of the key. For dsa 1024 bits is considered as secure enough, 2048 is considered more than secure. Keys larger than 2048 should only be used if erformance is not an issue
* name is the name of the key-files. Defaults are id_rsa for rsa and id_dsa for dsa. I personally use id_dsa-

The result are two files, id_dsa- the private key and id_dsa-.pub the public key.

2. Distributing public keys

In order to use the private/public key sheme to encrypt the session data the private key must be installed on the remote machine.

Copy the private key to the remote machine: # scp id_dsa-.pub @>remote-host>:/home//.ssh
Then connect to the remote machine and install the public key by adding it to ~/.ssh/authorized_keys2: # cat id_dsa- >> authorized_keys2
Please note:

* authorized_keys2 shall not be world readable (chmod 600 authorized_keys2)
* If you decided to use rsa keys the public key has to be placed in authorized_keys

After having installed the public key on the remote machine log off.

If you use a key naming that is different from the default id_dsa/id_rsa it is required to instruct ssh about the key name. Therefore edit ~/.ssh/ config and add following line to it: IdentityFile=~/.ssh/id_dsa- Finally chmod the file as not world readable (chmod 600 config.

3. Testing ssh accesses

Test ssh with following command:
# ssh-v @ First thing to check: make shure you are asked for your passphrase, not your password
. In case of any trouble the debug display can be used for tracing the decisions made during the access (also see “Troubleshooting”).

4. Troubleshooting

4.1. Using debug mode on client and server

For troubleshooting ssh both client and server provide detailed tracing options:

* The ssh option -v traces details during the session establishment (e.g. selection of identity file)
* You can start the sshd server on an alternate port using the command sshd -p -d -D. In this mode the server displays important information at session begin

4.1. Common errors

* ~/.ssh and/or the private data as well as config file are world readable
* If using a non-standard identity filename is is not defined in ~/.shh/config (you can also try forcing the identity file using the -i ssh option.

To get more quality articles, technical guides and discussions visit WebHostingChat.com

Web Hosting Guide for Beginner

First and foremost, for non-IT savvy, it might be a little tough for them to comprehend the meaning of web hosting. I believe if you search it on any search engine, of course there will be answer and explanation for them. But, how far do you really understand? Honestly, when I first get to know this term few years back, I had problem understanding myself. Then, I found one simple explanation that might be easy for people to understand. So, today, if anyone were to ask me what is “web hosting”, i’d explain as follows…

Imagine you are homeless and you want to rent a room or buy a house. In order to get a shelter for yourself, you need a room. So, you imagine yourself as the website and the room as the hosting that you need to place yourself in. That means your website need a web hosting. Then, that’s the time you start finding yourself a web hosting provider. Here, web hosting provider would be the house owner who rents you the room. So, in order for your website to be available and browsed by Internet users, you need to make sure your website is hosted in a web server provided by a web hosting provider.

So, when you finally understand what web hosting is, next will be the time to find out more about the different types of web hosting available. You have shared hosting, dedicated hosting, reseller hosting, VPS hosting, and colocation hosting. You name it, the Internet has it! So many to remember and differentiate..so, let’s get the ball rolling with…

Shared Hosting

Shared hosting means that a web server has its resources shared by many other websites. Or you can put it as, in a house, there are many tenants. Usually small or normal e-commerce businesses will choose this type of hosting. Websites with high traffic might not be able to choose this type of hosting due to insufficient webspace.

Dedicated Hosting

Dedicated hosting refers to hosting in which you rent a server from your web hosting provider and will be placed at your web hosting provider’s datacentre. They will provide software installation and connection to Internet. This will indicates that the website owner has control over the server as they don’t share it with other websites. In short, dedicated hosting is where only 1 user hosted on the server machine and have a full privilege over the server to manage it by themself. The server machine will be still belongs to the web hosting provider.

Colocation Hosting

Well, this hosting has the features which are almost the same as dedicated hosting EXCEPT that you provide your own server and web hosting provider just help you to plug it into their datacentre. You need to install own software and hardwares. Everything is DIY.

Reseller Hosting

Reseller Hosting is a hosting where the account owner has the priviledge to allocate the webspace and bandwidth access and resell them to his clients. This shows that reseller hosts act like a middleman and is usually not responsible for any software or hardware intallation. They only buy webspace and resell to clients.

VPS Hosting

VPS stands for Virtual Private Server. It is almost the same as dedicated server. Hence, it’s sometimes called Virtual Dedicated Server. Generally, it means that the account owner has the feeling as though his owns a dedicated server. In real sense, it’s actually separating a physical server into several independent hosting spaces or VPS-es, each isolated from the other.This will allow you to create and manage multiple sites and domains and take full control of your VPS with root/administrator access which allows you to access the virtual hard disk, RAM and to reboot your private server independently from other VPS-es.

Domain Name

After we are done with the different types of hosting, there is something else which I want to touch on. It is none other than the “domain name”. So, ever wonder what is domain name? Wow, sounds technical? Not really actually. Don’t be scared. Last time, when I saw the words domain name, it freaked me out too. Now, when I got used to it, it’s not that nerve-wracking after all.

So, domain name is just the normal web address or url (Uniform Resource Locator) you type in the “address” area when you open a browser. Examples of domain name are “exabytes.com”. You know? Just the normal web address. Well, since it’s a web address, it’s a unique name. Hence, there will be no other same domain name. In fact, domain name is actually corresponding with numeric IP address. So, every domain name will have its numeric IP address. For example, the IP address for exabytes.com is 72.18.131.206

When you see exabytes.com, ever wonder “.com” stands for what? It actually stands for commercial. Whenever you see .com, .org, .net or others which ends after the final dot or period (.) of a url, it is known as top-level domain. It actually tells you what kind of website it is, indirectly. And the commonly used domain name extension nowadays will be .org, .net, .com. However, there are a lot of new domain extension up for grab lately such as .aero, .info, .museum, and .name. Next in the list that I shall explain is, Country Level Domain Name. Examples of country level domain name is exabytes.com.my. It has “.my” as its country code top-level domain (ccTLD). .my here represents the country “Malaysia”. Of course, different country will have different ccTLD. For example, .jp stands for Japan, .au for Australia, .ca for Canada.

There are more to learn in order to excel in web hosting industry. Hopefully this simple guide will help all those novice out there. There are other things you need to know as well. But, it will be in my next article.

Shared Hosting VS Dedicated Server

Are you at a crossroads now, deciding which type of hosting best suits your needs, a Shared Hosting or a Dedicated Server may be the answer. This is definitely an important decision as it will affect how your business will run on the webspace in the future. So, before you start submitting a ticket to the support department or calling the sales department of any hosting provider to ask regarding your confusion, take a look at the guidelines and tips which I’m about to introduce to you.

First of all, ask yourself, which type of web busineses are you planning to get involved in? Next, I’ll show you the advantages, disadvantages and features offered to you by both shared hosting and dedicated server hosting. Before I proceed further, let’s refresh your mind with the definition of both types of hosting. Shared hosting, as most of you should be well-versed, is hosting where a lot of websites share the same resources in one server. Resources here simply mean the total webspace, the memory, the processor speed, as well as the bandwidth.

Dedicated server on the other hand, give you the freedom of being alone. Alone means you are the sole owner of the server. You can do whatever you want and no other sites share the resources with you. It sure comes with a price as dedicated server is way more expensive than shared hosting. However, if you believe that the advantages which I shall be listing in a short while are the advantages you long to have, then it’s wise to conclude that these advantages can outweigh the expensive price (but still affordable) of dedicated server.

Facing the challenges in the world of sharing!

Here’s a simple analogy; renting a room on your own or finding a roommate to share the room with you. Simply, that’s the problem or risks you might be facing when you opt for shared hosting. Shared hosting is just like you rent a room with a few other roommates. Won’t it be congested to share in a small room? However, there is a reason why people choose to find roommates. Price is the main concern. Same goes to hosting industry.

Shared hosting is cheaper and more affordable compared to dedicated hosting. Nowadays, you can find shared hosting with the price of USD4 to USD15 per month. Therefore, if you think that price is an issue and you are still green in hosting world and your online business has yet to achieve heavy traffic, the best solution is to go for shared hosting first. Consequently, you have to bear the drawbacks of shared hosting but if you choose a reliable and experienced hosting provider (probably in a hosting industry for around 3-4 years), the provider will ensure the most minimal drawbacks for its clients. In shared hosting environment, you will encounter certain disadvantages as follows:

Sharing Same IP

Having the same IP address in shared hosting is the main concern when other sites in the server is actually being blacklisted for unethical activities such as spamming or generating illegal script. Since, you share the same server, it’s obvious you will share the same IP address. So, when other sites are blacklisted, those sharing the same IP with them will also unfortunately share the same fate – being banned alltogether by search engine. You will be the victim of crime which you don’t commit. However, there are times where you can buy yourself a dedicated IP but this usually is not needed unless you are getting yourself an SSL certificate. In cases such as this one, it depends on your hosting provider on how they deal with clients who do illegal and unapproved activities. Usually, a reliable and responsible host will suspend those sites which perform spamming in order to rescue other sites who are innocent. In short, to get yourself a shared hosting, get to know how your provider deal with those sites which are hosted in the same server as you.

Slow Server Response Time

Using the same analogy as above, if you and your roommates want to use the bathroom, you have to queue up, correct? Hence, it will slow down your daily work. Same goes to shared hosting. If one of your neighbours have heavy daily traffic, it will consume most of the bandwidth and when things get tighten up, you will feel the slow response time such as difficulty accessing your website. This is because server will respond to the requested file in order of the queue. If one of the visitor happens to request it later and is on a long queue, that visitor will experience slow response time and might eventually end up leaving your website.

Server Crashes Regularly

The factor to server crashes more often than usual, is the fact that certain scripts are generated and it can overload a server’s resources. If webhosting provider does not monitor the server’s activity, those poorly-written CGI script can give you more headache than relief. Hence, it’s vital for host provider to monitor the server regularly to prevent server from crashes and to protect your site from being affected. You as a client, please do take the initiative to question your providers on how they take precautions for cases like this one. A well-knowledgable and reliable host provider will be able to answer your question to your satisfaction.

Despite aforementioned bad points, a lot of websites also use this shared hosting solution and if a proper provider is chosen, you can be assured that such incidents will barely happen.

Dedicated Hosting – A world of your own

What makes people opt for dedicated hosting instead of shared hosting? Again, the most important criterion is money. If you can afford a costly solution like this, go ahead. However, don’t just simply go ahead without weighing the pros and cons of dedicated hosting. Even if you have money, and you are just a small medium enterprise, think twice for investing in dedicated hosting. Reason is because dedicated hosting is mainly for large and busy sites such as portal, search engine, online content provider, heavy traffic forums and etc. In addition, dedicated hosting usually requires more technical-savvy specialist to monitor it. Listed below are some of the advantages why dedicated hosting is a popular option:

You are the boss!

Here, it means you have more control of everything. You can install whatever applications and scripts you want. You can do script testing and if anything were to happen, no one else to blame but yourself. You will have the ability to customise the hardware and softwares installed on your server, which you cannot find this priviledge if you are under shared hosting.

No more limitation in bandwidth usage

Compare to shared hosting, you might get yourself a “warning letter” from your hosting provider if you exceed the maximum bandwidth allocated to you. With dedicated hosting, you have the amount of bandwidth of a server. Hence, downloading and uploading any materials from your site will not be a problem if you have a lot of daily visitors performing such activity.

More Secured

Having a dedicated server is in fact more secured compared to shared hosting. This is because dedicated server will be provided its own firewall. Therefore, the information stored in dedicated server is less vulnerable to attacks by hackers or any malicious codes. In addition, hosting provider will usually provide backup for you with added fee, but, in terms of security, it’s actually worth it.

Better Performance

Since dedicated hosting means only you alone are hosted in that server, the response time of the server to requested files will be so much faster compared to shared hosting. Visitors who browse your website will feel happy because your pages will appear on their browser fast enough to satisfy them. Fast loading time will always brighten anyone’s day!

Generally, choosing which type of hosting solely depends on your needs. So, to make a wise decision, do more researches and evaluations as well as consult those highly technical savvy people. A Shared Hosting or a Dedicated Server may be the solution. Remember that a good and smart decision will determine your online storefronts’ success.

How to install Cpanel

How to install Cpanel

Here are short and simple about installing Cpanel on your server,

Make sure you are login to your server as root user.

1. Log into your server as root via the console or SSH.
2. Ensure your resolvers are working by trying to resolve cPanel Inc.
nslookup cpanel.net
3. Change directory into your /home.
cd /home
4. Download cpanels installer from layer1.cpanel.net/latest.
wget layer1.cpanel.net/latest
5. Now run the installer using sh or bash.
sh latest

You are done! :)