• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

FTP Error, 550 the filename directory name or volume label syntax is incorrect

Status
Not open for further replies.

krt463

New Pleskian
Hello, we have several installations of plesk 11.5 for Windows.

It was just brought to our attention today that when a new FTP user is created and allowed access to / They receive the following erorr after logging in and trying to access another directory:

"550 the filename directory name or volume label syntax is incorrect"

Two things to note:

1. The original FTP user that is created with the subscription continues to work without issue as expected. This error only applies to the next FTP users that are created under the same subscription;

2. If you change the root directory for the new user to /httpdocs or any other directory than /, it works correctly as well.

Any ideas on how to fix this behavior so new FTP users will be able to navigate folders correctly?
 
Ok. Please tell me ticket ID. I would like to monitor processing. Thank you.
 
Ok. Please tell me ticket ID. I would like to monitor processing. Thank you.

Confirmed a PVC issue and they provided a work around script ( a replacement PHP file for: C:\Program Files (x86)\Parallels\Plesk\admin\plib\Ftp\UserManager\Abstract.php)

They say the fix will be in the next release.

Ticket ID: 1954500
 
Status
Not open for further replies.
Back
Top