Save below code in ioncubein.sh save it anywhere in root & run the shell script to install Ioncube automatically

#!/bin/sh

clear
echo “Installing ioncube. Please wait…”
wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.zip &>/dev/null
unzip ioncube_loaders_lin_x86.zip &>/dev/null
rm ioncube_loaders_lin_x86.zip &>/dev/null
mv ioncube /usr/src/ioncube &>/dev/null
sed -i ‘3s/.*$/zend_extension = \/usr\/src\/ioncube\/ioncube_loader_lin_5.2.so\n\n&/g’ /etc/php5/apache2/php.ini &>/dev/null
/etc/init.d/apache2 force-reload &>/dev/null
clear
echo “Done. Ioncube loaders have been successfully installed.”
echo “Visit http://www.version-next.com if you have any questions.”

In this tutorial, we are aiming to accomplish several things:

* We’re going to install the Ubuntu Server operating system. I commonly use Ubuntu because of its ease of use and simple administration. It also has a rather large and extremely active community behind it, which makes getting support a breeze.
* We’re going to install an OpenSSH server. This allows you to administer your server from remote computers.
* A LAMP (Linux, Apache, MySQL, and PHP) stack is going to be installed. This provides the backbone that will run your web site. Apache is the industry standard web server on Unix-based operating systems; it’s what most web hosts use (DT.N is using it right now!) and it’s what we’re going to use.
* We’re going to install a firewall to protect your server from unauthorized access.

In order to follow this tutorial, you’re going to need a few items:

* A computer to use as your server. It doesn’t need to be powerful; as long as it’s not ancient, it’ll work fine. Please don’t do this on your desktop PC; Ubuntu will completely wipe your computer.
* A CD burner and a blank CD. These are so that you can burn Ubuntu to a disk in order to install it.
* Time. Seriously, this process is time-consuming, especially if you run into problems. Try to set aside an afternoon to follow this tutorial.

You may be asking why you’d want to have your own web server. There are several reasons, a few of them being: you can have your own testing ground for your websites; with a little modification, you could host your own site; and, you will learn a lot about Linux/Unix as you go. With that said, let’s get started!

Download Ubuntu Server

First and foremost, we’re going to need a CD with Ubuntu on it. Point your web browser to http://www.ubuntu.com/, and click download from the menu to the left. You will now be presented with a box with two tabs: “Desktop Edition” and “Server Edition”. Click the “Server Edition” tab, and select “Ubuntu 8.04 LTS”. Next, select a download location from the drop-down box. Finally, hit the “Begin Download” button.

( I THINK THERES A NEW VERSION OUT )

Now you need to burn the ISO (the file that you downloaded) to a blank CD. If you don’t know how to do this, there is an excellent guide at https://help.ubuntu.com/community/BurningIsoHowto

Install Ubuntu Server

Now that you’ve downloaded and burned the ISO, let’s get Ubuntu installed on your server. Put the disk in the drive, and boot from the CD. In most modern computers, this will happen by default if a disk is in the drive when you turn it on. If it doesn’t, then you need to press a key on your keyboard right when you turn it on. For my laptop, it’s F12, and for my server, it’s F2. It just depends on your computer. You can find it by looking at the text on your screen right when you turn the computer on, during the BIOS. You’ll see something like “Press [KEY] to change boot order”. Press that key, and select your CD drive.

Still with me? Good. Now that you’ve booted up Ubuntu, you should see the following screen:

Select your language, and hit enter. Now you’ll see this screen:

Select “Install Ubuntu Server”, and away we go!

The installer will now ask you if you want it to detect your keyboard layout. Personally, I always choose no, because it’s faster to select a standard american keyboard from the list than to have the installer detect it. Either option is fine, just follow the on-screen instructions.

After you’ve done that, you’ll now see a bunch of loading screens saying things like “Detecting CD-ROM drives” and such. These should pass quickly and without problems. However, during these screens, the installer will try to auto-configure your network settings. For most cases, this will work without complaint. However, if it doesn’t work for you, just follow the on-screen instructions to get it working.

