• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue letsencrypt help one ip two domain, can't figure it out

joeblow

New Pleskian
plesk on windows 2019 server, named server.domain1.com. domain 1 created, named domain1.com on shared primary ip. letsencrypt ssl created, secures plesk (server.domain1.com) and domain1.com. works.

then, domain2.com is created on same shared primary ip. letsencrypt ssl created and deployed on domain 2. sslab test passes cert 1, but cert #2 throws "no sni" and "alternate name server.domain1.com mismatch".

why is server.domain1.com showing up in this test when it's not in the ssl i'm testing? if the answer is enable sni, isn't sni enabled on windows by default? if not, how do i enable it and where in plesk/letsencrypt/windows? if sni isn't the fix, what is? how do you use letsencrypt to create multiple ssls on multiple domains using one shared ip in plesk?

please explain as if i'm a child.
 
Back
Top