Hi, everything works very well)

Hi!

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?

Dear Plesk,
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.
Best Regards
Massimo

This is a major for me. "Web host edition" more like for single man business when he dont have customers.

We have several resellers on our servers and all ask us if those features are available:
- Custom SSL Login URL
- Custom branded Login Portal for those URLs

It is very useful if those features are integrated in Plesk.

One thing to:
- For the SSL Login URL, it should have a ruction in the SSLit! Module that the reseller can make their own certificates.

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!

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:
https://gist.github.com/Eiskaltereistee/8f5467ad24107a92aba51b5415c7a5bf

I also can handle that for you, just let me know if you need something.

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.).

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.

Please implement this urgently. I can't do business and talking about security and my customer getting this at first access (and every access later).

Plesk implement this

Please 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

+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.