LAMP installation and configuration steps

I was able to conect Centos6 on Virtual Box to Windows (I am able to ping in both directions) with Host-only Adapter (for connection between the two) and NAT Adapter (to enable Linux on VB to connect to the Internet). I want to set up httpd, mysql and vsftpd servers and in the end easily connect to httpd from Windows based browser and ftp server with a Windows based client as well. I would also want to have access through SSH.

I have a general idea of the steps that are involved, but there is also a configuration that I am not sure about at this point. Lets say I follow these steps:

yum install httpd

yum install php php-pear php-mysql

yum install mysql-server


yum install vsftpd

yum install mod_ssl

Technically, I have everything installed, but what would be the next steps that I need to take (from the networking point of view, so to speak) to get it all working?

I know I need to configure, at least Apache, and ftp server, but I am not sure how is it gonna work; like where am I gonna be uloading the sites (I know this can vary), how am I gonna know what address to use in a browser if I wanna go to a website x, y, z on that installation etc. This sounds like I need to do some kind of DNS setup and I am kind of stuck at this point.

If somebody could give me a general outline of what are the things that need to be done that would be great (I was looking at a lot of websites and I know about etc/sysconfig/network, httpd.config - not too much abot it on Apache’s site, hostname, hostname -f etc; but it is kind of hard to piece it all together at this point). I am gonna be looking at the books also, but they not always reflect the setup that I have too (VirtualBox).

Thank you.

Mmm, well I’m not sure you’re doing yourself any favours picking CentOS and virtualbox, but that aside;

“ifconfig” should list the network connections on your CentOS box … I’d be expecting to see to interfaces with different addresses, one will ping from Windows and one won’t … the one that pings is the one you’re going to be sticking your websites on.

The way you will want to access Apache is via HTTP/1.1, which lets Apache listen on a single IP address, but respond differently based on the domain name you use in your browser. Your config should be in /etc/apache[2] and be called apache.conf, httpd.conf, or similar. (this is so much easier on Debian/Ubuntu!)

For each of the sites you want to host, you’ll need a config section something like this;

<VirtualHost *:80>
        CustomLog       /var/log/apache2/linux.log combined
        ErrorLog        /var/log/apache2/error.linux.log
        DocumentRoot    /home/linux/htdocs/

Then, on your Windows PC, find the “hosts” file and add a like like so;

<ip address> <domain name> [..<domain name>]

I think from memory it lives in \Windows\System32\drivers\etc\ …
… then in this example, in your browser, “” would take you to your local CentOS hosted site …

I read somewhere that I should be able to connect to the guest (Linux) with Putty. I tired and I was not able to. I also looked at all the network configuration info (ipconfig /all and ifconfig) and that information has changed also. I keep making screenshots, because it is hard to keep track of it when I am not sure how is it suppose to work (pictures are here

After the installation I was using (I think) to ping host (Windows) from Linux and the other way.
Today I think it should be (ping from Linux) and (the same, ping from Windows to Linux). So it gets confusing quickly.
Based on above information I was trying to use Putty with as an address and that did not work…

(Host-only network is basically the network that needs to connect Windows and Linux)

Don’t know if this will help … but I have noticed in the past that Windows tends to assign IP’s in the range to interfaces when it’s not sure what address it should assign (eg. when it’s expecting to get as IP from a DHCP server but doesn’t) … and surely the IP of the Vbox Host-Only adapter shouldn’t change like that … so my guess would be the problem is in Vbox or DHCP somewhere.