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.
Plesk team, any idea or plans to add this "feature"?
It's critical important for many people.
You offer a multi-client and multi-domain solution but we can't access for more than 1 domain to the platform, make no sense right?
Diego, I have the same problem.
I lost many clients, because they think that I have not good service and they data not be safe
After 30 min chat, I realize this is already a massive problem for many users.
No everyone votes because no everyone knows how to finish on this page.
Like me before chatting for 30 min with a support representative.
No idea why we should considering this as a feature, we should have this one already.
I can't give to a client another domain name access to avoid the SSL warning.
This is not an option.
I hope you release this "feature" ASAP, please.
I am surprised that after these votes and comments, Plesk does not take it serious and either they are not going to comment here.
Not secure for the most important account? It doesn't make any sense!
Евгений Карпенко commented
Hi, everything works very well)
It possible or we have to find other solutions?
Plesk Staff, can you comment this. please?
How can I use this option right? My clients don't have secure connection. It's very important for resellers companys. Do you have plan to implement this in future?
Hello! When it'll be implemented?
we need to issue a certificate with let's encrypt with multiple domain (eg. www.site1.com, www.site2.com, etc). in a normal LAMP environment we could use certbot with multiple "-d" flags for all the domains needed, but what in the plesk environment? It seems we can issue only certificate for a single domain or a wildcard domain. I hope you could implement this feature soon.
This is a major for me. "Web host edition" more like for single man business when he dont have customers.
Currently, it is only possible to include one domain for securing Plesk server with a Let's Encrypt certificate and this is a limitation.
We need this new functionality because:
- Previously, our business name was: https://plesk.example.com:8443, therefore Plesk was secured with LE including this hostname
- Currently, our business name has been renamed, therefore we've renamed the Plesk url to: https://plesk.newbusiness.com:8443 - We've issued a new LE certificate to secure it.
Therefore, almost all our customers are trying to reach our server with the old URL and a certificate error is shown to them.
This would be easy to solve if Plesk Let's Encrypt would be able to include multiple domains to secure our Plesk server.
Yes, please put this basic feature to top priority. It is really essential. There is no work-around which works for our use cases.
Really appreciated that you solved the similar problem for the users accessing the mail servers with their domain name!
Nasir Rashid commented
This is really needed, as we cant give reseller white label right now, and loosing allot of customers. I dont know why plesk is not implementing this, users coming from Cpanel are really annoyed.
A must to implement
Please add this feature if anyone use http://domain.com:8443 not redirect host name and if anyone use https://domain.com:8443 then redirect host we need this feature i hope every user nee this feature
I have a simple and nice workaround:
Install a simple nginx (it can be a additional instance on your plesk server or a docker container). You just need a own ip.
Then create a nginx proxy. Config example:
I also can handle that for you, just let me know if you need something.
Bob B commented
I would also like this, but I have used this workaround... I add a wildcard certificate (*.example.com) to secure the panel. Then I provide hostnames for each reseller to use to log in to Plesk (reseller1.example.com, reseller2.example.com, etc.).
Greg Lusienski commented
Yes this would be good idea. Have customer go to their control panel and it not secure. Then telling the customer their nothing you can do about. You lose a customer.
yes, Please implement.