Dedicated IPs should be assigned the same certificate as the subscription assigned to it
At the moment If you assign a certificate to a subscription it works as SNI by default, even when that domain has a dedicated IP assigned already. That is a problem in a shared hosting environment because every time that a clients installs or updates a certificate we have to manually activate it for the client (the clients only have access to their subscription's configuration, not the server's) and do a dirty hack to activate the same cert on both the IP and the subscription (as the cert doesn't appear in the certs list for that IP).
This should be implemented in a way that, if a subscription with a dedicated IP gets it's cert updated (for example the cert assigned to the main domain of that subscription is changed to a different one) the IP should be updated accordingly to reflect that change so It keeps working as a classic SSL certificate.
Almamu
shared this idea
Thank you for your input!
Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
—
IG