Opened 3 years ago

Closed 4 months ago

#11965 closed Bug report (outdated)

I can't connect to all of my servers with FileZilla since today

Reported by: algizodal Owned by:
Priority: high Component: FileZilla Client
Keywords: WSAEADDRNOTAVAIL Cc:
Component version: 3.43.0 Operating system type: Windows
Operating system version: 10.0

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

Change History (2)

comment:1 by marc.bau, 4 months ago

I found the reason why this happens. A previous version has set FTP server listen address to the DHCP address my computer had in past e.g. 192.168.0.5. Now my DHCP address has changed to 192.168.0.8 and the software fails to bind to 192.168.0.5.

So I changed the Listeners in FTP Server > Connections > Address tab to 0.0.0.0 and the server bound the listeners properly.

This is clearly a bug I think. It would be better if filezilla would automatically bind to 0.0.0.0 only.

comment:2 by Tim Kosse, 4 months ago

Resolution: outdated
Status: newclosed

If there is a custom bind address, it has previously been entered manually by the server administrator. I recommend to maintain a changelog.

Note: See TracTickets for help on using tickets.