• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Issue Move primary domain to another subscription fails with "invalid path specified"

websavers

Regular Pleskian
Had this happen with a domain today. The domain being moved is a primary domain of a subscription and the only one left in that subscription. Plesk just said it couldn't move the domain because "invalid path specified". This occurs when there's an FTP account that's pointing to an invalid path. If you get this error the solution is to:

1. In the target subscription create a backup of the folder with the name of the domain being moved, then remove that folder (otherwise you won't be able to select this subscription as a target for this domain move again)
2. In the source subscription, go to FTP users and remove any users which say they are pointing to an invalid path
3. Move the domain again

It will work now.

Plesk devs: should probably just remove the FTP user (as it likely wasn't working before *anyway* without a valid home path) and indicate that in the post-domain-move report.
 
Back
Top