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.
It seems like the problem is with the reseller plan, or the reseller user itself. If we take an account that is on this reseller, and move it to a new provider then everything seems to be working so far.
Yes, that was the first thing we checked, and I posted a screenshot showing that the reseller plan has the two permissions. Sorry, I must not have explained that clearly enough.
After moving all of the subscriptions to the new hosting service plans we're still seeing the same issue. Scheduler management and Remote access for database users is still missing, and can't be enabled. In the meantime we've gone through and added these features to each subscription manually...
I think I may have solved it. These hosting service plans have existed since 2021 and we've just been copying and duplicating and editing them over each time. If I create a new hosting service plan from scratch I am able to grant the remote access for database users, and scheduler management as...
We've been using Plesk since 2021 and have always been able to grant remote database access and scheduled tasks permissions to our hosting service plans. Recently we tried to change some unrelated option on our hosting service plans, and the change failed because the option "Remote access for...
I'm getting the same error message with Ruby on Rails on Plesk 18.0.67 Update #2.
Steps to reproduce:
Websites & Domains > Get Started > Ruby
The error appears near the top of the page as it's loading.
Here's the error from /var/log/plesk/panel.log:
[2025-02-12 13:31:48.652]...
After the output I posted above the restore didn't create their home directory or restore any of the files or create any of their domains. I already created a new account with the same username and domains as the person had before, and sent them the backup file to extract and restore the files...
Hello,
I created a full backup of a Plesk account that was using webalizer, and now I'm trying to run plesk bin pleskrestore on the .tar file backup on a server that doesn't have webalizer installed. I get this error
<?xml version="1.0" encoding="UTF-8"?>
<restore status="warnings"...
So it looks like the webui is using a json formatted migration-list file, and it's tacking these flags to the end of the transfer-accounts command:
--skip-services-checks --skip-infrastructure-checks --skip-main-node-disk-space-checks --skip-license-checks --skip-capability-checks...
I may have made some progress. I was looking in
/usr/local/psa/var/modules/panel-migrator/sessions/migration-session/
Like the documents you linked mention, but it looks like the webui migrator is actually using
/usr/local/psa/var/modules/panel-migrator/sessions/20210824152228/
Snooping...
This is the error that I get on the command line for one account
Detailed Migration Status
│
└ warning: Subscription 'example.com' does not exists on source server(s).
Probably it was removed from the source server since migration was started.
Migration of that subscription will be skipped...