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

Every SSL Certificate needs a seperate IP adress?

B

BoXie

Guest
Question:

Is it true that every IP address can only have one SSL certificate .. and that you'll need an extra IP-address for every (new) certificate that you install ?

Someone please explain this for me.
 
In short, Yup.

However there are wildcard certificates. Have a google for that term and perhaps you can accomplish what you need that way.

BP
 
He he .. yeah . i know .. but Wildcard means $$$$

But now i know for sure that every certificate needs its own IP adress.

So i think it might be a problem if i have 20 customers on 1 server who want a certificate .. I'm not sure if i can get 20 IP-adresses for my server !

But luckily that situation has not arised yet.
 
Originally posted by BoXie

But now i know for sure that every certificate needs its own IP adress.

Unfortunately HTTPS designed in this way: one IP - one certificate.
 
Back
Top