Custom Query (4044 matches)

Why is Filezilla constantly damaging pdf and swf and even animated gif files. Those files will not play or show when uploaded with Filezilla. This is going on for quite a while now, no matter wether you are uploading as ASCII or Binair or automatic.

When i use WinSCP the files arrive o.k. at the ftp server.

Help! cause i love FileZilla.

Hello,

I am desperately trying to configure a fileZilla account through my host media temple. I am following the instructions to s T but keep getting the following error:

Command: USER mcd-productions.com Response: 331 User mcd-productions.com OK. Password required Command: PASS Response: 530 Authentication failed, sorry Error: Critical error Error: Could not connect to server

PLEASE HELP!

adamoskii@…

Logs in successfully however the directory listing says it is empty. It has been working properly for months this just happened out of nowhere.

I sign into my Filezilla account just about every day to check on incoming work for my home business. Today, when I tried to login, I received the "Could Not Connect To Server" Error. This is how it looks:

Error: Could not connect to server Status: Waiting to retry... Status: Connecting to 174.32.139.150:21... Error: Connection timed out Trace: CFtpControlSocket::ResetOperation(2114) Trace: CControlSocket::ResetOperation(2114) Error: Could not connect to server

It is vital that I have filezilla up and running for my business. I have checked other tickets for problems connecting to the server and I cannot find the help I need. Please HELP!

Status: Resolving address of hdclean.co.il Status: Connecting to 80.179.24.66:21... Error: Connection timed out Error: Could not connect to server Status: Waiting to retry... Status: Resolving address of hdclean.co.il Status: Connecting to 80.179.24.66:21... Error: Connection timed out Error: Could not connect to server

Just found out about this due to a recurrent series of website hacks which seem on investigation to be to this error.

It's really lax. Even if FZ is not being used at the time, any virus or malware can scoop up the ftp addresses, usernames and passwords.

I have been recommending FZ for years, but I am now putting out an advisory to stop using it as a matter of urgency. For those using it to manage a lot of sites, a single infection on a client machine could trigger weeks of server clean-up work.

And I'm frankly shocked by the developer's response to tickets and forum posts on this over the years. It borders on negligence for such an otherwise excellent tool.

I right-clicked on a directory (that contained a lot of subdirectories with thousands of files) on the server and selected "download".

During the download process I lost connection a few times and sometimes had to restart filezilla (because of another bug, that sometimes you can't resume processing a queue until you restart filezilla), but then I always resumed; that shouldn't be a problem at all. I never, ever deleted anything from the queue nor did I ever receive any error prompt to which I could have given the wrong answer.

After hours of downloading, the queue was finally empty and FileZilla was apparently done downloading. Then I found out that more than half of the directory tree simply HADN'T BEEN DOWNLOADED.

I don't know whether the missing directories have never got into the queue (I'm ALMOST sure this was the case) or if they did and then they failed to download, but in both cases SILENTLY failing to download is a disaster.

If a queue becomes empty and you haven't explicitely deleted anything from it, you must be 100% sure that everything in it has been downloaded. And if you download a folder, you must have 100% guarantee that all its contents get added to the queue.

I SUSPECT that the queue is built (i.e. the directory tree scanned) while the download is ongoing, so in case of huge directories, if the download is interrupted and resumed, maybe the scanning of the directory is not resumed properly. If that is the case, than that is the bug. Either the whole scanning of directories and queuing of files should be done prior to starting to download, OR actions should be taken to ensure that in case of interruptions the scanning is resumed reliably.

Assuming that downloading a directory tree is always done without the slightest network error or without restarting FileZilla from the beginning to the end in one chunk, is a ridiculous assumption.

My install of FileZilla just updated (to 3.6.0). To reproduce the bug: open an SFTP site, exit out of FileZilla, then open Windows Task Manager. Both 'filezilla.exe' and 'fzsftp.exe' remain running.

I call FileZilla from a VBScript, and my program continues only after exiting FileZilla. After installing the latest version, exiting FileZilla did not allow my process to continue.

Opening Windows Task Manager, it became evident that closing the FileZilla interface does *not* halt 'filezilla.exe' or 'fzsftp.exe'; both of these remain resident in memory despite exiting-out of FileZilla.

