• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Problem with SNI and Plesk 10.4 on Debian

B

buliwyf

Guest
Problem with SNI and Plesk 10.4 on Debian [Solved]

Hello,

i upgraded one of our Machines to Plesk 10.3 from 9.4 after that i upgraded Debian Lenny to Debian Squezze.
All went fine without problems.

Shortly after that i upgraded to Plesk 10.4.

We now try to setup SNI but it fails. For every Site the Default certificate is used.
This line in the apache logfile tells me, that SNI is enabled in the apache Webserver and working.

[Wed Nov 30 13:45:52 2011] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)

It seems that Plesk does note recognize, that the Server is SNI capable.

Any ideas why?

Thanks for your help.
 
Last edited by a moderator:
Not yet.

But after i changed it and restarted the psa service i was able to select a certificate in the
hosting settings for the Domain.

Now the website uses the correct certificate.

Thanks for your Help.
 
Back
Top