Opening apache to the internet

Discussion in 'Server Operation' started by selectoe, Jan 27, 2009.

  1. selectoe

    selectoe New Member

    Hello, I am wanting to open up my apache root directory (var/www) to the internet. I can access the default page on the lan by typing 'myserver' into the browser address bar.

    I have a router which is port forwarding port 80 to the server's internal ip address. When I try to enter my external ip address it gives me the error message "The connection to the server was reset while the page was loading".

    What do I need to do to give everyone access?

    Thanks in advance.
     
  2. Allen15

    Allen15 New Member

    if you can browse it locally, you may be browsing it with only ARP. Are you browsing it on your local lan from Windows machines, or other Linux systems?

    This sounds like it may be the root of the same problem I'm having, where I get that same error message, but I have no other systems on that local network segment to check. Hopefully an answer will work for both of us.

    If you don't have the same problem, this may help you too: What do you have for DNS pointing to your router? This is sounding more and more like an Apache configuration issue, since I can browse by IP address, but not by name, but I can ping the name externally, and it resolved to the proper IP address. If you can't browse by IP address externally, it really sounds more like an Apache configuration problem, where you haven't set up proper permissions in Apache to serve those pages to the world at large, or you have some firewall configuration that is rejecting requests from anything outside of your local network.

    Check your firewall settings, just to make sure? Good luck.
     
  3. adam0x54

    adam0x54 New Member

    Like Allen said, it seems like a firewall setting. Go to dyndns.com and create an account to have you own fqdn so you dont have to remember ip addresses.
     
  4. falko

    falko Super Moderator ISPConfig Developer

    Also make sure that your ISP doesn't block port 80.
     
  5. selectoe

    selectoe New Member

    Thanks guys, it is likely to be an apache config problem I think. I have always had trouble configuring apache properly. I have switched off all firewalls and it still happens, also, ISP is not blocking port 80. I have a static IP address, so it is easy to remember the ip address, so I dont mind that.

    What would be a typical apache configuration to allow this to happen?
     
  6. falko

    falko Super Moderator ISPConfig Developer

    What are the outputs of
    Code:
    netstat -tap
    and
    Code:
    iptables -L
    ? Any errors in Apache's error log?
     
  7. selectoe

    selectoe New Member

    [email protected]:/$ sudo netstat -tap
    [sudo] password for richard:
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 *:imaps *:* LISTEN 5 013/dovecot
    tcp 0 0 *:pop3s *:* LISTEN 5 013/dovecot
    tcp 0 0 *:mysql *:* LISTEN 4 745/mysqld
    tcp 0 0 localhost:submission *:* LISTEN 4 995/sendmail: MTA:
    tcp 0 0 *:netbios-ssn *:* LISTEN 4 896/smbd
    tcp 0 0 localhost:bacula-dir *:* LISTEN 5 127/bacula-dir
    tcp 0 0 localhost:bacula-fd *:* LISTEN 5 111/bacula-fd
    tcp 0 0 *:pop3 *:* LISTEN 5 013/dovecot
    tcp 0 0 localhost:bacula-sd *:* LISTEN 5 082/bacula-sd
    tcp 0 0 *:imap2 *:* LISTEN 5 013/dovecot
    tcp 0 0 *:www *:* LISTEN 5 103/apache2
    tcp 0 0 *:ftp *:* LISTEN 5 041/proftpd: (acce
    tcp 0 0 192.168.0.159:domain *:* LISTEN 4 444/named
    tcp 0 0 localhost:domain *:* LISTEN 4 444/named
    tcp 0 0 localhost:postgresql *:* LISTEN 4 852/postgres
    tcp 0 0 localhost:smtp *:* LISTEN 4 995/sendmail: MTA:
    tcp 0 0 localhost:953 *:* LISTEN 4 444/named
    tcp 0 0 *:microsoft-ds *:* LISTEN 4 896/smbd
    tcp 1 0 192.168.0.159:34269 192.168.0.:microsoft-ds CLOSE_WAIT -
    tcp6 0 0 *:domain *:* LISTEN 4 444/named
    tcp6 0 0 *:ssh *:* LISTEN 4 493/sshd
    tcp6 0 0 ip6-localhost:953 *:* LISTEN 4 444/named
    tcp6 0 0 ::ffff:192.168.0.15:ssh ::ffff:192.168.0.:53993 ESTABLISHED1 0194/sshd: richard



    and::::::::::::::::






    [email protected]:/$ sudo iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination



    Thanks,
    Richard.
     
  8. falko

    falko Super Moderator ISPConfig Developer

    Looks ok,so my last guess is that it has something to do with your router's firewall...
     

Share This Page