• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

move ip's on the server (normally for SSL)

ollybee

New Pleskian
I can only have a site configured on one ip at a time.
This is a problem when I have a site configured on a shared ip and I want to move it to a dedicated for use with an SSL.
While the DNS update propagates either I may get requests for the site on either IP, only one of which can work.
I can mitigate this problem by reducing the TTL od the DNS records, if I have control; or making the change at at night.

Is there a better way to move a site to a new ip on the server without any downtime ?
 
I can only have a site configured on one ip at a time.

That is true for Plesk ...

When moving a website from a shared IP, the new server should also have a shared IP and thus a domain is moved from shared to shared IP, while for dedicated IP is must also be moved to a dedicated IP address.
 
Back
Top