Opening FileZilla manually and connecting to an SFTP site causes the same behavior. The behavior only manifests if an SFTP site is opened.

When i start filezilla client,i crash.

问题签名:
  问题事件名称:	APPCRASH
  应用程序名:	filezilla.exe
  应用程序版本:	3.7.3.0
  应用程序时间戳:	52029f25
  故障模块名称:	msftedit.DLL
  故障模块版本:	6.2.9200.16384
  故障模块时间戳:	50108893
  异常代码:	c0000005
  异常偏移:	0009fabf
  OS 版本:	6.2.9200.2.0.0.256.4
  区域设置 ID:	2052
  其他信息 1:	ccc2
  其他信息 2:	ccc26e050958f1c9740725e357b088e2
  其他信息 3:	d905
  其他信息 4:	d905c4a6e8c4f293bb902da09930cc0e

Sytetm: windows 8 Enterprise 64bit

Hi, I run Windows XP SP2, and I had no problems till I upgraded to ver. 3.7.4.1. Now File Zilla crashes within seconds of it being started. Not only it crashes, but the computer shuts down and it restarts on its own. Please help. Thanks.

Hi,

After upgrade Filezilla to version 3.9.0.1 i've notice, that sometimes when i "right click" (two fingers) on my macbook with maverics 10.9.4 filezilla recognize it like left click (one finger click). In the prev version, all works well. But if i click again it works ok.

bonjour, je viens de faire des mises à jour sur mon site avec l'avant dernière version de filezilla et tout s'est bien passé. puis j'ai fait la mise à jour de filezilla version 3.9.0.3 et depuis, je ne peux plus me connecter sur le serveur de mon site ! voilà ce que j'obtiens : Statut : Résolution de l'adresse de s145994011.onlinehome.fr Statut : Connexion à 82.165.86.87:21... Statut : Échec de la tentative de connexion avec "EACCES - Autorisation refusée". Erreur : Impossible d'établir une connexion au serveur Statut : Attente avant nouvel essai...

alors que juste avant la mise à jour cela fonctionnait correctement ! que dois-je faire ? Cordialement, Jean-Paul Pérot.

Hi All,

something very very strange is happening to me.

Yesterday at some point Filezilla lost all password.

Now:

Im not able to directly install the new version FileZilla_3.9.0.5_win32-setup.exe getting "Product Configuration Missing"

with the zip file i can lounch filezilla but..

if i import my backup it works untile i enter in the Site Manager. As soon i enter in the Site Maneger all my 20 ftp site change instantly from "normal Access" to "ask for password"

i already tried several times

On launching the past two or three versions of FileZilla the top menu bar of the program is not visible. There is no way to "drag the window" to make it visible. It is somehow being blocked by the system menu bar, therefore there is no way to "quick connect."

This must be a compatibility issue with the very latest Mac OS because I don't have this problem on another machine that has not yet been updated with the latest OS.

Also, "component" select menu (below this window) was not allowing me to select the component, which I believe is "client." Seems to work when previewing the ticket.

Total crash, I just installed the update from Beta 2 to rc1 and it crashes instantly... there isn't much to tell I even tried passing it through GNU debugger but it did have anything usable without debugging symbols...

Fault bucket 753968117, type 17

Faulting application name: filezilla.exe, 
version: 3.10.0.0, 
time stamp: 0x00000006

Faulting module name: filezilla.exe, 
version: 3.10.0.0, 
time stamp: 0x00000006

Exception code: 0xc0000005
Fault offset: 0x009c4d87
Faulting process id: 0xdb8
Faulting application start time: 0x01d026edf8cbe7ad

Faulting application path: 
C:\Program Files (x86)\FileZilla\filezilla.exe

Faulting module path: 
C:\Program Files (x86)\FileZilla\filezilla.exe

Report Id: 46d125af-92e1-11e4-afcd-001e33825849

Program received signal SIGSEGV, Segmentation fault.

0x00dc4d87 in ?? ()

(gdb) bt
#0  0x00dc4d87 in ?? ()
#1  0x004a5b1a in ?? ()
#2  0x004a66b8 in ?? ()
#3  0x005a115b in ?? ()

[Inferior 1 (process 3512) exited with code 030000000005]

I am attaching the windows Error report file its a txt file so any text editor should be able to read it...

