• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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