Custom Query (8117 matches)

I'm not sure whether this bug is reporting directory listing failures on client-local or server directories, but I'm seeing a very abbreviated server directory listing for one of my server directories.

I can see them all fine by logging in to the server via Putty, and I can't see any variation in the permissions that would prevent the listing.

Curiously, of the directory and files that are listed, only one of them actually exists on the server, all the ones from the synchronized client listing (which is accurate) also appear in the server listing (those include the one listed that actually exists on the server), and then there are two listed in the server listing that do not exist on either side.

This seems like a quite serious bug, disabling FileZilla when the bug is triggered. I have no idea what triggers it, not all directory listings seem as incomplete as this one I was trying to access today.

FileZilla Client

Version: 3.56.2

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2021-10-27 Compiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110 Compiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type

Linked against:

wxWidgets: 3.0.6 SQLite: 3.35.5 GnuTLS: 3.7.2

Operating system:

Name: Windows 10 (build 19042), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi bmi2 adx lm Settings dir: C:\Users\glenn\AppData\Roaming\FileZilla\

When trying to connect to the server, I receive the following error:

"Critical error: Could not connect to server"

Hello, my Client got an Problem where she couldnt log in in our FTP Server it worked before but now she only gets the error Failed to connect to the server, on other PCs it worked but for her not. Is it maybe because she is using a vpn to connect to our Server and using wlan that it is too slow.

best regards Adrian Reider