Default Apache pages shows for new domains

Discussion in 'General' started by glennbtn, Nov 20, 2020.

  1. glennbtn

    glennbtn New Member

    Hi All

    Going a little crazy here as trying to diagnose and issue that's landed on my plate. Currently any new domain added to ispconfig goes to the default apache page and not even the default ispconfig page (http only sites)

    I have gone through all the domains and they all have a * for ipv4 and blank for ipv6. I did find 1 site that had some bad apache directives in the options box, so removed. It then started working fine and then went back again. The new site I had had the .err in sites-avaliable but I can't seem to find any other issues and have been looking for days. Original sites work fine http & https just and new ones
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

  3. glennbtn

    glennbtn New Member

    Here we go. Errors about not running services are correct and the server has been working fine as this is not a new build.

    ##### SERVER #####
    IP-address (as per hostname): ***.***.***.***
    [WARN] could not determine server's ip address by ifconfig
    [INFO] OS version is Ubuntu 18.04.4 LTS
    [INFO] ISPConfig is installed.

    ##### ISPCONFIG #####
    ISPConfig version is 3.1.15p3


    ##### VERSION CHECK #####

    [INFO] php (cli) version is 7.2.24-0ubuntu***.***.***.***

    ##### PORT CHECK #####

    [WARN] Port 8080 (ISPConfig) seems NOT to be listening
    [WARN] Port 143 (IMAP server) seems NOT to be listening
    [WARN] Port 993 (IMAP server SSL) seems NOT to be listening
    [WARN] Port 110 (POP3 server) seems NOT to be listening
    [WARN] Port 995 (POP3 server SSL) seems NOT to be listening

    ##### MAIL SERVER CHECK #####


    ##### RUNNING SERVER PROCESSES #####

    [INFO] I found the following web server(s):
    Apache 2 (PID 22616)
    [INFO] I found the following mail server(s):
    Postfix (PID 441)
    [WARN] I could not determine which pop3 server is running.
    [WARN] I could not determine which imap server is running.
    [INFO] I found the following ftp server(s):
    PureFTP (PID 489)

    ##### LISTENING PORTS #####
    (only ()
    Local (Address)
    [anywhere]:587 (441/master)
    [localhost]:11211 (113/memcached)
    [anywhere]:465 (441/master)
    [anywhere]:21 (489/pure-ftpd)
    ***.***.***.***:53 (96/systemd-resolved)
    [anywhere]:22 (282/sshd)
    [anywhere]:25 (441/master)
    ***.***.***.***:4098 (25059/pure-ftpd)
    *:*:*:*::*:3306 (281/mysqld)
    *:*:*:*::*:587 (441/master)
    *:*:*:*::*:80 (22616/apache2)
    *:*:*:*::*:8081 (22616/apache2)
    *:*:*:*::*:465 (441/master)
    *:*:*:*::*:21 (489/pure-ftpd)
    *:*:*:*::*:22 (282/sshd)
    *:*:*:*::*:6009 (22616/apache2)
    *:*:*:*::*:25 (441/master)
    *:*:*:*::*:443 (22616/apache2)




    ##### IPTABLES #####
    Chain INPUT (policy DROP)
    target prot opt source destination
    ACCEPT all -- [anywhere]/0 [anywhere]/0
    ACCEPT all -- [anywhere]/0 [anywhere]/0 state RELATED,ESTABLISHED
    DROP tcp -- [anywhere]/0 [anywhere]/0 tcp flags:!0x17/0x02 state NEW
    DROP all -f [anywhere]/0 [anywhere]/0
    DROP tcp -- [anywhere]/0 [anywhere]/0 tcp flags:0x3F/0x3F
    DROP tcp -- [anywhere]/0 [anywhere]/0 tcp flags:0x3F/0x00
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 state NEW
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 state NEW
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 state NEW
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 state NEW
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 tcp dpt:22 state NEW
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 state NEW
    ACCEPT tcp -- ***.***.***.*** [anywhere]/0 state NEW
    ACCEPT tcp -- [anywhere]/0 [anywhere]/0 tcp dpt:80
    ACCEPT tcp -- [anywhere]/0 [anywhere]/0 tcp dpt:443
    ACCEPT icmp -- ***.***.***.*** [anywhere]/0 icmptype 8 state NEW
    ACCEPT udp -- ***.***.***.*** [anywhere]/0 udp dpt:161 state NEW
    ACCEPT icmp -- ***.***.***.*** [anywhere]/0 icmptype 8 state NEW
    REJECT all -- [anywhere]/0 [anywhere]/0 reject-with icmp-port-unreachable

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination
     
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    What is the error?
    What can you see in apache logs when accessing that problem website?
    Are there problems with certificates for the websites? Does this problem site have httpS?
     
  5. glennbtn

    glennbtn New Member

    The only error I have come across is (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80 in syslog

    There are current website using https with no issues. I have not tried to put this as https as I am presuming it won't work if the normal port 80 is not working correctly.
     
  6. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    There must be something in apache access log when going to that website. If there really is nothing, check DNS to seen where the domain name goes.
     
  7. glennbtn

    glennbtn New Member

    This is all it shows. I have changed the domain name so it's not the real one

    155.155.87.166 - - [20/Nov/2020:12:28:18 +0000] "GET /favicon.ico HTTP/1.1" 404 496 "http://test3.mydomain.co.uk/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:82.0) Gecko/20100101 Firefox/82.0"
     
  8. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    You probably just have a default website with a different ip setting, 'apachectl -s' should show you what's going on.
     
    ahrasis likes this.

Share This Page