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

Question SSL error https://52.***.***.***:8443/

Anirudh

New Pleskian
Can someone please give me a step by step guide to remove ssl error for plesk web server backend?

I am using Plesk on Azure VM.
 
Well you can still access Plesk with non secured port with the port 8880 instead of 8443 . However that is not recommended.

Regarding the SSL error you get its because the SSL certificate is self signed so no need to worry about it.
 
Bad idea. It would be much better if you protect your Plesk Admin interface with the certificate from built-in LetsEncrypt extension instead of default self signed certificate.
 
Bad idea. It would be much better if you protect your Plesk Admin interface with the certificate from built-in LetsEncrypt extension instead of default self signed certificate.
How? I don't need see Full hostname in LetsEncrpt
 
Back
Top