ISPConfig website not pointing to it's folder (apache2ctl)

Discussion in 'Server Operation' started by nark, May 20, 2023.

  1. nark

    nark New Member

    Hello,

    I've been using ISPConfig for a while, it's a great peace of work.
    Today I bumped into a situation that I cannot undestand.

    So I have multiple websites hosted, but today I added a new website in ISPConfig (let's say: problem.eu) and when I try to access the site (I edited my local hosts file pointing to ISPConfig IP), I get served by the index of the last website I entered. (cloud.site.ro)

    If I create another dummy website (dummy.ro) and point it to the ISPConfig IP (from the windows hosts file), I get the general index file of the new website, so all ok.

    So only this specific website (problem.eu) I get served by the index of the last website created. (cloud.site.ro)

    I want to mention that there is no name similarity, even the TLD is not the same.

    I looked up in /etc/apache2/sites-avalilable and the vhost in there (for problem.eu and all other sites) but when I run apache2ctl in ssh, i see all the websites, but not the new one. (problem.eu)
    Again, if I create a new dummy site (dummy.ro), it works, I see it in apache2ctl.

    Just to mention the last site and script installed before this problem accured was Nextcloud using the web installer, not manual install. (cloud.site.ro)
    I don't know if it has anything to do with my problem but just to put it out there.

    Thank you!
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    See FAQ section of the read before posting, it contains this topic:

    https://forum.howtoforge.com/threads/please-read-before-posting.58408/

    You also see this behavior when you access a site by https that has no SSL. Or you just missed activating the site, check if the active checkbox is ticked. And finally, if this does not solve your issue, use debug mode:

    https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/

    You might also want to check if the vhost file of the affected site has no .err file ending, which would indicate that it was rejected by apache.
     
    ahrasis likes this.

Share This Page