ISPConfig serving wrong website

Discussion in 'Installation/Configuration' started by WhitcombeRD, Mar 14, 2023.

  1. WhitcombeRD

    WhitcombeRD Member

    Got an issue that's driving me nuts currently.
    A clean install of 3.2.9p1 on a Raspbian Pi. All went OK other than having to removing the .rar as the package doesnt exist on Arm64.
    The box is running on a RaPi running under a 192.168.xxx.yyy address with appropriate port forwarding from the main internet IP.

    I first created a website "aaaaa.domain.here" under ISPConfig and it works perfectly.
    Going to http://aaaaa.domain.here or https://aaaaa.domain.here displays it.
    The problem i have is i added a second site - zzzzz.domain.here. DNS entries etc are correct.
    The issue is going to http://zzzzz.domain.here goes to the Apache default index page and not the site. Trying to go to the ssl https://zzzzz.domain.here redirects to the site at aaaaa.domain.

    In other words i cant see it - the non secure goes to an apache index, the secure version goes to the wrong website.
    Document root looks correct for the zzzzz site and i can see the folders and created indexes - it just wont display.

    In the Server Config i have the IP address set as the public IP of the connection

    Any idea what's gone wrong here ? I cant see anything obvious in any error logs at all. No redirects or rewrites are set.
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    ahrasis likes this.
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Just to mention, ISPConfig is a Hosting Control Panel and not a web server, so your websites are not served by ISPConfig. They are served by either Apache or Nginx web server. As @Taleman mentioned, the common issue that Apache or Nginx do not serve the right website when IP or domain or protocol does not match is described in the read-before posting guide.
     
    ahrasis likes this.
  4. WhitcombeRD

    WhitcombeRD Member

    Looked through the FAQ thread but i cant really see how its affecting what i have here.

    I just had 2 sites, one of which works on http and https. The other does not work at all http:// goes to the default apache (not ispconfig) index and https goes to the first site i created (the one that works).
    Both are listening on * for the IP, neither have rewrites to https or anything else set at all. I just cant make the second site reachable at all.

    Ive been running ispconfig for quite a few years and not come across this problem at all until this new server build this week.
     
  5. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Is the site domain the same as the hostname of that server?
     

Share This Page