Custom Query (8144 matches)
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 | ||
Description |
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 | ||
Description |
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 (min.io) | ||
Description |
I am running a local min.io s3 server on my local network and FileZilla Pro can not connect to it. I set the hostname to my min.io 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 192.168.0.43 and Port: 9000 however FZ Pro shows that it is trying to access a different server: Retrieving directory listing... Status: Resolving address of s3.dualstack.us-east-1.amazonaws.com Status: Connecting to 52.216.9.37:9000... 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:
Linked against:
Operating system:
|