next error is :
2021-11-21T12:29:15.392Z >> [FTP Session 2 192.168.0.6 admin] MKD FTP
2021-11-21T12:29:15.392Z DD [File-based Authenticator/impersonator client, user: <not impersonating>] info: result: 6
2021-11-21T12:29:15.392Z << [FTP Session 2 192.168.0.6 admin] 550 Permission denied
see log attached and also the motioneye and filezillaserver config
FileZilla Server 1.1.0 + motionEye FTP transfer error 450
Moderator: Project members
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
- Attachments
-
- filezilla-server-log-211121.txt
- (629.02 KiB) Downloaded 96 times
-
- last-config.png (84.91 KiB) Viewed 2093 times
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
This line from the log, coupled with the one you posted, indicates that it's trying to create the /FTP directory, but that directory is actually your mount point.
From what I understand what you want is to have all files end up in C:\FTP.
In that case, make both the virtual path in the filezilla server and the location in your application be "/", without quotes.
Code: Select all
2021-11-21T12:29:15.343Z >> [FTP Session 2 192.168.0.6 admin] CWD /
In that case, make both the virtual path in the filezilla server and the location in your application be "/", without quotes.
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
Accessing the upload service failed: 550 Couldn't open the directory!
c:\FTP exists and all download will be saved there
Tell me the right content of the fields and I will check
see attach config file
any further IDEA ?
c:\FTP exists and all download will be saved there
Tell me the right content of the fields and I will check
see attach config file
any further IDEA ?
- Attachments
-
- not-create-log.txt
- (717.68 KiB) Downloaded 101 times
-
- not-create.png (102.43 KiB) Viewed 2072 times
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
Is C:\FTP an actual directory, or is it a symbolic link, NTFS junction, or reparse point?
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
actual Directory
-
- 504 Command not implemented
- Posts: 8
- Joined: 2021-12-29 08:21
- First name: G.
- Last name: L.
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
Hello.
The same thing happens to me too.
I have hundreds of devices that have to interact with the sub dirs of the virtual paths of each device and are no longer able to access the aforementioned.
I also opened a new Topic with the same problem.
from what I have learned it would always be that the old LIST command is no longer recognized and that it has been replaced by the DIR command.
We cannot communicate with the hundreds of devices to update the firmware of each in order to make the terminals work with the DIR command instead of the old LIST, so I ask you if it is possible to add the old LIST command with the same operation as the new one.
The same thing happens to me too.
I have hundreds of devices that have to interact with the sub dirs of the virtual paths of each device and are no longer able to access the aforementioned.
I also opened a new Topic with the same problem.
from what I have learned it would always be that the old LIST command is no longer recognized and that it has been replaced by the DIR command.
We cannot communicate with the hundreds of devices to update the firmware of each in order to make the terminals work with the DIR command instead of the old LIST, so I ask you if it is possible to add the old LIST command with the same operation as the new one.
Re: FileZilla Server 1.1.0 + motionEye FTP transfer error 450
FTP has no DIR command.
LIST still works just fine. Note that the output of LIST is not standardized and cannot be used by machines.
Consider switching to a client that uses MLSD, it is the only command to obtain directory listings in an unambiguous machine-readable format.
LIST still works just fine. Note that the output of LIST is not standardized and cannot be used by machines.
Consider switching to a client that uses MLSD, it is the only command to obtain directory listings in an unambiguous machine-readable format.