• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Ignore Requests for non-configured domain/SSL combinations

rowingpeter_s

New Pleskian
Plesk Onyx on Linux hosting a mix of SSL and non-SSL sites.

Requests over https:// for sites where no SSL certificate is installed result in the plesk default webpage being returned as content for the request URL.

Naturally the default webpage SSL certificate is not valid for the request domain/URL and results in a browser warning that site is mis-configured.

My preference would be for any web requests over https:// that don't match an SSL configured domain to be ignored by the server [no response]. Is this possible?

I believe I could resolve this with a 2nd IP address and splitting SSL / Non-SSL sites. Would like to do it with a single IP if I can.
 
Last edited:
Apache always delivers the default page for domain request where it does not have a virtual host configuration for. This is expected behavior and cannot be changed. It is not Plesk related, but the standard behavior of Apache.
 
That makes sense and mirrors what I see. Thank you.

I can achieve the desired behaviour by mapping 2x IP addresses to the server and only opening port 443 in the firewall for one. SSL sites use one IP. Non-SSL the other.

I incidentally noticed that this isn't possible within a single subscription where all domains appear to need to use the same IP address.
 
Last edited:
Back
Top