all https requests goto one clientes domain.

    Afternoon all.
    I have one clients domain configured with a SSL certificate from RapidSSL. All HTTPS requests seem to resolve to this one customers site even though the other customers are not configured with SSL.


    How can I correct this so HTTPS does not resolve this one customers site only ?


    Cheers,
    Rob

    Hello @robbo,


    Thanks for your question.


    When there's no site configured on a zone Apache will present the default zone. If there's none set it will just show the alphabetical first website (config file name).
    To prevent this from happening you could use the ServerDefaultPage plugin.


    Please provide some more info (OS, i-MSCP version, logfiles, status of the domain in the panel etc), so we can check if there's anything fishy going on.
    Also in this case a screenshot of the certificate page would work well (please remove the private key)

    Thanks for the quick reply theemstra.


    I think the problem is coming from the apache config? The I-MSCP admin site uses NGIX port 8080 but if I remove port 8080 the admin pages resolves to this customers ssl domain too.


    Customer 1 has a public SSL certificate and HTTPS resolves fine.
    Customer 2 has no cert does not use SSL and HTTPS resolves to customer1's domain


    So if I use https://www.customer1.com this will resolve correctly
    So if I use https://www.customer2.com this will resolve customers1.com webpage instead of customer2.com
    If I replace https with http customer2.com resolves correctly.


    Here are the details:


    OS: 3.2.0-4-amd64 #1 SMP Debian 3.2.88-1 x86_64 GNU/Linux
    I-MSCP: 1.3.14


    Is there a global setting for HTTPS? Maybe its forwarding everything?


    Regards,
    Rob


    PS: Ive just done a test creating a self signed ssl cert via the I-MSCP control panel and it seems to resolve this issue. But it would be good to know whats going on without doing this.


    PPS: Adding a self signed SSL certificate to a test site works for that test site. Then I add it to another test site and it resolves test 1 instead of test site 2 ?(

    Files

    • customer1.jpg

      (134.82 kB, downloaded 7 times, last: )

    • customer2.jpg

      (90.98 kB, downloaded 6 times, last: )

    @theemstra


    There is no issue at all here and anyway, we don't support 1.3.x.

    Quote from robbo007

    Customer 1 has a public SSL certificate and HTTPS resolves fine.
    Customer 2 has no cert does not use SSL and HTTPS resolves to customer1's domain


    So if I use https://www.customer1.com this will resolve correctly
    So if I use https://www.customer2.com this will resolve customers1.com webpage instead of customer2.com
    If I replace https with http customer2.com resolves correctly.


    That is the expected behavior as stated previously by @theemstra


    Quote from robbo007

    Is there a global setting for HTTPS? Maybe its forwarding everything?

    There is no forward here... You should considere to read Apache2 documentation.



    Thread closed.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support