10

I've been trying to set up a CentOS server for the first time (ever setting up a Linux server). The installation went fine, I installed LAMPP (and the required dependencies for x86), used the lampp security tool, and went to http://192.168.0.112:8888/ using elinks.

So far so good... But then I wanted to access the server from the other computers in my network (including the host of the VM). But I can't get it to work and keep getting 404's...

Note that I have another webserver running on this network (on port 80), so I changed Listen 80 to Listen 8888 in httpd.conf and forwarded 8888 in my router to the IP from the CentOS installation (static: 192.168.0.112, according to ifconfig).

Ping 192.168.0.112 returns:

Ping statistics for 192.168.0.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Server details:

  • CentOS 6.5 minimal, installed from .iso
  • LAMPP 1.8.1 (via wget from apachefriends.org)

Host details:

  • Windows 8.1 x64
  • VirtualBox is using a Bridged Network Adapter (translated from Dutch: Netwerk bridge adapter)

Any ideas on how to fix this issue? I'm relatively new to networking and server as I'm a front-end developer myself, but I really want to get into back-end stuff.

It's getting really late now, so I'm off to bed. Hopefully I get some good insights in how networking/CentOS works in the morning!

Thanks in advance.

Cas Cornelissen
  • 248

4 Answers4

15

I also had this issue. From your description I was running the same set up as you. It turned out I had firewalld installed and was running and so had to use the commands:

sudo firewall-cmd --permanent --zone=public --add-service=http
sudo firewall-cmd --permanent --zone=public --add-service=https
sudo firewall-cmd --reload

This then enabled me to access the apache server running on my virtual machine from outside of the vm.

Jakuje
  • 10,827
George
  • 151
3

Run the following commands:

iptables -I INPUT -i eth1 -p tcp -m tcp --dport 80 -j ACCEPT

To make the changes persist, go to /etc/sysconfig/ and add to the following line to iptables:

-A INPUT -i eth1 -p tcp -m tcp --dport 80 -j ACCEPT

Then, restart the webserver:

service httpd restart

And now you can access out of VirtualBox.

Indrek
  • 24,874
Ricardo Pestana
  • 31
0

More than likely is a virtualhost configuration inside apache. There is a section in there that will say "allow from [something]". Make sure it says "allow from all".

Here is what mine looks like;

<Directory /var/www/>
    Options FollowSymLinks
    AllowOverride AuthConfig FileInfo Limit
    Order allow,deny
    allow from all
</Directory>

My personal opinion is to not use xampp at all. You are actually making things more difficult. Just use the native packages in CentOS. Here is a good tutorial (from a quick google search)

https://www.digitalocean.com/community/articles/how-to-install-linux-apache-mysql-php-lamp-stack-on-centos-6

Or, you can install Ubuntu Server and there is an option during the install phase that you can check to install LAMP. It will download and install all of the packages for you.

Good luck.

Linuxx
  • 161
0

It sounds like you forwarded traffic on your router to 192.168.0.112 when really you wanted 192.168.0.112:8888. It would be helpful to know some more about what computers you can and cannot ping the CentOS machine from, how your router is configured to forward ports to it, and what the contents of /etc/httpd/conf/httpd.conf are.

Also, it shouldn't matter that you have another webserver on this network, unless you're routing out to another network that you want to be able to access this webserver and both webservers will have the same external IP.

If this is the case, then say your "external" ip is 10.10.10.10 and the internal IP of this router is 192.168.0.1. Assume your CentOS webserver is at 192.168.0.112 as described, and your other server is at 192.168.0.110 and is hosting a webserver at port 80.

Because you wanted 192.168.0.110 to be able to serve HTTP traffic to devices on 10.10.10.*, you forwarded 10.10.10.10:80 to 192.168.0.110. However, this doesn't mean you have to serve web traffic on port 8888 from 192.168.0.112. Only if you would like to access 192.168.0.112 from devices that need to route through 192.168.0.1 do they need a port besides 80. So in this case, you would keep 192.168.0.112 serving web pages on port 80 and forward traffic inbound from 10.10.10.10:8888 to 192.168.0.112:80.

Finally, the fact that you're getting 404 messages in a browser means you're hitting some kind of webserver:

The 404 or Not Found error message is a HTTP standard response code indicating that the client was able to communicate with the server, but the server could not find what was requested. (Wikipedia)

ndt
  • 198