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.
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.
Eugenio Carrió commented
It would be very important for each user to be able to access the Plesk control panel interface from their domain, it is vitally important for a good customer experience.
Sihar Manullang commented
Francesca Smith commented
Ridiculous this has not been implemented. The old parent company that Plesk was bought out and destroyed Hsphere which 20 years ago had this functionality
Netandhost. com commented
Yes . Its Need
Olaf T commented
Kallef Alexandre commented
"please continue voting for this feature if you consider it important." The suggestion is from 2014 (8 years old) and currently has 374 votes. Maybe in 2030 they will do something.
waleed samy commented
This has already 366 votes, how many votes do you need it to be to become popular?
Stephen Elwell-Sutton commented
At present I can only secure my Plesk site with a single domain certificate, so when my users try to connect to their control panel, they get a certificate error. I would very much like to connect to Plesk via multiple domains, e.g. https://domain1.com:8443, https://domain2.com:8443, https://domain3.com:8443, etc so they are not prompted with a certificate error
Alexander Yamshanov commented
We aware of that UserVoice request and periodically attempt to find a good way how we can improve Plesk to provide this feature, but right now there are no good solutions how to do it. There are some workarounds existing but we can't implement them into Plesk or recommend for the Production use because of important limitations and/or known issues.
As an example, there are a few of possible workarounds:
- It can be a Let's Encrypt certificate that contains several different names using the Subject Alternative Name (SAN) mechanism. The certificate should be reissued every time when a new domain is created on Plesk. It means it is easy to reach existing Let's Encrypt limits for issuing certificates, after that LE stops issuing free certificates for that server for some period of time.
- It could be a wildcard certificate like *.example.org but Plesk's domainname usually manages by external name servers and the process could not be automated. At the same time *.example.org (reseller1.example.org, reseller2.example.org, etc.) is not the asked solution like unique and SSL protected link to Plesk per reseller/customer example1.org/example2.org.
- Some other workarounds have concerns from security point of view.
We will continue researching on how we can deliver requested functionality. Please continue voting for this feature if you consider it important.
Don Higbee commented
I don't know why this was never a major priority. This is standard practice with every other hosting control panel I have ever used.
Patricio Almonacid commented
I have always managed my clients' accounts, and now that I will no longer make hosting manageable for me, I just realized this great detail. It seems basic to me that each client should log in by his domain name. I hope you can solve it in the future.
Note: voting should be done with the same credentials that you use to login to technical support.
Piensanet Desarrollo en Internet commented
Fabian Marsiglione commented
Nobody from Plesk is answering this, requested since LOT years ago?
This is a BASIC functionality guys!!! YOu are out of the market !!!
Thomas C. commented
This functionality is essential for resellers to resell with their own branding !!
It's been more than 7 years that this functionality is requested !
I just can't belive Plesk have such issues with SSL certificates on panels.
Problem continues from year to year, and you still did not fixed it
Some kind of a workarond you give us here is still not enough.
We need either to redirect user before certificate validation by browser, or you to make SSL certificates works for customerdomain.com:8443.
People should consider about paying PLESK license for product that does not meet industry standards.
مسعود نجار خدابخش commented
Litschi EDV & Werbetechnik commented