Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
Ok, I have figured out what I think was causing this issue. Posting here for anyone who runs into this in the future.
1. This is important: whatever command is used by Plesk under the hood to ssh into the source server does not appear to send keep-alive requests. I think this is a bug that...
Well, I have tried it again after making the last post. Still the same result.
1. What processes should I be looking for on the source server? I have checked for anything named "migrat", but this is all I see:
# ps aux | grep migrat
root 7 0.0 0.0 0 0 ? S 2024...
All of these subscriptions are coming from the same source server, so if the 150GB subscription transferred in <30 min, I would expect these others to also transfer very quickly. Plus, as I have pointed out above the process freezes during the pre-migration check at the "Merging local and remote...
How much additional time should I allow it? It's now confirmed that the time it takes has nothing to do with disk usage. I migrated the 180GB subscription I had in <30min. Meanwhile, every time I try to migrate one of these 4 subscriptions that get stuck like this, the migrator hangs...
This command produced no output for me. I ran the following in case this would shed some light:
# tail /usr/local/psa/var/modules/panel-migrator/sessions/20260129234720/debug.log -n 25
=|2026-02-10_17:01:52,592|D|MT|core.runners.base||[/'/s/o/u/r/c/e/'/]|exit code: 0...
I recently posted a question about Plesk Migration speed (Question - Plesk Migration Obsidian to Obsidian: How Long To Expect?). It appears to be that it's a specific subscription that's bugged. Other subscriptions, even ones containing substantially more data, are migrating just fine. On the...
It is always getting stuck on the same step when I run `plesk-migrator check`. Here is the full output. I left it running overnight, and this was still the same step it was on. Is this step expected to take a long time?
# /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator check...
I am working on migrating from one server to another, both running the latest Plesk Obsidian for Linux, using the Plesk migration tool. For the smaller subscriptions, it works like a dream, but I have a few websites that take up a much larger amount of disk space, several around 30-35 GB and one...
In the end, I resolved this in the following way:
plesk bin service_plan -u "Plan Name" -php_handler_id plesk-php74-fastcgi -php_served_by_nginx false
plesk bin subscription --unlock-subscription domain.com
plesk bin subscription --sync-subscription domain.com
I should note that using the...
I'm trying to change the PHP handler for a domain from CLI. I'm using the command:
plesk bin site -u example.com -php_handler_id plesk-php74-fastcgi
I get the result:
PHP scripts cannot be processed by nginx if the Plesk CGI or FastCGI handler is selected. Either omit the "-nginx-serve-php"...
More digging:
(1) After deleting all of the config files under /var/www/vhosts/system/domain1.com/conf/ and rebuilding them with `plesk repair web domain1.com`, the server now returns the same output of File Not Found for https://www.domain3.com/item/existing-item AND...
This is a weird one. I have three domains, let's call them domain1.com, domain2.com and domain3.com.
Domain1.com is the main domain.
Domain2.com is a domain alias of domain1.com
Domain3.com is a domain alias of domain2.com
I am using the domains WITHOUT a 301 redirect. I don't want to get into...
DKIM re-enabling DID NOT help this issue. It was necessary to get DKIM working with SMTP-submitted mail after the migration.
My work-around with non_smtpd_milters is what fixed this issue for me.
I have figured out the problem. It seems that Postfix did not define milters for mail that did not come in via SMTP. This is all Mailman mail, of course. I do not use the Plesk webmail, so it might also be a problem there.
In the Postfix configuration file at /etc/postfix/main.cf, I added the...