fileZilla server more 260 chars error, win 10 LongPathEnabled=1

[vg2k]

Win 10
LongPathEnabled = 1 (gpedit and regedit) check via win cmd
FileZilla Server with long client path more 260 chars
got error on upload (create sub folder )
ftp client see it like custom client errors like "Filename invalid" "Internal error creating the directory." and etc

[vg2k]

I FOUND ONLY ONE SOLUTION (WIN 10 works fine)

steps:

1. enable win long path (not for all soft)
1.1 Win+R -> gpedit.msc
1.2 Local Computer Policy -> Computer Configuration -> Administrative Templates -> System -> Filesystem -> NTFS (or one folder up)
1.3 set Enable NTFS long paths = 1

2. change Filezilla server target folder in config (texteditor) to UNC path
2.1 Setup the account in the UI. Point the directory to “c:temp” or similar.
2.2 Open up the “FileZilla Server.xml” located in the Filezilla install directory.
2.3 Find the corresponding user node “<User Name=”{username}”>
2.4 Under “<Permissions>” you will have an entry for each folder setup. Change the <Permission Dir=”C:temp”> to <Permission Dir=”\\?\C:temp”>
2.5 full reboot Filezilla server (windows)

[boco]

Beware! The \\?\X:\path\file syntax accesses the filesystem directly. I's possible to create some files or directories with names that would be invalid otherwise (CON, NUL, AUX, LPT1, COM1 etc.). Such files cannot be deleted by Explorer, but only by the same syntax used before.

[mark.antao]

Am able to see the hosted files that breach the 260-char limit (they were previously not visible), using the UNC workaround suggested above. Long Path has been enabled in Win 10.

However, am unable to download these files (refer screen snapshot below). Am using FileZilla Server 1.5.1 and FileZilla Client 3.62.0

Attachment.png (121.25 KiB) Viewed 2970 times

Any assistance is appreciated.

[oibaf]

Could you please post the log from the server, whose level has to be set to "5 - Debug"?

[mark.antao]

Attached herewith is a copy of the server log set at 5-Debug

filezilla-server.log

(21.63 KiB) Downloaded 54 times

We have done two tests - one where path length does not exceed 260 (download succeeds) and second where path length exceeds 260 (download fails).

Both files are in the same remote folder and are being downloaded to the same local folder.

[mark.antao]

It would appear that LN 218 in the server log is the key to understanding why the download of a long path file fails (LN 234, LN 238 & LN 242), when a short path one succeeds (LN 92 & LN 139).

The UNC workaround has been confirmed working by others, and yet FileZilla Server reports inability to open the long path file / directory, though the same can be opened and modified using File Explorer.

A bit lost and any suggestions are most appreciated.

[botg]

Windows itself isn't even ready for long path support, not even Explorer can handle long paths.

We won't make any changes to long path support in FileZilla Server until Windows itself is ready.

If your use-case absolutely requires longer paths, consider switching to Linux and run FileZilla Server on that operating system instead.