• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Client Plesk Login with Their Domain Name

FutureX

Basic Pleskian
Server operating system version
AlmaLinux 8.7 (Stone Smilodon)
Plesk version and microupdate number
Plesk Obsidian Version 18.0.48
In the interest of simplicity I'm trying to figure out how a customer can login to their Plesk control panel using their domain name instead of the server name but when I try it the browser complains that the connection is not private and when I check the cert it's looking at in the browser it's the server SSL cert and not the users domain name cert.

https://clientdomainname.com:8443 - shows "connection is not private"
https://servername.com:8443 - works fine

I know you can just click 'trust' as the server has a cert but I would rather the client not have to do that.

Thanks!
 
In the interest of simplicity I'm trying to figure out how a customer can login to their Plesk control panel using their domain name instead of the server name but when I try it the browser complains that the connection is not private and when I check the cert it's looking at in the browser it's the server SSL cert and not the users domain name cert.

https://clientdomainname.com:8443 - shows "connection is not private"
https://servername.com:8443 - works fine

I know you can just click 'trust' as the server has a cert but I would rather the client not have to do that.

Thanks!
I looked at this page: Log In to Plesk
 
Hello @FutureX

Since port 8443 is another service, the SSL warning is expected when you use a customer's domain name. When accessing https://clientdomainname.com:8443 the browser uses the hostname's certificate and sees the mismatch. So you have 3 options here:
  • Use https://servername.com:8443 (any customer can access it)
  • Set up another domain name to access Plesk and use the option "customize Plesk URL" in Tools & Settings.
  • Use UCC SSL certificate covering several domains
Some details can be found here: https://support.plesk.com/hc/en-us/articles/115002338353
 
Thanks Yaroslav for the info! That's what I kind of thought but wasn't sure. This information should also be in the Log In to Plesk document where there is no indication that logging in with a customer domain name will give a privacy error message.
Thanks!
 
Back
Top