• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question IF SSL/TLS support is checked, but domain does not have cert?

larryk

Regular Pleskian
for a domain, on the hosting settings page:

IF THIS IS CHECKED...
SSL/TLS support. Select this option to secure transactions with your site via SSL/TLS protocol, which encrypts all data and transfers it over a secure connection.

AND the domain does NOT have a SSL cert...

Does that cause a problem?
Should it not be checked?
What happens if checked?

This question is in reference to the apache log error of:
AH01909: RSA certificate configured for domainname.com:443 does NOT include an ID which matches the server name

thanks

PS. I'm guessing many/ most domains on my new server have it checked, I'm guessing because it was checked on the old?
 
Server will respond but will use a default self-signed certificate. This will cause the browser to either drop the connection or display a yellow or red lock and a warning message to surfers.
 
thanks... i've been removing them, unchecking... but i think my support team also did something? maybe not... but the "AH01909: RSA certificate configured..." errors were stopped!
 
Back
Top