Articles in this section

See more

Password-protected root directories for domains are not migrated in Plesk for Linux

Avatar
Renan Moreira
Updated
Follow
Plesk for Linux kb: bug ext: migrator

Applicable to:

  • Plesk for Linux

Symptoms

  • Pre-migration check shows the following warning in regards to protected directories.

    PLESK_WARN: Protected directory of domain example.com
    Before migration, rename (move) protected directory on the source server. Once migration is finished, move the directory on the target back, and then recreate protected directory and its users manually.

Cause

Password-protected root directories of domains ("/") are not migrated. This is Plesk Migrator bug #EXTPLESK-1866 which will be fixed in future Plesk updates.

Resolution

As a workaround.

  1. Log into Plesk on the source server.
  2. Rename "/" password protected directory, for example to "/httpdocs/testfolder" in Domains > example.com > Password-Protected Directories > click on "/" > Directory Settings.
  3. Log into Plesk on the target server and migrate domain example.com at Extensions > Plesk Migrator
  4. Rename on the target server the password protected directory back to "/" in Domains > example.com > Password-Protected Directories > click on "/testfolder" > Directory Settings.

Comments

2 comments

Sort by Date Votes
  • Avatar
    Glenn (Edited )

    This is a real problem when you're trying to migrate some domains with a dozen subs and they're all in the root directory!

    Instructions aren't clear. 

    1
    Comment actions Permalink
  • Avatar
    Michel vd Lingen

    Useless KB article....!!!

    Issue was already reported back in September 2021 (more than a year ago)!
    See also here: https://talk.plesk.com/threads/migrator-fails-to-migrate-password-protected-directories.362164/

    However after a year this issue still has not been resolved. Also, like Glenn stated already 2 weeks ago (no answer ofcourse) it's impossible to migrate several domains which have multiple protected directories...!

    Now Plesk is increasing their pricing every year nowadays and Plesk states it's necessary to improve the functionality of Plesk and to fix bugs and others issues. Okay... How come this very old bug (older than one full year) still hasn't been solved? Aren't we paying enough already as it is? Or do we have to pay an extra price increase first to get these simple bugs fixed?

    Very, very disappointing to see Plesk not taking issues seriously other then increasing their pricing every year!!!

    1
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles