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

Same box moving domain to different IP

J

jpwdesigns

Guest
Hi I'm trying to move a domain from one ip to another on the same box. Why cant plesk direct traffic for domain correctly while i'm waiting for dns propagation? is there a way to tell the server what to do with requests for the domain for both ip addresses?
 
If I correctly understood you want that all requests to hostname with old assigned IP will be redirected by Plesk to new IP till this new IP will be assigned to hostname by nameservers?
Well. In this case how Plesk will know that hostname already updated with new IP on nameservers and old IP should be released? Also old IP should be released immediately because it may be used by others new domains especially when Plesk managed by automation systems like POA, Expand or PBAS.
So, it is interesting idea but not sure that such possibility can be implemented due to mentioned reasons.
 
Back
Top