• 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 Servers in DMZ / Private Subnet

L

lib99

Guest
Hi - I've been unable to find this answer. My plesk servers are in a DMZ and I would like to change the subnet to a private subnet and use NAT from the firewall. If I do so, then each domain will be assigned a private IP and that IP is populated to the DNS. The DNS then needs to be changed from private IP so as to reflect the public IP's. However, how will the domain (server) understand the public vs private IP??
 
I found a recently updated Plesk KB article that seems to confirm and answer my question. For the benefit of others...

My server is behind NAT and I cannot access a domain, get DNS or "connection cannot be established" error in the browser. http://kb.swsoft.com/en/1984

Make sure that the real IP addresses (but not the internal ones, like 192.168.x.x) are used in the DNS zones in Plesk for the domains. To achieve that, you should change all zones manually or setup DNS template on the Server->DNS with real IP addresses and rebuild DNS zones accordingly the template.
 
Back
Top