+1

+1

I would really like this feature. I got asked for it several times.

+1

+ 1

Hello Plesk,

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.

best regard,

Eugenio

When?

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

So important, please consider it

Yes . Its Need

+1

+1

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

+1

This has already 366 votes, how many votes do you need it to be to become popular?

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

Hi everyone,

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.

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.

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.

+1