• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Migrator fails to migrate password protected directories

Hangover2

Regular Pleskian
Username: Hangover2

TITLE

Migrator fails to migrate password protected directories

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.38 Update #2, Debian 10.10, x86-64

PROBLEM DESCRIPTION

Using the Plesk "Migration & Transfer Manager" between two Plesk servers for subscriptions having password protected directories (via "WordPress Toolkit" or manually created) will lead to strange warnings and not migrated password protected directories.

STEPS TO REPRODUCE

- create a subscription with e.g. two domains "domain-a.com" + "domain-b.com"
- first domain: create a password protection in the "/" directory
- second domain: install WordPress via "WordPress Toolkit" and also enable password protection
- migrate the subscription to a new Plesk server with the Plesk "Migration & Transfer Manager" tool

ACTUAL RESULT

- the pre-check of the "Migration & Transfer Manager" will show two strange error messages:
Code:
Client "Test-Customer" - Subscription "domain-a.com"
Protected directory '' of domain 'domain-a.com' can not be created in Plesk: it does not conform to Plesk rules.
Before migration, you can rename (move) protected directory on the source server. Once migration is finished, you can move the directory on the target to a place which conforms to Plesk rules, and then recreate protected directory and its users manually.
Client "Test-Customer" - Subscription "domain-b.com"
Protected directory '' of domain 'domain-b.com' can not be created in Plesk: it does not conform to Plesk rules.
Before migration, you can rename (move) protected directory on the source server. Once migration is finished, you can move the directory on the target to a place which conforms to Plesk rules, and then recreate protected directory and its users manually.
- after migration is done, the password protection of both domains is missing

EXPECTED RESULT

- password protected directories should be migrated correctly (WordPress Toolkit same as manually created ones)

ANY ADDITIONAL INFORMATION

- in some of our older subscriptions with password protected directories we do not have this problem and they are migrated correctly without any issues
- those older subscriptions have two leading slashes "/ /" for all password protected directories, e.g. created by WordPress Toolkit
- it looks like this behavior was changed leading nowadays to the migration issues we did not experience before

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
After more than a year, is still not resolved?!

Or is it "still known issue"...? That would be very bad ofcourse. Especially since the upcoming price increase again. No clue for what the increased prices is being used. Certainly not for improving Plesk of fixing bugs as it seems...
 
The whole migrator seems not to have a high priority anymore as it has a lot of serious open bugs. We stopped using it whenever possible. We did not have one single migration in the past that was ok out of the box. Data was missing, settings were not transferred, [the list is endless]. I remember the discussion when the distribution upgrade procedure was planned to be stopped in favor of the migrator tool. Luckily this idea was quickly discarded.
 
Great workaround... Do that with 30 or 40 websites you have to migrate... Great fun. This is bug, which is over a year old already.
Probably they will need to increase the Plesk license prices again before they fix a simple bug like this...

Peter Deblik famous last words before he retired (Community Manager until 3/2024):
Plesk has plans to update Plesk Migrator this year. I hope it'll fix most known issues.
Posted on 20th of February 2024

 
Back
Top