subdomain serving up website of another client

Discussion in 'Installation/Configuration' started by winsbury, Sep 10, 2019.

  1. winsbury

    winsbury Member

    I have a new virtual server configured as per "The Perfect Server - Ubuntu 18.04" running ISPconfig 3.1 and all updates to the system are done and monitor state is showing green across the board: State: ok (0 unknown, 0 info, 0 warning, 0 critical, 0 error)

    I am migrating a number of websites from an older physical server running Centos and ISPConfig3.0.5 but that is somewhat irrelevant except to note that DNS has the majority of the domains still pointing to this older server including www/mail for client#2

    The first client migrated without any issues so client#1 website, ftp and email is working perfectly using Lets Encrypt SSL .

    The second website is causing me a real headache and I just cannot see what is wrong. Client#2 is a large ecommerce website so I wanted to set up a temporary URL to test it on the new server prior to switching over DNS to point to it. I set up a subdomain for client#2 and published dns entry which directs to the new server's IP address , this client is also using Lets Encrypt SSL. However, when I type the subdomain into a browser it is serving up the webpage and ssl certificate for client#1 instead.

    Any ideas why Apache might be serving up the wrong website ? Could there be corruption somewhere? I have tried a number of methods for creating temporary URLs using 'Website auto alias' at the server level and 'Alias domain for the website' so wondering if something has corrupted a config file somewhere ?
  2. winsbury

    winsbury Member

    Just found that the Lets Encrypt SSL and SSL boxes were unticked in the websites:domain setting, I am certain they were ticked prior to creating the sub-domain so perhaps creating a sub-domain deletes this config in the main domain or perhaps because the tld already has a certificate issued by Lets Encrypt which is on the old server there was a conflict of some sort ? ... strange behaviour imo. Anyway, having ticked them again a certificate has been issued for the subdomain which seems to be working normally.

    As for why it was defaulting to displaying the 1st website, I remembered something similar from the install of our old server and had in fact made a comment here about it back then, I imagine its a similar issue:

Share This Page