FileZilla Forums

Hello

Had a look through the FAQ and did not see the issue listed. If I missed it I apologize.

My automatic update from version 3.32.0 to version 3.42.1 is not working. I get the following results:

Found new release 3.42.1
Downloading /FileZilla_Pro_3.42.1_win64-setup.exe
Resolving address of download.filezilla-project.org
Connecting to 136.243.154.86:443...
Connection established, initializing TLS...
Verifying certificate...
TLS connection established, sending HTTP request
Resolving address of prodownload.filezilla-project.org
Connection timed out after 20 seconds of inactivity
File transfer failed

When I go to the download page I do not see any files for the download of the pro version update.

Trying to download the latest version of normal filezilla results in a Virus warning from Avira as per the attachment.

I would appreciate it if someone could point me in the right direction.

Failures to download the update are typically caused by faulty firewalls interfering with the connection. Make sure no firewall is interfering with the connection.

You can manually download FileZilla Pro from https://filezilla-project.org/prodownload.php


In the future please refer to our customer forums for assistance with FileZilla Pro: http://customerforum.filezilla-project.org/

Thank you for the quick response.

There are no firewalls configured on the network or on the PC, but I managed to get the file downloaded from the link that you provided.

Thank you very much.

There were some issues with auto update in a few old FileZilla versions that have since been resolved. As you tried to update from a very old version, you might have run into that old bug. Should be gone now for all new releases.

boco wrote: ↑

2019-06-11 12:48

There were some issues with auto update in a few old FileZilla versions that have since been resolved. As you tried to update from a very old version, you might have run into that old bug. Should be gone now for all new releases.

That was a different issue resulting in a checksum verification error, not a timeout like in this case.