• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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