• 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 Issues with SSL (conflicting with expired plesk)

johnl

New Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian 18.0.45
Hello Team,

I have no idea why I get this, it's configured the same way as any other domains on the server.

I am using WordPress Multisite and have other domains that work perfectly well with SSL

If you visit: Zac Browser – Discover a world of possibilities with the most popular software for people with autism. you get:

====

Your connection is not private​

Attackers might be trying to steal your information from www.zacbrowser.com (for example, passwords, messages, or credit cards). Learn more


NET::ERR_CERT_AUTHORITY_INVALID

====

while if you use Zac Browser – Discover a world of possibilities with the most popular software for people with autism. it's working well.

if you look here: SSL Server Test: zacbrowser.com (Powered by Qualys SSL Labs) you'll see the expired plesk certificate

I have used the wildcard (including www for the subdomain) and the checkbox is showing it's fully secured for all domains including zacbrowser.com

Please help as I am losing visitors (they are scared).

Thank you
 
Back
Top