but... WinDbg is helpful O_o

(47c.228): Break instruction exception - code 80000003 (first chance)

I take it you forgot to remove a break point lol.... O_o

When I try to connect with my personal ftp server it give me a error that the certificate expired 7/16/2013 and will not allow me to trust the certificate and give me errors when I connect so I can no longer connect with the FTP server. I have been using this server for years on a daily basis and have never seen this error.

When I try to connect to my hosting, tries connect and then disconnect me and does not show the file list.

Status: Resolving address xxxxxxxxxxxxxxxxxxxx.xxx Status: Connecting to xxx.xxx.xxx.xxx:21 ... Status: Connection established, waiting for welcome message ... Status: Initializing TLS ... Status: Verifying certificate ... Status: TLS connection established. Status: Server does not support non-ASCII characters. Status: Online Status: Retrieving directory listing ... Command: PWD Response: 257 "/" is your current location Command: TYPE I Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (108,61,29,155,37,151) Command: MLSD Error: Connection timed wait Error: Failed to retrieve directory listing Status: Resolving address xxxxxxxxxxxxxxxxxxxx.xxx Status: Connecting to xxx.xxx.xxx.xxx:21 ... Status: Connection established, waiting for welcome message ... Status: Initializing TLS ... Status: Verifying certificate ... Status: TLS connection established. Status: Server does not support non-ASCII characters. Status: Online Status: Retrieving directory listing ... Command: PWD Response: 257 "/" is your current location Command: TYPE I Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (108,61,29,155,218,184) Command: MLSD Error: Connection timed wait Error: Failed to retrieve directory listing

On new FileZilla_3.10.1, there is a temp files corruption problem with editing 2 files with same name.

I edit myftp/include/myfile.php I edit myftp/anotherpath/anotherfolder/myfile.php

Filezilla take my second file for my first file and see my first file as modified and ask me to update it on server ...

At the end result myftp/anotherpath/anotherfolder/myfiles.php = myftp/include/myfiles.php

This problem is not present in FileZilla 3.10.0.2 and previous ...

Myfile.php is open as temp file Myfile.php and /anotherfolder/Myfile.php as Myfile2.php

When I am connected FTP show error

Status: Connecting to 184.164.144.133:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server Status: Waiting to retry... Status: Connecting to 184.164.144.133:21... Status: Connection established, waiting for welcome message... Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- Response: 220-You are user number 3 of 50 allowed. Response: 220-Local time is now 02:15. Server port: 21. Response: 220-This is a private system - No anonymous login Response: 220-IPv6 connections are also welcome on this server. Response: 220 You will be disconnected after 15 minutes of inactivity. Command: AUTH TLS Response: 234 AUTH TLS OK. Status: Initializing TLS... Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server Status: Connecting to 184.164.144.133:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server Status: Waiting to retry... Status: Connecting to 184.164.144.133:21... Status: Connection established, waiting for welcome message... Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- Response: 220-You are user number 5 of 50 allowed. Response: 220-Local time is now 02:17. Server port: 21. Response: 220-This is a private system - No anonymous login Response: 220-IPv6 connections are also welcome on this server. Response: 220 You will be disconnected after 15 minutes of inactivity. Command: AUTH TLS Response: 234 AUTH TLS OK. Status: Initializing TLS... Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server

There seems to be a security issue in your filezilla application. We need to connect with a security/developer personnel to disclose this vuln. Please reply ASAP.

As received via mail:

It seems that the setup.exe is prone to unquoted path vulnerability.

more info on the vuln itself : ​https://cwe.mitre.org/data/definitions/428.html

While it send the command :

"C:\Program Files\FileZilla FTP Client\uninstall.exe _?=C:\Program Files\FileZilla FTP Client"

It fail to quote the path correctly and launch any program named Program.exe in c: with administrator rights ( or Filezilla.exe/Filezilla FTP.exe in Program Files) I've made piece of code to help me investigate on this (get the command and the parent process) and a video as proof of concept

​https://www.youtube.com/watch?v=r06VwwJ9J4M

