• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

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