• 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.

Net affect of enabling SSL by default for all Plans

RationalPolymer

Basic Pleskian
Is there any downside to enabling SSL for all sites/all Plans even though there will be sites that will never use or require HTTPS? What is the "net affect" of enabling SSL?

Does this cause Apache configuration changes (eg; define vhost at port 443 where if SSL was NOT enabled there would be no such Apache configuration) even if the site does not have a certificate installed?
 
Last edited:
Back
Top