501 Couldn't open the directory

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
filezilla_user__
500 Command not understood
Posts: 3
Joined: 2022-06-29 10:52

501 Couldn't open the directory

#1 Post by filezilla_user__ » 2022-06-29 11:02

Hello.
These are the commands that run when I attempt to connect to the server:

Code: Select all

Status:	Connecting to 127.0.0.1:21...
Status:	Connection established, waiting for welcome message...
Status:	Plain FTP is insecure. Please switch to FTP over TLS.
Status:	Logged in
Status:	Retrieving directory listing...
Command:	PWD
Response:	257 "/" is current directory.
Command:	TYPE I
Response:	200 Type set to I
Command:	PASV
Response:	227 Entering Passive Mode (127,0,0,1,197,132)
Command:	MLSD
Response:	501 Couldn't open the directory
Error:	Failed to retrieve directory listing
Any ideas what could be the solution?

User avatar
boco
Contributor
Posts: 26899
Joined: 2006-05-01 03:28
Location: Germany

Re: 501 Couldn't open the directory

#2 Post by boco » 2022-06-29 12:51

Which OS?

If Windows: The account the server runs under (SYSTEM by default) does not have access to the resource you have configured as / in FileZilla Server. First, check the NTFS permissions, the server user account must have full access. Second, check if the Windows "Controlled Folder Access" feature is active and blocking access.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Please do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

filezilla_user__
500 Command not understood
Posts: 3
Joined: 2022-06-29 10:52

Re: 501 Couldn't open the directory

#3 Post by filezilla_user__ » 2022-06-30 07:44

Thanks for the answer.
I'm runnig the server on a Windows 10 pro.
You refer to NTFS permissions of the FileZilla executable file?
I checked the "Controlled Folder Access" and is off, so that's not the issue.
Last edited by filezilla_user__ on 2022-06-30 07:58, edited 1 time in total.

User avatar
botg
Site Admin
Posts: 35492
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: 501 Couldn't open the directory

#4 Post by botg » 2022-06-30 07:50

The NTFS permissions of the directory you are attempting to list through FileZilla Server.

filezilla_user__
500 Command not understood
Posts: 3
Joined: 2022-06-29 10:52

Re: 501 Couldn't open the directory

#5 Post by filezilla_user__ » 2022-06-30 08:02

I uninstalled and reinstalled the FileZilla server again, and now the server is not working.
The following is printed when I try to run the server:

Code: Select all

<Date> Info [Type] Message
<30/06/2022 7:56:50> Admin UI [Error] GnuTLS error -15: An unexpected TLS packet was received.
<30/06/2022 7:56:50> Admin UI/RMP Session, id: 0 [Error] Failed securing connection. Reason: ECONNABORTED - Connection aborted.
<30/06/2022 7:56:50> Admin UI [Error] Session ended with error from source 0. Reason: ECONNABORTED - Connection aborted.
<30/06/2022 7:56:50>  [Error] Disconnected from server 127.0.0.1:14148 with error 106 (ECONNABORTED - Connection aborted).
<30/06/2022 7:56:50> Admin UI [Status] Attempting reconnection to server 127.0.0.1:14148 in 2 seconds...

User avatar
oibaf
Contributor
Posts: 396
Joined: 2021-07-16 21:02
First name: Fabio
Last name: Alemagna

Re: 501 Couldn't open the directory

#6 Post by oibaf » 2022-07-01 16:09

Did you, by any chance, before reinstalling, configure FileZilla Server so that it would listen for FTP connection on port 14148? If so, that is what is causing your issue: the Administration part of FileZilla Server is not able to start accepting connections.

We will make this impossible to happen in the next releases, for now you ought to modify the configuration file by hand.

As administrator, you should edit the file settings.xml within the folder C:\Windows\System32\config\systemprofile\AppData\Local\filezilla-server. In that file, locate the <ftp_server> node, then within that note locate the <listener> node that contains the <port>14148</port> entry. Delete that <listener> node, save the file and restart the service. You should then be able to connect again with the administration interface.

User avatar
botg
Site Admin
Posts: 35492
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: 501 Couldn't open the directory

#7 Post by botg » 2022-07-04 07:35

There is an easier workaround: Reinstall and during installation pick a different admin port.

Post Reply