Supporting SSL resellers
We need to protect with SSL certificates panels resellers. It is currently not possible.
This should be an urgent implementation.
Resellers constantly have the error that the website is not secure.
Right now we can only put a SSL to protect the panel. We need to protect the panel for more domains.
Example:
https://domain1.es:8443
https://domain2.es:8443
https://domain3.es:8443
etc...
Forgive my translation, I use google translator.
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
-
Anonymous
commented
yes, need this request too.
Other Solution was disable port 8443 forhttps://domain2.es:8443
https://domain3.es:8443only enable for the Plesk Interface default Domain. How i can do this?
-
Sean
commented
Not secure for the most important account? It doesn't make any sense!!!!
-
Osi Dosi
commented
+1
-
Fran Silva
commented
It is urgent and necessary. Google Chrome has new treatments for "not secure" websites!
-
Anonymous
commented
Same problem here
-
Gil
commented
I've the same Problem. How can I ask to my Customer to migrate to Onyx, with lets encrypeted and then they receive a certificate error of administration panel!
-
Robert Sandström
commented
Please fix this! Many have asked for this feature.
-
Mark
commented
Please fix this. It is more professional when your customer can login into Plesk from his own domain. Now he must use my domain to log in, otherwise, he gets a security error...
-
rdk
commented
seems to be a duplicate of the same feature: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/6640242-supporting-ssl-resellers
please vote there to speed up the process!
-
Marco Marsala commented
The SSL certificate is not applied to webserver listening on port 8443, even if installed for the domain.
Live example:
https://www.holidayworld.it/ shown as secure
while https://www.holidayworld.it:8443/ is shown as not secure -
rdk
commented
implement this feature to all domains with ssl enabled, so accessing panel under custom domain will use correct certificate and will not show warning messages
-
Michael
commented
Our company also has the urgent need for this feature. The migration of customers would be much more easy, if they could use their own branded Plesk admin login URL under their existing Domain. The only work around right now is the Plesk Multi Server. But this will not fix the branded argument and is not suitable for all environments.
-
Anonymous
commented
Wow cpanel /whm has this why not plesk. It's been a hard shift from whm/cpanel to plesk. This is a simple thing that should of been part of plesk as soon as you started ssl. Very disappointed. You create a owner > subscription > domain.
Owner logs into example.com:8443. Goes to https:example.com:8443. Warning someone might he trying to steal your information. ?? Why do this to plesk subscribers that pay. You raised the prices. So this is a simple fix. Please add it asap. I'm sure it's a few lines of code and it's very possible. -
Anonymous
commented
Hi
It's urgent not just required
Please start on it -
Anonymous
commented
Hi
I also have a requirement for resellers to have their own SSL CP url with their own SSL certificate.
-
Manu-K
commented
very important and usefull feature, no whitelabelling possible with standard SSL
-
Lefteris commented
Yes we need this feature,
its important -
Simon Bendall
commented
I believe this suggestion is exactly what I was about to suggest.
Basically I am looking at reselling a hosting package, but am unable to offer a correctly branded management interface, as the SSL certificate for the management interface is for the company that I am reselling - I need to be able to specify an SSL certificate for MY domain which Plesk will accept. I agree that this should be an urgent requirement, and find it amazing that there are not more people asking about this.