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 Anonymous
    
 commentedPlease implement this urgently. I can't do business and talking about security and my customer getting this at first access (and every access later). 
- 
      Anonymous commented Plesk implement this 
- 
       Pascual
    
 commented Pascual
    
 commentedPlease add SSL to all Plesk login pages (port 8443) and mail.example.com for mobile connections / and other remote devices of the clients This panel has everything, BUT LACKS of the essentials and the languages are paid subscription ... where this has been seen in these times ... it seems an absurdity. In other words, you pay a month on average about € 36 / license + € 18.11 / 3 additional languages ... so that in the end you will be saving customers with SSL security notices ... I am really very impressed of the great advances and improvements that were implemented in the last v. Plesk Onyx (Docker, Node.js, Apache & Nginx server improvements) ... in this regard I congratulate you 5 years ago I left Plesk for these reasons, I saw the improvements, I thought that these problems were solved ... but I see that no ... it will be that I made a bad decision to have used the Plesk panel again ... or not !? Bests regards 
- 
       Daniel
    
 commented Daniel
    
 commented+1. very important for plesk users that we offer services to third parties, and offer them a secure administration panel. Please consider, implement this functionality soon. 
- 
       Anonymous
    
 commented Anonymous
    
 commentedyes, 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 Sean
    
 commentedNot secure for the most important account? It doesn't make any sense!!!! 
- 
       Osi Dosi
    
 commented Osi Dosi
    
 commented+1 
- 
       Fran Silva
    
 commented Fran Silva
    
 commentedIt is urgent and necessary. Google Chrome has new treatments for "not secure" websites! 
- 
       Anonymous
    
 commented Anonymous
    
 commentedSame problem here 
- 
       Gil
    
 commented Gil
    
 commentedI'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 Robert Sandström
    
 commentedPlease fix this! Many have asked for this feature. 
- 
       Mark
    
 commented Mark
    
 commentedPlease 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 rdk
    
 commentedseems 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 rdk
    
 commentedimplement 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 Michael
    
 commentedOur 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 Anonymous
    
 commentedWow 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 Anonymous
    
 commentedHi 
 It's urgent not just required
 Please start on it
- 
       Anonymous
    
 commented Anonymous
    
 commentedHi I also have a requirement for resellers to have their own SSL CP url with their own SSL certificate. 
- 
       Manu-K
    
 commented Manu-K
    
 commentedvery important and usefull feature, no whitelabelling possible with standard SSL 
 
          