FileZilla Forums

I'm setting up an FTP server with Filezilla for a client to use the scan to folder function on their plotter/scanner. Everything seems to be set up correctly but whenever I have the client attempt to scan the file/pdf shows up in the log but the next response is "550 This function is not supported on this system". I have a screenshot of the log attached.

Only other thing I've seen resembling this error is another forum post that made it sound like this is an issue with latest version of filezilla, 1.8.1, since they reverted to the previous version, 1.8.0, and their problem went away.

Any assistance with this would be appreciated. If you need any additional information, please let me know.

The error message is a bit misleading due to harmless regression that does not affect the 5yz response code. Your client is trying to download a file that simply does not exist.

It doesn't exist? The plotter/scanner scans and creates a pdf. Is it just not receiving the actual scan and the pdf it lists is just a placeholder name? If that's the case, is there any solution to this?

Otherwise, as I stated in my original post, I saw a post similar to this and it seemed like a solution for them was to revert to version 1.8.0. If that works, how do I get the 1.8.0 version of Filezilla?

The log you've posted shows an attempt to RETRieve a file from the root of the virtual filesystem associated with the user "scanuser". If you are sure the file does exist, then the reason it cannot be found must be in the mount list for that user.

Make sure that the virtual path "/" points to the actual native folder where the file is supposed to be. Altenatively, make sure that the client looks for the file in the right virtual directory.

Here's what I have set for the virtual and native paths.

We have a similar setup with another client set the same way and they have no problems. The other client is running 1.6.7 though. That is the only difference.

Not sure what more I could change.

Confirmed, downgrading to 1.8.0 works.
You can get all versions from official server https://download.filezilla-project.org/server/
Sending from other Windows machine through Filezilla Client or other ftp clients worked, so it thought it was a problem of the multifunction scanner (Ricoh), but it seems that downgrading to 1.8.0 did the trick.

HI,
I'm joining the discussion too because I have the exact same problem.
I have a server used to receive scans from multifunction printers and everything works normally with FileZilla Server version 0.9.60. I decide to update to the latest version which is currently 1.8.0, I redo the entire configuration and everything works again.
1.8.1 comes out and I decide to update and here the problem arises, no scanner works anymore and the errors are identical to those mentioned in the first post.
What is said is not true, that is, that the file does not exist since the only thing that has changed is the version of the ftp server, with 1.8.0 the file is created correctly and copied to ftp, filezilla server 1.8.1 however it doesn't work anymore.
Luckily I took a snap before updating because returning to 1.8.0 made everything work again.
I did some tests in vm and it's exactly like this, what works in 1.8.0 stops working in 1.8.1.
This only happens to me when scanning from multifunction printers, but if I use the FileZilla Client I have no problems with any version of the server.
In 1.8.1 the command RETR filename.pdf is received, in 1.8.0 however the command changes and is always RETR (File not Found), however followed by a STOR filename.pdf

Screen of version 1.8.1
Screen of version 1.8.0

That's actually a problem in the FTP client, the 1.8.0 success vs. 1.8.1 fail is only a symptom.

Looks like your FTP client interprets the response text, which it must never do except in a few, well defined cases (like PASV or EPSV responses). FTP clients must only rely on the response code, which is the same in both cases (550). The text is for humans only and can vary greatly between server implementations.

To my knowledge, the text has been corrected in all versions higher than 1.8.1. Unfortunately, they have been released only for Pro Enterprise Server (currently at 1.8.7). Just wait or try a Nightly until the next release.

Hi, thanks for the reply.
I confirm that everything is working again with the nightly.
So for now I'll stick with 1.8.0 and wait for an official update.
Thank you
Thank you very much