• 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!
  • 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.

Issue Access to Plesk

neighbourtom

New Pleskian
Server operating system version
Debian 10.0 / 64 bit
Plesk version and microupdate number
Version 18.0.56 Update Nr. 4
Hello there,

I'm trying to get access to Plesk via another domain.
The first domain is https://[domain 1 redacted].com:8443. It's working fine, but it's canceled, so the access is limited of course.
Now Im trying to get access via https://[domain 2 redacted]:8443, but I can't get it running with SSL.

Do you have an idea?

Thank you.
Best regards
Thomas
 
Last edited by a moderator:
Hi! As an example, you should be able to connect to Plesk via ip-address, https://ip.ad.dr.ess:8443/ and ignore SSL certificate for the first time, reconfigure the Plesk to use the second domain and protect it with new SSL certificate. Also, check "Tools & Settings > Customize Plesk URL" and update if required. After that, you should be able to connect to Plesk with using the second domain without any issues.

(yesterday I did the same on my own Plesk :) )
 
Back
Top