• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Plesk 12 delivers wrong site if subdomain does not exist

southy

Basic Pleskian
Hi all,

I have a domain that has an DNS-record:
* A [IP of plesk server]
DNS is not managed by plesk, but seperately.

For the domain.com, a site is existing.
However if someone opens [any string].domain.com , _another_ client's site from that server opens up.

Shouldn't accessing a non-existent site call for an error page or a plesk-standard-page?

What's going wrong here?
 
Back
Top