• 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 Connection to Plesk via HTTPS is shown as not secured

stathopon

New Pleskian
hello to everyone,

i have a plesk server which is not working the SSL for one of my client,
it says that there is not a SSL protection in his mail.

what can i do?

I am trying to log in to my plesk account nsr.mysite:8443 and its appear

Your connection is not private
Attackers might be trying to steal your information from nsr.server1.gr (for example, passwords, messages, or credit cards). Learn more

NET::ERR_CERT_COMMON_NAME_INVALID

ADVANCED and logging with unsecure environment!
what can i do?
 
Generally speaking, Plesk assigns a single certificate to the control panel access and a single certificate to mail servers. So if you're accessing either under different server names than those specified in the certificate, you will get SSL/TLS warnings.

To actually investigate the mail connection issue, we'd need to know which settings is your client using for their email access. IMAP/POP3 server name, SMTP server name, ports, SSL/TLS settings, etc. At the same time, we'd need to know the actual hostname of your server.

As for investigating the control panel access, we'd also need to know the hostname of the server and the actual address you're using for access.
 
Back
Top