Custom Query (8168 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 8168)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#13035 worksforme File corruption problem - Feature request Bathrax Grimtoad
Description

It happens that sometimes, when the internet connection is bad, that the downloaded file is corrupted. It seems allright, but when you check it, you discover that there is some troubles in it. So it will be very useful to have a control device, like MD5 or SHA256, included into FileZilla Client to be sure that the transfer is OK. As this process is time consuming, it could be optional.

Best regards,

Bathrax.

#13032 rejected FileZilla New Update Apple Silicon chip mhogue
Description

Hi,

This morning I noticed that my private key authentication, which used to work seamlessly, is now frequently timing out. When it doesn't time out, it's taking a very long time to successfully process actions such as directory changes or file updates. My initial thought is that this might be related to the notification in my FileZilla that a new version is available. However, there doesn't appear to be a valid version available for my operating system.

I already tried making new connections to my web server. When that didn't help, I quit and restarted FileZilla, which also didn't help.

#13028 fixed Data peer IP error which aborts the data connection - reproducible with AWS EC2 Ann-at-HREF
Description

This error message came up for me today after upgrading to the latest FileZilla Server.

<Date/Time> Info [Type] Message <08-12-2023 07:15:38> FTP Session 3 34.xxx.xxx.12 (snip username) [Error] Data peer IP [172.xx.xx.xx] differs from control peer IP [34.xxx.xxx.12]: this shouldn't happen, aborting the data connection.

How to reproduce this error

You need two AWS EC2 machines which happen to be in the same region. Put FileZilla server on one of them. Put ncFtpPut client on the other one. ( Download the client from https://www.ncftp.com/ncftp/ )

When ncFtpPut tries to connect, probably due to some AWS routing optimizations, it comes through using the private IPv4 of the client machine instead of using the public IPv4. This accounts for the difference.

Hope that helps.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.