Hi everyone!

To make Plesk easier to use, we would like to ask you to take part in a short user experience test about “Plesk Customization URL”. It should not take you more than a few minutes to participate.

A link to the UX-test: https://usabi.li/do/1c9eceb2d9d0/215

Hi Heinrich,

> the feature seems to work improperly. I get a certificate error when trying to connect to the site.

I have tried to reproduce it but couldn't (https://www.ssllabs.com/ssltest/analyze.html?d=ipv6test.yamshanov.ru&latest). If you have steps-to-reproduce, could you please share the steps on Plesk Forum (https://talk.plesk.com/forums/reports.746/) with us?

> If enabled, is this subdomain automatically included in Let's encrypt certificates?

Securing Plesk with SSL/TLS certificates from Let's Encrypt is available in "Tools & Settings > SSL/TLS certificates".

Hello,

the feature seems to work improperly. I get a certificate error when trying to connect to the site.
ssllabs.com states the plesk-panel-subdomain deliveres an invalid certificate over ipv6 adress but a valid one over ipv4.

So, PLESK should correct there functionality, here.

Best regards,
Heinrich

If enabled, is this subdomain automatically included in Let's encrypt certificates?

For I can't find an entry and some browsers don't open the subdomain, cause of HSTS restrictions.

Also, is it bound to listen to all the servers IP addresses?
For asking www.ssllabs.com to check the subdomain specifically returns no valid answer on ip6.

hello Admin,

Please change port 8443 to name alias

Example :
https://name-domain.com:8443

Change :
https://name-domain.com/control-plesk

I would like to see this feature especially where I'm not able to use a Let's Certificate certificate for the plesk console.

Very good idea. Need it on Linux
+1

Hi guys, any news on this? Regards!

Hello,

Please allow the usage of Plesk in Windows without using a Port. This is already available in Linux as Described in the KB.

Example:
Accessing to: https://publicexample.com
Returns the content of: https://server.example.com:8443

Thank you!

A workaround: https://www.the-greathouses.net/blog/2009/12/plesk-control-panel-access/

No news?

The port is nothing but an issue for people.

first: its nice to have
second: its easier for our customers to login into plesk. they forget the port often ;-)

hi, we need the same. but without port or subdomain. only the domain.tld in combination with the extansion custom login url.

its easier for our customers :-)

thanks

I can create separate domain or sub domain for plesk panel access if the plesk application in IIS website virtual directory. so that i will provide panel panel access to customer and reseller with my brand domain without port. even though we can have optional to access panel with existing scenario.

This needs to happen

Required feature plesk panel access without port no 8443. so that we can configure to access plesk panel with separate domain for