Not able to access folder shared via Filezilla

[Healthvue]

We have shared some folder using FileZilla server to our client , so that they can have access to the folder. However, the client is getting an error(Screenshot attached).
Using latest filezilla version.

[Tim Kosse]

What does it say in the server log?

[Healthvue]

Added the logs in the attachment.

[Tim Kosse]

First log: Which mount points do you have configured in the server?

Second log: Which client are you using? Looks like it is outdated.

[Healthvue]

Mount Point- Screenshot attached.
User(Test_VL) is using WinSCP to connect to this mount point.
For quicker resolution can we connect over a call.

[Tim Kosse]

Please update the server to 1.2.0

According to log1.PNG you are attempting to list "/" but according to the mountPoint.PNG there is directory mounted at "/"

Make sure to access "/test_FTP" or add a mount under "/" if you don't want to configure the initial path in your client.

[Healthvue]

As per the instruction mentioned given initial path as "/" ,attached in screenshot. But still facing the same issue as mentioned in pervious chats.

[Tim Kosse]

Please update the server to 1.2.0

[Healthvue]

Updated FileZilla to 1.2.0 version.
For quicker resolution can we connect over a call.

[Tim Kosse]

Calls are not archiveable and not searchable.

Does the Windows account the FileZilla Server service runs under, SYSTEM by default, have permission to access the target directory?

[Healthvue]

There are few users who are able to access the folders which they are permitted to access. But most of them are not able to.

We have all the permissions set to the SYSTEM account.

[Marco Peroni]

I noticed a similar flaw which perhaps explains the problem: when I save the configuration Filezilla Server remove some "/" from the native PATH:
for example I write
10.10.0.126\ftp_dream\Dream\dreams\UPLOAD
but, when I apply it save
10.10.0.126\ftp_dreamDreamdreamsUPLOAD causing the same error reported here.. it could be an explanation, however it is a mistake to correct

[Healthvue]

As commented by Marco Peroni, this issue exists for other users as well and might be a software bug. What is the workaround for this and a permanent solution for the same?

[Healthvue]

Any information on the workaround for inaccessibility of folders and files shared via FileZilla?

[Marco Peroni]

this is only a workaround: I opened the configuration file, corrected the path string adding the slashes mistakenly removed by the software bug and restarted the service... but this is only a temporary workaround because if you modify the configuration and save again you have to repeat the workaround. We hope that the developers will provide a patch to fix this flaw

[Tim Kosse]

I've been able to reproduce this issue.

[Healthvue]

Thank you Marco Peroni for following up. @Tim Kosse, can you please suggest a resolution to this issue as this is adversely affecting the production environment and performance?

[Fabio Alemagna]

This should be a solved problem in 1.3.0. Closing this ticket. Please reopen if the problem still persists.