Added Website Domain Only Shows Default Apache Page

Discussion in 'ISPConfig 3 Priority Support' started by yupthatguy, Jul 13, 2021.

  1. yupthatguy

    yupthatguy Member

    Hey there,

    Under Domains I added a new website "example.com". I added a site alias "test.example.com", I created a DB and shell user for example.com.

    https://test.example.com:8080 is also the control panel page for ISPConfig.

    How can I build a website for example.com that does not "conflict" with https://test.example.com:8080 (if a conflict is actually what is happening).

    NOTE: Under /etc/apache2/sites-enabled/

    Thanks
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    There is no conflict and domain names can't conflict with different ports anyway as port 8080 is not port 80 and is not port 443. If you add a port to a URL, then your web browser connects to this port instead of the usual port 80 (HTTP) or 443 (https). So https://test.example.com:8080 is not https://test.example.com as they are on completely different ports and therefore, they can not be a conflict.
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    And if a website shows the content of a different website, then this is explained in the read before posting thread: https://www.howtoforge.com/community/threads/please-read-before-posting.58408/

    But the server hostname is always treated a bit differently by apache, that#s why you use for the hostname a subdomain that's not used for other purposes like using it as a website or subdomain of a website.
     
  4. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    Aside from the port issue, perhaps what you're wanting is a "vhost alias domain" rather than a (non-vhost) "alias domain"? That lets both example.com and test.example.com have their own website root, even though they share ssh logins for management, etc.
     
  5. yupthatguy

    yupthatguy Member

    For users looking for a simple solution and having a similar problem. What worked for me was tools -> resync websites.
     

Share This Page