• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved How to migrate Drupal away from Plesk?

seancamden

New Pleskian
Server operating system version
Ubuntu 22.04/Debian 12
Plesk version and microupdate number
Plesk Obsidian Version 18.0.63 Update #4
I have a Drupal 7 site currently running on an Ubuntu server managed by Plesk, and I'd like to move it to a Debian server so that I can upgrade it to the current Drupal version (10).
So far I've tried simply copying the site files and the database, and creating a new vhost file, but that has not worked. Drupal serves up the "in maintenance mode" page pretty well, but nothing else will load.
Is there a guide for migrating a Drupal site away from Plesk anywhere? I don't have to use Debian, but I'd like to.
Also, if there's a way to upgrade Drupal without moving away from Plesk, I'd be interested in hearing about that, too.
 
I have a Drupal 7 site currently running on an Ubuntu server managed by Plesk, and I'd like to move it to a Debian server so that I can upgrade it to the current Drupal version (10).
So far I've tried simply copying the site files and the database, and creating a new vhost file, but that has not worked. Drupal serves up the "in maintenance mode" page pretty well, but nothing else will load.
Is there a guide for migrating a Drupal site away from Plesk anywhere? I don't have to use Debian, but I'd like to.
Also, if there's a way to upgrade Drupal without moving away from Plesk, I'd be interested in hearing about that, too.
This was actually pretty easy to fix. Corrected file permissions in DocumentRoot, and allowed overrides in the Apache config, and it's working. Now the real fun begins.
 
Back
Top