This trick can be use by malware to gain admin privilege or persistance, on compromised windows system (for info i'm on Win7 SP1 x64 but it should work for all systems as its a common windows vulnerability)

I didn't investigate on the previous version but they are possibly vulnerable too.

A cool way to trigger the vulnerability is to wait for an update as it launch the same unquoted command (that's where it was first discovered and that's why it concern the client too not only the install.exe)

​https://www.microplus.fr/secu/

Cyril Vallicari /Ug_0 Security

Encountered on 3.20.1, tried nightly snapshot from 2016-08-23 and encountered it there as well.

I have a Debian jessie 8.5 system running openssh-server 6.7p1-5+deb8u3. I attempt to access it via ​sftp://IP as my user/pass, and it logs in successfully, says "Listing directory /home/FOO", and then reports timeout after 20 seconds, repeat forever.

Experimentation has revealed that removing the file named "download?dl=packages%2Fdebian%2Fnautilus-dropbox_0.7.1_amd64.deb" in my homedir causes FileZilla to behave as expected. (Determined by comparing the "raw directory output" from FileZilla with ls -f and seeing which file came next.

Other SSH and SFTP clients, like PuTTY, sftp under Cygwin, and WinSCP, on the same machine, function perfectly fine while filezilla is not behaving.

I do not have any saved config settings for this host.

I had a user on my network download the latest windows package from filezilla-project.org and Palo Alto Traps caught what looked to be malware delivered to his system at install. I submitted the exe to our malicious code analysis service and it was flagged as suspicious. I've attached that report for your review.

Please give me a call or email if I can be of assistance.

Hello, I tried to install the latest version of FileZilla from FileZilla_3.32.0_macosx-x86_setup_bundled but this time Avast threw a warning.

Could somebody advice is this is false or the repository been hacked?

I have been attempting since yesterday to connect to the FTP site using the same connection method I have used for years. My version of FileZilla Client is 3.35.2.

Response: 550 Directory not empty.

After last update i have this error when i try to delete directory witch is not empty. I verify this with my pro client on various type of connection and various type of servers. I try to delete folders with other client and succes.

En la más reciente versión de FileZilla Pro no se pueden borrar carpetas que tengan algún tipo de contenido. Marca error 550. Sin embargo con otros programas de cliente FTP si es posible hacerlo. Utilizo el software WinSCP y logro borrar carpetas con contenidos sin problema alguno. No puedo hacerlo solamente en FileZilla.

After downloading and uploading back the same file - it's content got messed up. I attached file examples after downloading/uploading.

But it's a little bit tricky: 1) Everything works fine on my previous laptop 2) The bug appears on a completely fresh installed OS with latest FileZilla version 3) The bug doesn't appear when I'm using a different FTP client (WinSCP) on the fresh install.

I upgraded today to 3.41 (64-bit windows) and it is unusably slow. I estimate it is at least 100 times slower than earlier versions. For example, I regularly need to replace a complete subdirectory tree on the server and it usually takes less than second or so. With 3.41 it was taking longer than 10 minutes and barely made an impact, I gave up.

I also see that I cannot just jump from one directory to another, since I now get warnings that a directory synchronisation is taking place.

I wasn't sure that it was Filezilla the problem (maybe a network issue or a million other things), so I downgraded to 3.40 and all was good again. I then tried to reinstall 3.41 and all was slow again. I have now gone back to 3.40 until this gets fixed.

I am a long time user and big fan of Filezilla.

Hi,

I just updated to the latest version 3.45.1 and now unable to access Google's Shared Drives. *Checked accessibility via web browser, works OK.

This is what I've tried a few times after restarting.

1. Connecting to Google Drive is per usual
2. Accessing "My Drive" (personal) and "Shared with Me" works normally.
3. When I click into Shared Drives, and I click on one of the Shared Drives subfolders, FileZilla Pro becomes unresponsive/frozen.
4. Upon freezing, I'm unable to click on anything except to close it.

<Laptop and FileZilla info>

FileZilla Pro

Version: 3.45.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2019-09-25 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5 SQLite: 3.29.0 GnuTLS: 3.6.9

Operating system:

Name: Windows 10 (build 17763), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: C:\Users\howie\AppData\Roaming\FileZilla\

<Message Log>

Status: Resolving address of www.googleapis.com Status: Connecting to [2404:6800:4001:80e::200a]:443... Status: Connection established, initializing TLS... Status: Verifying certificate... Status: TLS connection established, sending HTTP request Status: Retrieving root listing... Status: Directory listing of "/" successful Status: Retrieving directory listing of "/My Drive"... Status: Directory listing of "/My Drive" successful Status: Retrieving directory listing of "/Shared with me"... Status: Directory listing of "/Shared with me" successful Status: Retrieving directory listing of "/Shared drives"... Status: Directory listing of "/Shared drives" successful Status: Retrieving directory listing of "/Shared drives/howie Shuttle"...

When select any associating edit client(sublime text,ultra edit or any other client),the filezilla client always crash. here is crash detail:

Process: filezilla [3301] Path: /Applications/FileZilla.app/Contents/MacOS/filezilla Identifier: org.filezilla-project.filezilla Version: 3.49.1 (3.49.1) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: filezilla [3301] User ID: 503

Date/Time: 2020-07-20 13:06:06.203 +0800 OS Version: Mac OS X 10.15.4 (19E287) Report Version: 12 Anonymous UUID: AE5ABE47-6F3E-A103-F814-AD8AD782E4A0

Time Awake Since Boot: 8500 seconds

System Integrity Protection: disabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [3301]

VM Regions Near 0: --> TEXT 000000010bf3d000-000000010cada000 [ 11.6M] r-x/r-x SM=COW /Applications/FileZilla.app/Contents/MacOS/filezilla

Application Specific Information: Performing @selector(controlAction:) from sender wxNSButton 0x7fae13ebd610

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 org.filezilla-project.filezilla 0x000000010bfeac2b 0x10bf3d000 + 711723 1 org.filezilla-project.filezilla 0x000000010bffcefc 0x10bf3d000 + 786172 2 org.filezilla-project.filezilla 0x000000010bffcded 0x10bf3d000 + 785901 3 org.filezilla-project.filezilla 0x000000010c95c952 0x10bf3d000 + 10615122 4 org.filezilla-project.filezilla 0x000000010c95c6cb 0x10bf3d000 + 10614475 5 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 6 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 7 org.filezilla-project.filezilla 0x000000010c77b95e 0x10bf3d000 + 8644958 8 com.apple.AppKit 0x00007fff33a37437 -[NSApplication(NSResponder) sendAction:to:from:] + 299 9 com.apple.AppKit 0x00007fff33a372d2 -[NSControl sendAction:to:] + 86 10 com.apple.AppKit 0x00007fff33a37204 26-[NSCell _sendActionFrom:]_block_invoke + 136 11 com.apple.AppKit 0x00007fff33a37106 -[NSCell _sendActionFrom:] + 171 12 com.apple.AppKit 0x00007fff33a3704d -[NSButtonCell _sendActionFrom:] + 96 13 com.apple.AppKit 0x00007fff33a3332b NSControlTrackMouse + 1745 14 com.apple.AppKit 0x00007fff33a32c32 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 130 15 com.apple.AppKit 0x00007fff33a32af1 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 691 16 com.apple.AppKit 0x00007fff33a31e6d -[NSControl mouseDown:] + 748 17 org.filezilla-project.filezilla 0x000000010c7e34ee 0x10bf3d000 + 9069806 18 com.apple.AppKit 0x00007fff33a30280 -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 4914 19 com.apple.AppKit 0x00007fff3399aa81 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 2612 20 com.apple.AppKit 0x00007fff33999e29 -[NSWindow(NSEventRouting) sendEvent:] + 349 21 org.filezilla-project.filezilla 0x000000010c7d420b 0x10bf3d000 + 9007627 22 com.apple.AppKit 0x00007fff339981b4 -[NSApplication(NSEvent) sendEvent:] + 352 23 org.filezilla-project.filezilla 0x000000010c75e432 0x10bf3d000 + 8524850 24 com.apple.AppKit 0x00007fff33af5b0b -[NSApplication _doModalLoop:peek:] + 388 25 com.apple.AppKit 0x00007fff33c87fac 33-[NSApplication runModalSession:]_block_invoke_2 + 69 26 com.apple.AppKit 0x00007fff33c87f54 33-[NSApplication runModalSession:]_block_invoke + 78 27 com.apple.AppKit 0x00007fff33af4094 _NSTryRunModal + 100 28 com.apple.AppKit 0x00007fff33c87e4f -[NSApplication runModalSession:] + 128 29 org.filezilla-project.filezilla 0x000000010c7c9a20 0x10bf3d000 + 8964640 30 org.filezilla-project.filezilla 0x000000010c942533 0x10bf3d000 + 10507571 31 org.filezilla-project.filezilla 0x000000010c9425d6 0x10bf3d000 + 10507734 32 org.filezilla-project.filezilla 0x000000010c7ca08d 0x10bf3d000 + 8966285 33 org.filezilla-project.filezilla 0x000000010c94268d 0x10bf3d000 + 10507917 34 org.filezilla-project.filezilla 0x000000010c8d5305 0x10bf3d000 + 10060549 35 org.filezilla-project.filezilla 0x000000010c760bbf 0x10bf3d000 + 8534975 36 org.filezilla-project.filezilla 0x000000010bfc14ff 0x10bf3d000 + 541951 37 org.filezilla-project.filezilla 0x000000010bfe5051 0x10bf3d000 + 688209 38 org.filezilla-project.filezilla 0x000000010bfe22b3 0x10bf3d000 + 676531 39 org.filezilla-project.filezilla 0x000000010bfdfad6 0x10bf3d000 + 666326 40 org.filezilla-project.filezilla 0x000000010c2303a7 0x10bf3d000 + 3093415 41 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 42 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 43 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 44 org.filezilla-project.filezilla 0x000000010c891372 0x10bf3d000 + 9782130 45 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 46 org.filezilla-project.filezilla 0x000000010c84b746 0x10bf3d000 + 9496390 47 org.filezilla-project.filezilla 0x000000010c782fc9 0x10bf3d000 + 8675273 48 com.apple.AppKit 0x00007fff33a37437 -[NSApplication(NSResponder) sendAction:to:from:] + 299 49 com.apple.AppKit 0x00007fff33b47aee -[NSMenuItem _corePerformAction] + 312 50 com.apple.AppKit 0x00007fff33b4786a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 106 51 com.apple.AppKit 0x00007fff33b983e8 -[NSMenu performActionForItemAtIndex:] + 114 52 com.apple.AppKit 0x00007fff33b9836d -[NSMenu _internalPerformActionForItemAtIndex:] + 82 53 com.apple.AppKit 0x00007fff33b981b7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 101 54 com.apple.AppKit 0x00007fff33b288f8 NSSLMMenuEventHandler + 908 55 com.apple.HIToolbox 0x00007fff351828ff DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1254 56 com.apple.HIToolbox 0x00007fff35181d8d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 329 57 com.apple.HIToolbox 0x00007fff3519747e SendEventToEventTarget + 39 58 com.apple.HIToolbox 0x00007fff351f740b SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef) + 368 59 com.apple.HIToolbox 0x00007fff3521e065 SendMenuCommandWithContextAndModifiers + 45 60 com.apple.HIToolbox 0x00007fff3521e00d SendMenuItemSelectedEvent + 346 61 com.apple.HIToolbox 0x00007fff3521de59 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 96 62 com.apple.HIToolbox 0x00007fff353288c2 PopUpMenuSelectCore(MenuData*, Point, double, Point, unsigned short, unsigned int, unsigned int, Rect const*, unsigned short, unsigned int, Rect const*, Rect const*, CFDictionary const*, CFString const*, OpaqueMenuRef, unsigned short*) + 1615 63 com.apple.HIToolbox 0x00007fff35327db6 _HandlePopUpMenuSelection8(OpaqueMenuRef*, OpaqueEventRef*, unsigned int, Point, unsigned short, unsigned int, unsigned int, Rect const*, unsigned short, Rect const*, Rect const*, CFDictionary const*, CFString const*, OpaqueMenuRef, unsigned short*) + 410 64 com.apple.HIToolbox 0x00007fff351ff2b5 _HandlePopUpMenuSelectionWithDictionary + 329 65 com.apple.AppKit 0x00007fff33cea96d SLMPerformPopUpCarbonMenu + 1611 66 com.apple.AppKit 0x00007fff33b90f48 _NSSLMPopUpCarbonMenu3 + 782 67 com.apple.AppKit 0x00007fff33b90b94 -[NSCarbonMenuImpl popUpMenu:atLocation:width:forView:withSelectedItem:withFont:withFlags:withOptions:] + 439 68 com.apple.AppKit 0x00007fff33bca117 -[NSPopUpButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 604 69 org.filezilla-project.filezilla 0x000000010c7d07ad 0x10bf3d000 + 8992685 70 org.filezilla-project.filezilla 0x000000010c769e27 0x10bf3d000 + 8572455 71 org.filezilla-project.filezilla 0x000000010c8742e3 0x10bf3d000 + 9663203 72 org.filezilla-project.filezilla 0x000000010bfa91de wxWindowBase::PopupMenu(wxMenu*, wxPoint const&) + 46 73 org.filezilla-project.filezilla 0x000000010c22d1c5 0x10bf3d000 + 3080645 74 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 75 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 76 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 77 org.filezilla-project.filezilla 0x000000010c891372 0x10bf3d000 + 9782130 78 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 79 org.filezilla-project.filezilla 0x000000010c767175 0x10bf3d000 + 8561013 80 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 81 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 82 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 83 org.filezilla-project.filezilla 0x000000010c891372 0x10bf3d000 + 9782130 84 org.filezilla-project.filezilla 0x000000010c7b3636 0x10bf3d000 + 8873526 85 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 86 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 87 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 88 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 89 org.filezilla-project.filezilla 0x000000010c7e708d 0x10bf3d000 + 9085069 90 org.filezilla-project.filezilla 0x000000010c7e3497 0x10bf3d000 + 9069719 91 com.apple.AppKit 0x00007fff3399b9bd -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 6512 92 com.apple.AppKit 0x00007fff33999e29 -[NSWindow(NSEventRouting) sendEvent:] + 349 93 org.filezilla-project.filezilla 0x000000010c7d3dcb 0x10bf3d000 + 9006539 94 com.apple.AppKit 0x00007fff33998b1b -[NSApplication(NSEvent) sendEvent:] + 2759 95 org.filezilla-project.filezilla 0x000000010c75e432 0x10bf3d000 + 8524850 96 com.apple.AppKit 0x00007fff337e521f -[NSApplication run] + 707 97 org.filezilla-project.filezilla 0x000000010c7c9c0a 0x10bf3d000 + 8965130 98 org.filezilla-project.filezilla 0x000000010c94268d 0x10bf3d000 + 10507917 99 org.filezilla-project.filezilla 0x000000010c8d5305 0x10bf3d000 + 10060549 100 org.filezilla-project.filezilla 0x000000010c8ac514 0x10bf3d000 + 9893140 101 org.filezilla-project.filezilla 0x000000010c79306a 0x10bf3d000 + 8740970 102 org.filezilla-project.filezilla 0x000000010c8fc89a 0x10bf3d000 + 10221722 103 org.filezilla-project.filezilla 0x000000010c0123c3 0x10bf3d000 + 873411 104 libdyld.dylib 0x00007fff704becc9 start + 1

I uploaded a bunch of files by dragging them from a Nemo window into Filezilla's server-side tab.

I do this all the time, but this time a window with an assert error message showed up.

Here's the backtrace:

    ASSERT INFO:
    QueueView.cpp(1231): assert "(res & (0x0100 | (0x0002))) != (0x0100 | (0x0002))" failed in SendNextCommand().

    BACKTRACE:
    [1] wxEvtHandler::TryHereOnly(wxEvent&)
    [2] wxEvtHandler::ProcessEventLocally(wxEvent&)
    [3] wxEvtHandler::ProcessEvent(wxEvent&)
    [4] wxEvtHandler::ProcessPendingEvents()
    [5] wxAppConsoleBase::ProcessPendingEvents()
    [6] wxApp::DoIdle()
    [7] g_main_context_dispatch
    [8] g_main_loop_run
    [9] gtk_main
    [10] wxGUIEventLoop::DoRun()
    [11] wxEventLoopBase::Run()
    [12] wxAppConsoleBase::MainLoop()
    [13] wxEntry(int&, wchar_t**)
    [14] __libc_start_main

I tried the "Continue" button, but the popup would show up again and again, so I eventually chose "Stop", and then FileZilla crashed (unless closing it is what the Stop button does).

I have no idea how to reproduce this systematically. It only happened randomly this one time (and I'm sure it'll happen again in the future, but it certainly doesn't happen often)

Error Al descargar archivos de ftp Los asteriscos * lo he cambiado manualmente ya que es un proyecto privado

cd "/var/www/vhosts/*.com/httpdocs/0_*.1/update" Respuesta: New directory is: "/var/www/vhosts/*.com/httpdocs/0_*.1/update" Comando: get "update.php" "/Users/imac_fer/Desktop/vertary/0_*.1/update/update.php" Error: Could not allocate memory to open '/Users/imac_fer/Desktop/vertary/0_*.1/update/update.php' for writing. Error: local: unable to open /Users/imac_fer/Desktop/vertary/0_*.1/update/update.php Error: Error crítico de transferencia de archivo

FileZilla Client

Version: 3.52.0.3

Build information:

Compiled for: x86_64-apple-darwin20.2.0 Compiled on: x86_64-apple-darwin20.2.0 Build date: 2021-01-06 Compiled with: Apple clang version 12.0.0 (clang-1200.0.32.28) Compiler flags: -Werror=partial-availability -Wall -g

Linked against:

wxWidgets: 3.0.6 SQLite: 3.31.1 GnuTLS: 3.6.15

Operating system:

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

Hi,

We just updated our Filezilla Pro (3.52.0.4) and sent a compressed file in WinRAR format (.rar) to an S3 bucket on AWS. The upload is successful and the download is successful, but when trying to extract the file it gives an error. We repeated the process several times and it doesn't work, and the compressed file on the source computer is unzipping normally. The problem is when we send the file. Since we sent and downloaded it through the AWS web interface and the file unzipped normally at the destination.

Please check.

I look forward and thanks.

Cristiano.

The new 3.52.2 version is crashing when uploading to dropbox. I never had any problems with 3.51 and have uploaded over 2TB of Data with no problems. The new version randomly crashes at different times. I've also tried reinstalling. Is there any chance you can send me a link to download the older FileZilla Pro 3.51 again until there's a fix?

The download of FileZilla for Windows in the front page is infected with malware:

​https://download.filezilla-project.org/client/FileZilla_3.54.1_win64_sponsored-setup.exe

Windows Defender has removed the file on download.

Virustotal shows a number of detections, from adware to trojan: ​https://www.virustotal.com/gui/file/9c7d724fa2f7bed9f1967fae78eba83ad027c6b3431ac064fd56c91a2f179e42/detection

While connecting to SFTP we are facing an error in login. Error 'Could not get reply from fzputtygen'. Please help me in troubleshooting the error

hello team, i am a filezilla user, recently i update the software to FileZilla_3.56.2 , after doing this FTP not working.

Status: Connecting to 162.241.85.69:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Command: USER giveuc2t Response: 331 User giveuc2t OK. Password required Command: PASS Response: 530 Login authentication failed Error: Critical error: Could not connect to server

for every FTP account same happening, please help me to connect FTP.

One more thing left local path folders & file not showing.

installed the new release version 3.57.0, the local site failed to load any directory or files.

i try all versions portable cludnt version server version

i cannot list my owner pc Harddisk C or D or any one from stick i can connect the server and transfer files from server to my laptop but ohnly on Main Drive like D or D i cannot list any folder on my Lapto to see files or folder on my PC on Server side i can see folder and change them and can see files too und transfer them in both ways .

But no version and latest version 3.58.0 64bit dont whant open any folder on my laptop . win 7 Pro

DLL Hijacking vulnerability is discovered in latest version of FileZilla Client which is 3.63.1 which allows an attacker to gain access, execute arbitrary code via crafted DLL.

hi, FileZilla is awesome but there are many bugs on version 3.58. I can't officially update it and in Ubuntu software, there's no newer version :)

please update the project for Ubuntu users :)

File cannot be uploaded to Onedrive.

The reason for cancellation is "Could not start transfer".

My ondrive capacity is 500gb left, so it's not a capacity issue.

My current Filezilla version is 3.65.0, and I am a pro user.

Dear Support Team,

I wanted to bring to your attention that the FileZilla Application is currently being flagged as malware by Windows Defender. Additionally, upon checking the file and URL with VirusTotal, both are identified as suspicious or potentially harmful.

I appreciate your prompt attention to this matter and look forward to your guidance on resolving this issue.

Best regards,