After it’s done with all of that, it will ask you for a host name. You can usually set this to anything; I always set mine to “web-server”.

The system will now want you to set the time zone for your clock. For me, it’s Pacific. Choose the one that applies to you.

Now, the system will detect more hardware, and you’ll be prompted to “partion the disk(s)”. Select “Guided – use entire disk”.

You will now need to select the disk you wish to partition. For most setups, only one disk will be available; however, for more specialized systems, more options will be available here. Choose the one that applies to you.

It will ask you if you want to write the changes to the disk. Select “Yes” and hit enter. The installer will now proceed to format the drive and set up the partitions.

Now the magic happens. The system will begin to install. While this happens, go get a cup of coffee. This can take anywhere from 10 minutes to an hour. It just depends on your system. There might be times that it seems like it’s frozen; don’t worry, it isn’t. Just let it do it’s thing. However, if it’s stuck on one thing for upwards of an hour, then yes, it is frozen.

Now that the system is installed, it needs to set up the account you are going to login with. First, give it your full name and hit “Continue”.

Now give it your username. It will normally just set it as your first name, but you can change it. One name you may not use is “root”.

You will now be asked to provide a password. It is ESSENTIAL that you choose a strong password, or your server will not be secure at all. I recommend at LEAST a mixture of numbers, lowercase letters, and uppercase letters. However, for my servers I use symbols, as well as a mixture of the above. DO NOT use a password shorter than 7 characters.

Then, re-enter your password to verify that you typed it correctly.

The system will now attempt to configure the “Package Manager” (we’ll get to what that is shortly). Provide it with your proxy information, or leave it blank if you don’t use a proxy, and select “Continue”.

The system will now scan several servers looking for updates and configuration settings.

After that has completed, you will be presented with several options to install server software. Now, listen VERY carefully. Select OpenSSH server, and press SPACE, NOT ENTER. If you hit enter, the install will proceed without installing the OpenSSH server. You could install “LAMP server” as well, but I have no experience with this option, so we’re going to install it all with a different command later on.

The system will now install your selected software, as well as other system components.

Finally, the install will finish. Remove the CD, and hit enter. The computer will reboot. If all goes well, you will be presented with a screen that looks similar to the following:

Congratulations! You’ve just finished the hardest part. Ubuntu is now installed, and it is time to turn this computer into a web server.

Update Your New Server

Before we go any further, we need to make sure your server is up-to-date. To do this, you need to login. First, type your username (the one you chose earlier), press enter, and then type your password. As you’re typing your password, you’ll notice that nothing seems to be happening. Don’t worry, that’s the way it was designed to work. After you’ve finished typing your password, hit enter, and your screen should look similar to the one below if all went well:

Now, type:

sudo aptitude update && sudo aptitude dist-upgrade

It will ask you for you password, and again, you won’t see anything as you’re typing it. After you’ve done that, it will ask you if you want to continue. Type “y” and press enter. Your screen will look similar to the following:

Your system will now download and install all the latest updates. This will take a while depending on your internet connection. After it has finished, your computer will need to be rebooted. To do this, type:

sudo shutdown -r now

And let it reboot. Your server is now completely updated.

A Quick Note About “Sudo”

By now, you may have noticed that all of the commands you have typed have started with “sudo”. This is because they require administrator privileges, and that’s what “sudo” does. It runs the command (i.e. “shutdown”) as an administrator, allowing it to work properly. This is also why it asks you for your password. However, after you have typed “sudo” once and entered your password, you do not have to enter your password again for five minutes. Not all commands require sudo, only ones that modify parts of the system. Got all of that? Good.
Install Apache, MySQL, and PHP

It is now time to install some programs. In order to access your sites from the internet, we’re going to need to install a web server (Apache). In additon to the web server, we’ll also want a database server (MySQL) and a server-side language (PHP) so that we can run popular applications such as WordPress. So, let’s get to it!

