Opened 5 years ago

Closed 5 years ago

#12012 closed Bug report (worksforme)

Using TLS causes Directory Listing Timeout (it used to work fine)

Reported by: dbareis Owned by:
Priority: normal Component: FileZilla Client
Keywords: TLS, directory, timeout, ETIMEDOUT Cc:
Component version: 3.45.1 Operating system type: Windows
Operating system version: Windows 10 (build 18362), 64-bit edition

Description

In the last few months (using newest versions at the time) I have had to change from "Use explicit FTP over TLS if available" to "Only use plain FTP (insecure)" or it will timeout (30 seconds) on listing the remote directory.

FileZilla Client


Version: 3.45.1

Build information:

Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2019-09-25
Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406
Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5
SQLite: 3.29.0
GnuTLS: 3.6.9

Operating system:

Name: Windows 10 (build 18362), 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 bmi2 bmi2 lm
Settings dir: C:\Users\\AppData\Roaming\FileZilla\

Attachments (1)

DetailLogOfTimeout.txt (3.6 KB ) - added by dbareis 5 years ago.
detailed log of the connection and timeout

Download all attachments as: .zip

Change History (2)

by dbareis, 5 years ago

Attachment: DetailLogOfTimeout.txt added

detailed log of the connection and timeout

comment:1 by Tim Kosse, 5 years ago

Resolution: worksforme
Status: newclosed

A faulty firewall or NAT router is blocking the connection, most likely server-side.

You can use https://ftptest.net/ to figure out whether it's a server-side or client-side networking component.

Note: See TracTickets for help on using tickets.