Can't access Apache in my CentOS Virtualbox

5,321

You have copy pasted the iptables rules? If yes then there is an error in it:

 _I OUTPUT -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT

the underscore insted of hyphen.

Share:
5,321

Related videos on Youtube

user1045696
Author by

user1045696

Updated on September 18, 2022

Comments

  • user1045696
    user1045696 almost 2 years

    I'm setting up a VirtualBox with CentOS so I can test out all my code, etc. on a Linux box instead of the Windows I use for development.

    I just got the SSH working (I SSH to localhost:2222 and it port forwards it to the virtualbox port 22).

    It's using NAT because for some reason it refuses to start with a bridged adapter.

    I'm trying to do the same thing with Apache, to get a web server up and running.

    I've portforwarded port 8888 on localhost to port 80 in my CentOS Virtualbox, but I can't seem to access anything with localhost:8888 in my browser?

    Apache is also definitely running:

    ps -e | grep httpd
    2108  ?      00:00:00 httpd
    2110  ?      00:00:00 httpd
    2111  ?      00:00:00 httpd
    2112  ?      00:00:00 httpd
    2113  ?      00:00:00 httpd
    2114  ?      00:00:00 httpd
    2115  ?      00:00:00 httpd
    2116  ?      00:00:00 httpd
    2117  ?      00:00:00 httpd
    

    Iptables:

    # Generated by iptables-save v1.4.7 on Fri Jan 27 18:26:36 2012
    *filter
    :INPUT ACCEPT [0:0]
    :FORWARD ACCEPT [0:0]
    :OUTPUT ACCEPT [32:2278]
    -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
    -A INPUT -p icmp -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
    -A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
    -A INPUT -j REJECT --reject-with icmp-host-prohibited
    -A FORWARD -j REJECT --reject-with icmp-host-prohibited
    -I INPUT -p tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT
    -I OUTPUT -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT
    -I INPUT -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT
    -I OUTPUT -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT
    COMMIT
    # Completed on Fri Jan 27 18:26:36 2012
    

    I've also stopped iptables, so that's not interfering. I tried to telnet into port 80 from my CentOS Virtualmachine to see if it'd work, and Neither 127.0.0.1 or [vm ip] works for telneting to port 80. It gets to connecting to [ip] and then says connection closed by foreign host. For the listen lines in my httpd.conf, it says listen 0.0.0.0:80

    Output of netstat -tlnp | grep http

    netstat -tlnp | grep http
    tcp        0      0 0.0.0.0:80                       0.0.0.0:*                        LISTEN      2032/httpd
    tcp        0      0 :::443                      :::*                        LISTEN      2032/httpd
    

    When I nmap localhost, I get

    [root@CentOS conf]# nmap localhost
    
    Starting Nmap 5.21 ( http://nmap.org ) at 2012-01-28 00:58 WST
    Nmap scan report for localhost (127.0.0.1)
    Host is up (0.0000090s latency).
    Hostname localhost resolves to 3 IPs. Only scanned 127.0.0.1
    Not shown: 993 closed ports
    PORT    STATE SERVICE
    22/tcp  open  ssh
    23/tcp  open  telnet
    25/tcp  open  smtp
    80/tcp  open  http
    111/tcp open  rpcbind
    443/tcp open  https
    631/tcp open  ipp
    
    
    • cyberx86
      cyberx86 over 12 years
      Looks like you are binding to ipv6 only and not ipv4 - you may need to explicitly specify the use of ipv4 with Listen 0.0.0.0:80 (Apache docs). (Also check that localhost maps to 127.0.0.1 and not just to ::1 in /etc/hosts - but that is unlikely).
    • user1045696
      user1045696 over 12 years
      @ShaneMadden definitely sure it's the right IP
    • user1045696
      user1045696 over 12 years
      Hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.0.2.15 localhost
    • user1045696
      user1045696 over 12 years
      @ShaneMadden So I somehow fixed the IP issue, nmaping the IP address is now the same as nmaping localhost. However, it's still not working. I also can't ssh into the IP address directly (10.0.2.15:22) so I assume it's the same issue that's messing things up
    • user1045696
      user1045696 over 12 years
      Wgeting also works perfectly, whether it's localhost/index.html, 127.0.0.1/index.html or 10.0.2.15/index.html. I'd assume it's a port forwarding issue if the SSH didn't work perfectly
    • user1045696
      user1045696 over 12 years
      @cyberx86 Done. Everything works from the local machine now, just not my windows host?
  • user1045696
    user1045696 over 12 years
    I've edited the OP with the output, I'm not entirely sure what it means?
  • user1045696
    user1045696 over 12 years
    Should have said, I've fixed that, editing the post now :)