Installing programs on Ubuntu is a lot different than installing programs on Windows or OS X, in that Ubuntu will download and install the programs for you with a simple command. This is because Ubuntu has something called a Package Manager, which manages nearly all the programs on your system. All we have to do is tell the package manager (called “aptitude”) that we want it to install Apache, MySQL, and PHP. To do this, type the following command:

sudo aptitude install apache2 php5-mysql libapache2-mod-php5 mysql-server

And press enter. Aptitude will download and install of the programs you specified. It will also download and install any dependencies.

During the install process, MySQL will ask you for a root password. You can set this to anything, just be sure you make it long and secure. Whatever you do, DO NOT leave this blank.

After that has all finished, you now have a fully working web server. To test it out, first find your server’s IP by typing:

ifconfig | grep inet

It’s usually the first IP returned. In my case, it’s 192.168.177.129. Now that you know the IP, open your web browser and point it to your server IP. If you see the “It works!” message, then congratulations, it works.

However, we’re not done yet. We don’t want Apache or PHP to disclose any information about themselves, as this information is not needed by your users and could pose a security risk. First, back up the original Apache configuration file:

sudo cp /etc/apache2/apache2.conf /etc/apache2/apache2.conf.bak

Now open the configuration file:

sudo nano /etc/apache2/apache2.conf

Scroll down (down arrow) to where it says “ServerTokens Full” and change it to read “ServerTokens Prod”

Now, scroll down a little further and change “ServerSignature On” to “ServerSignature Off”

Finally, press Control-O followed by Control-X. That will save the file and exit the text editor.

Now, we need to do the same thing for PHP. First, back up the original PHP configuration file:

sudo cp /etc/php5/apache2/php.ini /etc/php5/apache2/php.ini.bak

Open the configuration file:

sudo nano /etc/php5/apache2/php.ini

Change “expose_php = On” to “expose_php = Off”

Again, press Control-O followed by Control-X. Now that the configuration files are updated, restart Apache:

sudo /etc/init.d/apache2 restart

You are done setting up Apache, MySQL, and PHP.

Install a Firewall

We now are going to lock down our server a bit more by installing Shorewall, a command-line firewall. To install it:

sudo aptitude install shorewall

By default, Shorewall is installed with no rules, allowing complete access. However, this is not the behavior we want. Instead, we’re going to block all connections to anything other than port 80 (HTTP) and port 22 (SSH). First, copy the configuration files to the Shorewall directory:

