Plesk server migration

[Arkshine]

I don’t think it will work. Plesk will copy only your domain and proxy configuration. Discourse itself is not associated with Plesk; it’s a separate installation.

You can follow this guide to move your Discourse instance:

Move your Discourse Instance to a Different Server

In this guide we’ll move an existing Discourse instance on Linode (source) to a new Discourse instance on Digital Ocean (destination), but of course these steps will work on any other cloud providers that support Docker. If you are using the same domain name and moving servers, you should set the TTL (time to live) on your DNS entry to a very low value in advance of the change. If you are using different domain names, this won’t matter. Log In and Update Only admins can perform backu…

Or you can use directly the command line without booting the web UI:

Restore a backup from the command line

Here’s how to restore a Discourse backup from the command line, without ever booting the Discourse web UI. This is handy when you’re moving servers. Prerequisites Download the latest backup file from source Discourse instance. The destination discourse needs to be bootstrapped (run ./discourse-setup or copy your existing app.yml) Make sure that the destination Discourse instance is on the latest version. Update it if necessary. Transfer the backup SSH into the destination server, or otherwi…

I highly suggest you upgrade your discourse before doing a backup!

Note: Whatever the method you choose, when you Install Discourse on your new server, instead of using ./discourse-setup, copy your old app.yml in /containers, then rebuild. Since you’re using Plesk, it will be easier this way.