Custom Query (8144 matches)


Show under each result:

Results (433 - 435 of 8144)

Ticket Resolution Summary Owner Reporter
#11965 outdated I can't connect to all of my servers with FileZilla since today algizodal

I can't connect to all of my servers with FileZilla since today, I have an error "Data connection cannot be established: WSAEADDRNOTAVAIL - Unable to assign the requested address"

Please, could you help me?

PS. I use Vesta control panel - I install it before trying to connect with FileZilla

Logs: =============================================== Status: Connecting to *MY HOST*... Status: Connection established, waiting for welcome message... Status: Insecure server, it does not support FTP over TLS. Status: Logged in Status: Retrieving directory listing... Command: PWD Response: 257 "/" Command: TYPE I Response: 200 Switching to Binary mode. Command: PASV Response: 227 Entering Passive Mode (136,244,116,96,47,48). Command: LIST Error: The data connection could not be established: WSAEADDRNOTAVAIL - Cannot assign requested address Response: 150 Here comes the directory listing. Response: 226 Directory send OK. Error: Failed to retrieve directory listing

#11958 worksforme Download and add files to queue are greyed out Chris Lahiff

Download and add files to queue are greyed out

#11955 worksforme For s3 connection, FZ ignores "host:" configuration box so impossible to connect to local s3 server ( Richard Jelbert

I am running a local s3 server on my local network and FileZilla Pro can not connect to it.

I set the hostname to my s3 server network IP address but I can see in the access logs that FZ ignores my host entry and simply uses an Amazon address instead which of course fails.

The host IP address is entered in the "Host:" box as and Port: 9000 however FZ Pro shows that it is trying to access a different server: Retrieving directory listing... Status: Resolving address of Status: Connecting to Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing ... so it looks like it has used my port number but ignored my host IP address and used something from AWS or something internal instead. This seems to be a bug because it is entirely reasonable to expect "Host:" to allow me to connect to a s3 server at my own IP address.

My app and mac details are: FileZilla Pro

Version: 3.43.0

Build information:

Compiled for: x86_64-apple-darwin18.6.0 Compiled on: x86_64-apple-darwin18.6.0 Build date: 2019-06-27 Compiled with: Apple LLVM version 10.0.1 (clang-1001.0.46.4) Compiler flags: -Werror=partial-availability -Wall -g

Linked against:

wxWidgets: 3.0.5 SQLite: 3.26.0 GnuTLS: 3.6.7

Operating system:

Name: Mac OS X (Darwin 18.6.0 x86_64) Version: 10.14 CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: /Users/richardj/.config/filezilla/

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.