sudo cp /usr/share/doc/shorewall-common/examples/one-interface/* /etc/shorewall/

Now, open the “rules” file:

sudo nano /etc/shorewall/rules

Add these lines above where it says “#LAST LINE”

HTTP/ACCEPT net $FW
SSH/ACCEPT net $FW

Then press Control-O and Control-X. Your firewall is now configured to only accept HTTP and SSH traffic. The last thing we need to do is tell Shorewall to start on boot. So, open up the main Shorewall configuration file:

sudo nano /etc/shorewall/shorewall.conf

Scroll down to “STARTUP_ENABLED=No” and set it to “STARTUP_ENABLED=Yes”

Press Control-O and Control-X. Now, open the Shorewall default configuration file:

sudo nano /etc/default/shorewall

And change “startup=0″ to “startup=1″. Press Control-O and Control-X. Finally, start your firewall:

sudo /etc/init.d/shorewall start

Congratulations! Your firewall is now set up and protecting your server.
Add Your Website to Your Web Server

Now that you’ve got everything all set up, you’d probably like to add a website to it. By default, all of the files Apache serves up to the internet are located at “/var/www/”. However, you cannot write to this folder. Let’s make it so you can:

sudo usermod -g www-data [YOUR USERNAME]
sudo chown -R www-data:www-data /var/www
sudo chmod -R 775 /var/www

What happened there was you added yourself to the “www-data” group, and made the website folder writable to the members of the “www-data” group.

Now, you’re going to log into your server using SFTP (not to be confused with FTPS). Some clients that support SFTP are: WinSCP (Windows, Free), FileZilla (Windows, Linux, OS X, Free), Cyberduck (OS X, Free), and, my personal favorite, Transmit (OS X, $30)

Connect to your server using your username and password, and, if your client supports it, a default path of “/var/www” (if it doesn’t, simply browse to /var/www once you have logged in): (Transmit pictured)

You may now add your files to this folder (/var/www) and they will show up on your server when you browse to it with your web browser.

Now, you may wonder why we’re using SFTP instead of FTP. Mainly, because SFTP is already built into OpenSSH (which you installed earlier). However, it is also a lot more secure than FTP, and makes it difficult (if not impossible) for malicious users to gain access to your login credentials.

Make Your Server Accesible to the Internet

Most modern home networks are behind a router these days. Because of this, your web server will not be visible to the internet without a little work. As I don’t have every router available to test with, I can only give you general directions in this area.

There are two ways to open your server up to the internet: a DMZ or Port Forwarding. The main difference you’ll notice is that with a DMZ, your server uses the firewall we installed earlier to protect itself. However, with Port Forwarding, your server will be protected by your router’s firewall.

However, before we go on, you’re going to want to give your server a static LAN address. To do that, login to your router, and look for something along the lines of “Static IPs” or “Static Routing”. After you have given your server a static LAN address, you can do these next parts. Remember, Google is your friend.

To port foward, there is an excellent website, PortForward.com, that, while ugly, can help you get the job done for almost any router. The ports that you want to forward are 22 and 80.

To create a DMZ, you need to login to your router and look for something like “DMZ settings”. Once you find it, add your server to the DMZ, and you’ll be set. Again, Google is helpful in situations like this.

Now, find your public IP, and voila! You can access your server from anywhere as long as your IP doesn’t change.
Managing Your Server Remotely

Beside allowing you to upload files, OpenSSH allows you to login to your server from anywhere as long as you know it’s IP. For Windows, you’ll need an SSH client. I recommend Putty. For OS X, SSH is already installed. Simply open up Terminal, and type “ssh you@yourip”. For Putty, choose SSH, and put in your IP, username, and password when it asks for it. You’ll notice that, once you login, it looks exactly the same as the screen on the server:

You can do anything from here that you would do actually sitting at the server. To logout from the server, simply type “exit” and hit enter.
That’s It!

You now have a completely functioning web server. It makes for a great testing ground, and would even be suitable to host websites with fairly low traffic. There is obviously a lot left to be learned, but hopefully you have gained a little insight into how web servers work.

Hope you have fun.  leave comment 

A dedicated hosting service, dedicated server, or managed hosting service is a type of Internet hosting in which the client leases an entire server not shared with anyone. This is more flexible than shared hosting, as organizations have full control over the server(s), including choice of operating system, hardware, etc. Server administration can usually be provided by the hosting company as an add-on service. In some cases a dedicated server can offer less overhead and a larger return on investment. Dedicated servers are most often housed in data centers, similar to colocation facilities, providing redundant power sources and HVAC systems. In contrast to collocation, the server hardware is owned by the provider and in some cases they will provide support for your operating system or applications.

Operating system support

Availability, price and employee familiarity often determines which operating systems are offered on dedicated servers. Variations of Linux (open source operating systems) are often included at no charge to the customer. Commercial operating systems include Microsoft Windows Server, provided through a special program called Microsoft SPLA. Red Hat Enterprise is a commercial version of Linux offered to hosting providers on a monthly fee basis. The monthly fee provides OS updates through the Red Hat Network using an application called yum. Other operating systems are available from the open source community at no charge. These include CentOS, Fedora Core, Debian, and many other Linux distributions or BSD systems FreeBSD, NetBSD, OpenBSD.

Support for any of these operating systems typically depends on the level of management offered with a particular dedicated server plan. Operating system support may include updates to the core system in order to acquire the latest security fixes, patches, and system-wide vulnerability resolutions. Updates to core operating systems include kernel upgrades, service packs, application updates, and security patches that keep server secure and safe. Operating system updates and support relieves the burden of server management from the dedicated server owner.

Bandwidth and connectivity

Bandwidth refers to the data transfer rate or the amount of data that can be carried from one point to another in a given time period (usually a second) and is often represented in bits (of data) per second (bit/s). For example, visitors to your server, web site, or applications utilize bandwidth as the traffic moves from your server to the Internet and vice versa. Connectivity refers to the “access providers” that supply bandwidth, or data transfer rate, through various connection points across a network or footprint to one or multiple data centers where dedicated servers are housed.

Bandwidth measurements are defined (per telecom standards) as the following:

• First – 95th (measured using average bits and speed of transfer)
• Second – Unmetered (measured in speed or bits)
• Third – Total Transfer (measured in bytes transferred)

95th Method: line speed, billed on the 95th percentile, average or peak usage, refers to the speed in which data flows from the server or device. Line speed is measured in bits per second (or kilobits per second, megabits per second or gigabits per second).

Unmetered Method: The second bandwidth measurement is unmetered service where providers cap or control the “top line” speed for a server. Top line speed in unmetered bandwidth is the total Mbit/s allocated to the server and configured on the switch level. For example, if you purchase 10 Mbit/s unmetered bandwidth, the top line speed would be 10 Mbit/s. 10 Mbit/s would result in the provider controlling the speed transfers take place while providing the ability for the dedicated server owner to not be charged with bandwidth overages. Unmetered bandwidth services usually incur an additional charge.

Total Transfer Method: Some providers will calculate the Total Transfer, the measurement of actual data leaving and arriving, measured in bytes. Measurement between providers varies and includes one of the following equations:

• Method 1: IN TRAFFIC + OUT TRAFFIC = TOTAL TRANSFER
• Method 2: IN TRAFFIC = TOTAL TRANSFER
• Method 3: OUT TRAFFIC = TOTAL TRANSFER

One of the reasons for choosing to outsource dedicated servers is the availability of high powered networks from multiple providers. As dedicated server providers utilize massive amounts of bandwidth, they are able to secure lower volume based pricing to include a multi-provider blend of bandwidth. To achieve the same type of network without a multi-provider blend of bandwidth, a large investment in core routers, long term contracts, and expensive monthly bills would need to be in place. The expenses needed to develop a network without a multi-provider blend of bandwidth does not make sense economically for hosting providers.

Many dedicated server providers include a service level agreement based on network uptime. Some dedicated server hosting providers offer a 100% uptime guarantee on their network. By securing multiple vendors for connectivity and using redundant hardware, providers are able to guarantee higher uptimes; usually between 99-100% uptime if they are a higher quality provider. One aspect of higher quality providers is they are most likely to be multi-homed across multiple quality uplink providers, which in turn, provides significant redundancy in the event one goes down in addition to potentially improved routes to destinations.

Bandwidth consumption over the last several years has shifted from a per megabit usage model to a per gigabyte usage model. Bandwidth was traditionally measured in line speed access that included the ability to purchase needed megabits at a given monthly cost. As the shared hosting model developed, the trend towards gigabyte or total bytes transferred, replaced the megabit line speed model so dedicated server providers started offering per gigabyte.

Prominent players in the dedicated server market offer large amounts of bandwidth ranging from 500 gigabytes to 3000 gigabytes using the “overselling” model. It is not uncommon for major players to provide dedicated servers with 1Terabyte (TB) of bandwidth or higher. Usage models based on the byte level measurement usually include a given amount of bandwidth with each server and a price per gigabyte after a certain threshold has been reached. Expect to pay additional fees for bandwidth overage usage. For example, if a dedicated server has been given 3000 gigabytes of bandwidth per month and the customer uses 5000 gigabytes of bandwidth within the billing period, the additional 2000 gigabytes of bandwidth will be invoiced as bandwidth overage. Each provider has a different model for billing. As of yet, no industry standards have been set.

Management

To date, no industry standards have been set to clearly define the management role of dedicated server providers. What this means is that each provider will use industry standard terms, but each provider will define them differently. For some dedicated server providers, fully managed is defined as having a web based control panel while other providers define it as having dedicated system engineers readily available to handle all server and network related functions of the dedicated server provider.

Server management can include some or all of the following:

• Operating system updates
• Application updates
• Server monitoring
• SNMP hardware monitoring
• Application monitoring
• Technical support
• Firewall services
• Antivirus updates
• Security audits
• DDoS protection and mitigation
• Intrusion detection
• Backups and restoration
• Disaster recovery
• DNS hosting service
• Load balancing
• Database administration
• Performance tuning
• Software installation and configuration
• User management
• Programming consultation

Dedicated hosting server providers define their level of management based on the services they provide. In comparison, fully managed could equal self managed from provider to provider.

Administrative maintenance of the operating system, often including upgrades, security patches, and sometimes even daemon updates are included. Differing levels of management may include adding users, domains, daemon configuration, or even custom programming.

Dedicated server hosting providers may provide the following types of server managed support:

• Fully Managed – Includes monitoring, software updates, reboots, security patches and operating system upgrades. Customers are completely hands-off.
• Managed – Includes medium level of management, monitoring, updates, and a limited amount of support. Customers may perform specific tasks.
• Self Managed – Includes regular monitoring and some maintenance. Customers provide most operations and tasks on dedicated server.
• Unmanaged – Little to no involvement from service provider. Customers provide all maintenance, upgrades, patches, and security.

Note: The provider will continue to maintain security on the network regardless of support level.

Security

Dedicated hosting server providers utilize extreme security measures to ensure the safety of data stored on their network of servers. Providers will often deploy various software programs for scanning systems and networks for obtrusive invaders, spammers, hackers, and other harmful problems such as Trojans, worms, eggdrops and crashers (Sending multiple connections). Linux and Windows use different software for security protection.

Software

Providers often bill for dedicated servers on a fixed monthly price to include specific software packages. Over the years, software vendors realized the significant market opportunity to bundle their software with dedicated servers. They have since started introducing pricing models that allow dedicated hosting providers the ability to purchase and resell software based on reduced monthly fees.

Microsoft offers software licenses through a program called the Service Provider License Agreement. The SPLA model provides use of Microsoft products through a monthly user or processor based fee. SPLA software includes the Windows Operating System, Microsoft SQL Server, Microsoft Exchange Server, Microsoft SharePoint and shoutcast hosting, and many other server based products.

Dedicated Server Providers usually offer the ability to select the software you want installed on a dedicated server. Depending on the overall usage of the server, this will include your choice of operating system, database, and specific applications. Servers can be customized and tailored specific to the customer’s needs and requirements.

Other software applications available are specialized web hosting specific programs called control panels. Control panel software is an all inclusive set of software applications, server applications, and automation tools that can be installed on a dedicated server. Control panels include integration into web servers, database applications, programming languages, application deployment, server administration tasks, and include the ability to automate tasks via a web based front end.

Most dedicated servers are packaged with a control panel. Control panels are often confused with management tools, but these control panels are actually web based automation tools created to help automate the process of web site creation and server management. Control panels should not be confused with a full server management solution by a dedicated hosting provider.

Limitations

Many providers do not allow IRC (bots, clients or daemons). This is due to rogue IRC users triggering DDoS attacks against the provider, which may overwhelm their networks, lowering service quality for all customers.

• Adult content is disallowed by many providers as it may either be of questionable legality or consume large amounts of bandwidth.
• Copyright violation Hosting copyrighted material of which you do not own the copyright to is almost always against the terms of service of all hosting companies.

Article SOURCE WIKI