Custom Query (4044 matches)

I just installed version 3.26.0 and when I opened of FileZilla my Site Manager entries had changed. Specifically any site where I had more than one site specific book mark only showed the first one.

FileZilla 3.26.1 does not build on Mageia due to an underlinking issue [0]:

libtool: link: g++ -I/usr/lib64/wx/include/ -I/usr/lib64/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -Wall -std=gnu++14 -pthread -Wl,--export-dynamic -pthread -Wl,--as-needed -Wl,--no-undefined -Wl,-z -Wl,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags -o filezilla filezilla-aboutdialog.o filezilla-asksavepassworddialog.o filezilla-asyncrequestqueue.o filezilla-aui_notebook_ex.o filezilla-auto_ascii_files.o filezilla-bookmarks_dialog.o filezilla-buildinfo.o filezilla-chmoddialog.o filezilla-clearprivatedata.o filezilla-cmdline.o filezilla-commandqueue.o filezilla-conditionaldialog.o filezilla-context_control.o filezilla-customheightlistctrl.o filezilla-defaultfileexistsdlg.o filezilla-dialogex.o filezilla-dndobjects.o filezilla-dragdropmanager.o filezilla-drop_target_ex.o filezilla-edithandler.o filezilla-encoding_converter.o filezilla-export.o filezilla-fileexistsdlg.o filezilla-filelistctrl.o filezilla-filelist_statusbar.o filezilla-FileZilla.o filezilla-filter.o filezilla-filter_conditions_dialog.o filezilla-filteredit.o filezilla-file_utils.o filezilla-fzputtygen_interface.o filezilla-graphics.o filezilla-import.o filezilla-inputdialog.o filezilla-ipcmutex.o filezilla-led.o filezilla-listctrlex.o filezilla-listingcomparison.o filezilla-local_recursive_operation.o filezilla-locale_initializer.o filezilla-LocalListView.o filezilla-LocalTreeView.o filezilla-loginmanager.o filezilla-Mainfrm.o filezilla-manual_transfer.o filezilla-menu_bar.o filezilla-msgbox.o filezilla-netconfwizard.o filezilla-Options.o filezilla-password_crypto.o filezilla-power_management.o filezilla-queue.o filezilla-queue_storage.o filezilla-QueueView.o filezilla-queueview_failed.o filezilla-queueview_successful.o filezilla-quickconnectbar.o filezilla-recentserverlist.o filezilla-recursive_operation.o filezilla-recursive_operation_status.o filezilla-remote_recursive_operation.o filezilla-RemoteListView.o filezilla-RemoteTreeView.o filezilla-search.o filezilla-serverdata.o settings/filezilla-optionspage.o settings/filezilla-optionspage_connection.o settings/filezilla-optionspage_connection_active.o settings/filezilla-optionspage_connection_ftp.o settings/filezilla-optionspage_connection_passive.o settings/filezilla-optionspage_connection_sftp.o settings/filezilla-optionspage_dateformatting.o settings/filezilla-optionspage_debug.o settings/filezilla-optionspage_edit.o settings/filezilla-optionspage_edit_associations.o settings/filezilla-optionspage_fileexists.o settings/filezilla-optionspage_filelists.o settings/filezilla-optionspage_filetype.o settings/filezilla-optionspage_ftpproxy.o settings/filezilla-optionspage_interface.o settings/filezilla-optionspage_language.o settings/filezilla-optionspage_logging.o settings/filezilla-optionspage_proxy.o settings/filezilla-optionspage_sizeformatting.o settings/filezilla-optionspage_themes.o settings/filezilla-optionspage_transfer.o settings/filezilla-optionspage_updatecheck.o settings/filezilla-settingsdialog.o filezilla-sftp_crypt_info_dlg.o filezilla-sitemanager.o filezilla-sitemanager_dialog.o filezilla-sizeformatting.o filezilla-speedlimits_dialog.o filezilla-splitter.o filezilla-state.o filezilla-statusbar.o filezilla-statuslinectrl.o filezilla-StatusView.o filezilla-systemimagelist.o filezilla-textctrlex.o filezilla-themeprovider.o filezilla-timeformatting.o filezilla-toolbar.o filezilla-treectrlex.o filezilla-updater.o filezilla-update_dialog.o filezilla-verifycertdialog.o filezilla-verifyhostkeydialog.o filezilla-view.o filezilla-viewheader.o filezilla-volume_enumerator.o filezilla-welcome_dialog.o filezilla-window_state_manager.o filezilla-wrapengine.o filezilla-wxfilesystem_blob_handler.o filezilla-xh_text_ex.o filezilla-xmlfunctions.o filezilla-xrc_helper.o filezilla-prefix.o  ../engine/libengine.a -lfilezilla -lpthread -lpugixml -lnettle -lhogweed -lgnutls ../dbus/libfzdbus.a -ldbus-1 -L/usr/lib64 -lwx_gtk2u_aui-3.0 -lwx_gtk2u_xrc-3.0 -lwx_gtk2u_adv-3.0 -lwx_gtk2u_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu-3.0 -lsqlite3 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgmodule-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -pthread
filezilla-asksavepassworddialog.o: In function `CAskSavePasswordDialog::OnOk(wxCommandEvent&)':
/home/akien/Mageia/Checkout/filezilla/BUILD/filezilla-3.26.1/src/interface/asksavepassworddialog.cpp:50: undefined reference to `fz::random_bytes(unsigned long)'
filezilla-password_crypto.o: In function `private_key::generate()':
/home/akien/Mageia/Checkout/filezilla/BUILD/filezilla-3.26.1/src/interface/password_crypto.cpp:40: undefined reference to `fz::random_bytes(unsigned long)'
/home/akien/Mageia/Checkout/filezilla/BUILD/filezilla-3.26.1/src/interface/password_crypto.cpp:45: undefined reference to `fz::random_bytes(unsigned long)'
settings/filezilla-optionspage_interface.o: In function `COptionsPageInterface::SavePasswordOption()':
/home/akien/Mageia/Checkout/filezilla/BUILD/filezilla-3.26.1/src/interface/settings/optionspage_interface.cpp:113: undefined reference to `fz::random_bytes(unsigned long)'
collect2: error: ld returned 1 exit status
Makefile:928: recipe for target 'filezilla' failed

I haven't tested but I suppose the issue only happens when using the -Wl,--no-undefined linker parameter, which is enforced by several distros in their packaging to prevent underlinking issues [0].

[0] ​https://wiki.mageia.org/en/Underlinking_issues_in_packaging

Been fighting writing this up.. But now with the latest 3.26.2 package still having filezilla crash. My Debian 8 was just updated to the latest code as of 6/12/17.. So if i attempt to see if there is any new updates.. filezilla will crash. I have 10 objects under "site manager" if i attempt to switch from one of these to another one it will crash. Now I have had to update my passwords on each of these objects. So not sure if that bug is coming into play.. There have also been time were just attempting to bring up filezilla that it would crash.. This i noticed several segment faults being seen. I gathered some data.. See if it is usable.. thanks Brent

Just tried to build FileZilla 3.26.2 with libfilezilla 0.9.2 using GCC 5.3.0 and GNU Binutils 2.28 - got the following linkage error:

  CXXLD    filezilla
filezilla-asksavepassworddialog.o: In function `CAskSavePasswordDialog::OnOk(wxCommandEvent&)':
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/asksavepassworddialog.cpp:50: undefined reference to `fz::random_bytes(unsigned int)'
filezilla-password_crypto.o: In function `private_key::generate()':
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/password_crypto.cpp:40: undefined reference to `fz::random_bytes(unsigned int)'
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/password_crypto.cpp:45: undefined reference to `fz::random_bytes(unsigned int)'
settings/filezilla-optionspage_interface.o: In function `COptionsPageInterface::SavePasswordOption()':
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/settings/optionspage_interface.cpp:113: undefined reference to `fz::random_bytes(unsigned int)'
collect2: error: ld returned 1 exit status

Command

[elijah@santiago .libs]$ strings libfilezilla.so.0.0.0 | grep random_bytes

shows me the following output:

_ZN2fz12random_bytesEj
random_bytes
_ZN2fz12random_bytesEj

Summary: Immediately after clicking on connect while a non-ftp URL is in the site-manager's host field crashes FileZilla on OSX. Example URLS: ​smb://192.168.100.22 ogg://192.168.100.22 (does not make sense, but was used for testing)

Description: See Summary.

Assign to:

Type: Bug Report Priority: normal

Component: client

Keywords: Site Manager, FileZilla crash

Cc:

Operating system type: OSX

Operating system version: 10.12.5 (16F73)

Hello,

I see this issue in FileZilla Client (version 3.26.2):

A folder/directory's name with an extension, like ".flac", is detected has a "FLAC file" in the "Type" column.

This issue is present in Local and Remote View.

Hi I am having trouble using Filezilla i have used it for about a year now and this is the first time has done this. I have screen shots of the error. It is closing down unexpectedly when i copy and paste over my log in details from DJ complications.

Are you able to help? I am unable to use it at all?

Thanks Shannon

When using Filezilla Pro Client and downloading from Amazon S3 storage, handling of folders seems wrong.

If you select a folder on the remote size and then try to download it, behavior is inconsistent:

1. If the folder already exists on the local side, the files are transferred into that folder as expected.

2. If the folder does not exist on the local side, the download fails for each file because the folder path does not exist.

In case 2, I believe expected behavior is for FileZilla to create the missing folder and proceed. This would be consistent with its behavior for FTP sources.

Hi,

I have installed FileZilla 3.26.2 from 3.26.2 installer for windows (64 bits) and the filezilla installed is 3.26.1 version.

Thanks to solve it

++

Hello, 32-bit shell extension is not working Windows 32-bit versions since version 3.27.0. It is not possible to register fzshellext.dll using regsvr32.exe

I am trying to compile FileZilla with Storj support from sources.

The ../configure --enable-storj=yes command is successful, but then make fails with the following error:

In file included from ../../../src/engine/storj/connect.cpp:4:0: ../../../src/engine/storj/event.h:4:31: fatal error: ../storj/events.hpp: No such file or directory #include "../storj/events.hpp"

There is no "events.hpp" file in the FileZilla_3.27.0.1_src.tar.bz2 source package. However, I found it in the SVN repo. After copying it manually, the build is successful.

Please, make sure that the "events.hpp" file is included in the source package.

My web server was recently updated from RHEL 7.3 to 7.4. After this regular server OS update I am unable to log in with Filezilla 3.27.0.1.

I use passwordless login to connect over SSH and this was working fine (in FileZilla) until the server OS update last night. None of the server SSH config files were modified as part of the OS update (based on file creation/modified dates).

I am able to connect to the server via the command line sftp client. I'm also able to connect with at least two other SFTP guis (Caja and gFTP).

OneDrive has recently updated and since then FileZilla no longer shows file information ie modified date/size etc if the file is in the local cache. This then prevents drag and drop from working.

If the file is local only then information is shown & everything works as expected.

Dear Sir / Madam

I am getting the following error, when trying to install Filezilla v3.27.1 (64 bit) on my Windows 10 PC.

Can't write: C:\Program Files\Filezilla FTP Client\fzsftp.exe

This error occured, when I tried updating the Filezilla installation using my limited access account, by entering the admin credentials.

To double confirm, I did login to the admin user account and tried installing Filezilla Client once again, but, the same issue occured again.

Currently, I am searching for older version of filezilla client, to continue working, as before.

please help fix this issue with Filezilla CLient v3.27.1

thank you

With Best Regards Raghu veer

Filezilla: 3.27.1 openSUSE Tumbleweed 20170830, Kernel 4.11.8 Settings: Using Masterpassword

I am not sure, if the version-upgrade or using a master-password is the last relevant change I made, since filezilla crashes.

Steps to reproduce (everytime):

• Open Server-Manager
• Add new server
• change the auth-type to "Normal"
• Try to edit/paste the password field

=> filezilla crashes

Hi I asked for a new feature which I understand you had included in the new release I downloaded today. I.e. when updating a large file / files I wanted fZ to close itself afterwards automatically. However after setting this option FZ kept closing itself. The new feature would allow FZ to be set to CLOSE ONCE only.

I tried it out now and could not activate any of the options in the drop down menue. I.e. only NONE works.

Small bug I am sure.

Hopefully this will be fixed asap as this new feature is GREAT and will be used by me and others a lot.

Enter in host name, user, password. The credentials are still being sent to Amazon and not the host name I entered.

Filezilla Pro version 3.28.0

Windows 7 Pro.

On startup:

ASSERT INFO:
../src/gtk/toplevel.cpp(988): assert "m_widget" failed in Show(): invalid frame

BACKTRACE:
[1] wxTopLevelWindowGTK::Show(bool)
[2] wxTopLevelWindowBase::Destroy()
[3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[5] wxEvtHandler::TryHereOnly(wxEvent&)
[6] wxEvtHandler::ProcessEventLocally(wxEvent&)
[7] wxEvtHandler::ProcessEvent(wxEvent&)
[8] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[9] wxTimerImpl::SendEvent()
[10] g_main_context_dispatch
[11] g_main_loop_run
[12] gtk_main
[13] wxGUIEventLoop::DoRun()
[14] wxEventLoopBase::Run()
[15] wxAppConsoleBase::MainLoop()
[16] wxEntry(int&, wchar_t**)
[17] __libc_start_main

FileZilla 3.28.0 (Debian Sid)

For example, on El Capitan, building FileZilla 3.28.0 via MacPorts failed:

/opt/local/bin/clang-mp-4.0 -DHAVE_CONFIG_H -I. -I../../src/include  -I./../include   -I/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/lib/wx/include/osx_cocoa-unicode-3.0 -I/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXMAC__ -D__WXOSX__ -D__WXOSX_COCOA__   -I/opt/local/include -fpch-preprocess  -pipe -Os -arch x86_64 -MT filezilla-power_management_osx.o -MD -MP -MF .deps/filezilla-power_management_osx.Tpo -c -o filezilla-power_management_osx.o `test -f 'power_management_osx.m' || echo './'`power_management_osx.m
file_utils_osx.m:11:22: error: property 'path' cannot be found in forward class object 'NSURL'
                        path = strdup(url.path.UTF8String);
                                      ~~~ ^
/System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:251:8: note: forward declaration of class here
@class NSURL;
       ^
1 error generated.

The full build log can be found at ​https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/40551/steps/install-port/logs/stdio

When you attach or detach external monitors, FileZilla client intermittently crashes - report attached.

When I have a long queue to upload and then one file with same name happens to exist already, a dialog will appear asking about action for existing file. Like in file explorers usually, these verifications are asked after the whole queue has processed. With FileZilla they are asked according to queue order. Therefore an unpleasant surprise waits if you have left your computer for hours expecting that all the uploaded files are uploaded. I know that I can choose default action but it depends on the situation.

• Connect to an ftp or sftp server by using FileZilla 3.30.0
• Enter a remote directory and rename a file in that directory
• End renaming operation by clicking outside of the file-name textbox
• As a result, you won't be able to click on any file from that point forward or click on "..." to switch to another directory.
• Refreshing file listview does not help. The only way to unfreeze file listview is to switch to another directory by using the remote site combobox other than closing the application and opening it back on.

It doesn't occur if you use Enter Key to finish renaming a file.

It doesn't occur if you click on rename but don't make any changes to file's name, and then click outside of the file-name textbox.

If you wish to see it, I've recorded my screen while following the steps mentioned above to reproduce the bug, and put it on YouTube. Here's the unlisted link of the video:

​https://youtu.be/6nGvlrpZDvs

C'è una "i" in più.. Elaborato xxx file iin xxx cartelle

The checkbox Conditions are case sensitive is enabled, when the Edit filters configuration window is opened and no filter is selected, although the checkbox is filter specific like the checkboxes below the title Filter applies to: right under it.

This can create some confusion, as it can be assumed that the checkbox is universal for all filters, especially because the two checkboxes below are enabled when a filter is selected, highlighting the otherness of the first-mentioned checkbox.

Bravo for closing the previous ticket without bothering to find the real problem here! Your last comment is patently false, 100%!!!

Moving the location of the private key file for SFTP login doesn't work. I have several SFTP sites set up whereby the folder for their private keys changed from C:\ to W:\. All of the sites work perfectly to log in and browse the remote folders. The problem occurs when I drag and drop a local file to the remote server. In this case, it tries to reconnect to the remote server using the OLD keyfile location. You can see the error message "Skipping non-existing key file "C:\0_Work\".... in the attached copy of the message log.

Hello, I've googled filezila not saving port numbers and note that it does not display known default ports. I'm using 3.27.0.1 under win7. I'm trying to connect via sftp using port 22. I'm able to connect when I manually type in port 22. but if I connect with the default setting without the port 22, it does not connect at all. I believe this to be an issue with the software.

Ticket #10832 showed this as closed in v3.17.0.1. I just updated a machine with v3.33.0.0 and our AlienValue issued similar message as in Ticket #10832 (below).

I have verified that the UninstallString is unquoted in my registry settings for both Client and Server. ray

-- Alert --

Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\FileZilla Client|C:\Program Files\FileZilla FTP Client\uninstall.exe Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\FileZilla Server|C:\Program Files (x86)\FileZilla Server\uninstall.exe

Impact:

A local attacker could gain elevated privileges by inserting an executable file in the path of the affected service or uninstall entry.

Solution:

Either put the listed vulnerable paths in quotation by manually using the onboard Registry editor or contact your vendor to get an update for the specified software that fixes this vulnerability.

When I download a folder containing thousands of files and sub-folders I receive a lot of "Target file already exists" pop-ups. I am downloading into an empty folder, so apparently FZ is trying to download the same file twice. I can see from the timestamp of the "already existing" file that it has just been downloaded, but now the file apparently is being downloaded again. I have also observed, that the file that is to be overwritten is smaller than the source file, i.e. the file wasn't transferred fully, but I did not receive any error messages. What is going on? I am really worried if I can trust that everything has been downloaded correctly.

Dragging a new file into the upload queue sometimes causes the following errror:

ASSERT INFO:
./src/generic/listctrl.cpp(3422): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem

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

FileZilla Client
----------------

Version:          3.34.0

Build information:
  Compiled for:   x86_64-pc-linux-gnu
  Compiled on:    x86_64-pc-linux-gnu
  Build date:     2018-06-18
  Compiled with:  gcc (GCC) 8.1.1 20180531
  Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wall -g

Linked against:
  wxWidgets:      3.0.4
  SQLite:         3.24.0
  GnuTLS:         3.5.18

Operating system:
  Name:           Linux 4.17.3-1-ARCH x86_64
  Version:        4.17
  CPU features:   sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx
  Settings dir:   /home/user/.config/filezilla/

Hello, In previous version 3.34.0 it was possible to edit/delete:download from the search module. With the version downloaded this morning 3.35.0 it is not the case anymore. Is it a bug or normal behaviour due to a chnage of Policy ? See attachment. Rgds.

Running the following command: "C:\Program Files\FileZilla FTP Client\filezilla.exe" ​sftp://[creds]@[site] --local="X:\local path"

In 3.34.0 this opens the remote site and the local directory just fine.

In 3.35.1 this opens the remote site, but defaults the local directory to last used local directory (if I was in "C:\Users\[username]\Desktop\ for example, it would use that) and not the local directory specified on the command line.

The "Remember Passwords" dialog box, which asks you if you want to save passwords with a master password or not at all, has the word "reconnnect" which should be "reconnect." See below:

The app keep telling me there is a new version, when downloading and install my Imac (10.11.6) chrash every time. I want to disable new version or have a fixed version.

Attach chrash report

I have not used FileZilla for a few months. I need to update some of my website files, and when I opened FileZilla to transfer them, there was a new update option. I updated to the newest version, 3.35.1.

I always move 1 file first to test and make sure everything is okay. I moved 1 file over to update. Filezilla said that it updated successfully and the last modified date is today. Then I went to the website to be sure the changes were reflected, and there were NOT!

I checked the source code on the website and it shows that it is still the old file. I am not sure if this is a server or client problem.

All I know is that the new file, with today's date shows up in the public_html area in FileZilla on my computer. And the udpates do not appear on my website and the source code on the website reflects the old file.

Also, when I opened FileZilla, I had to connect to my site. It did not connect automatically. I thought that it used to connect automatically when opening FileZilla. I may be remembering incorrectly here.

Thank you

Nikki Geannelis gnikki@…

I have not used FileZilla for a few months. I need to update some of my website files, and when I opened FileZilla to transfer them, there was a new update option. I updated to the newest version, 3.35.1.

I always move 1 file first to test and make sure everything is okay. I moved 1 file over to update. Filezilla said that it updated successfully and the last modified date is today. Then I went to the website to be sure the changes were reflected, and there were NOT!

I checked the source code on the website and it shows that it is still the old file. I am not sure if this is a server or client problem.

All I know is that the new file, with today's date shows up in the public_html area in FileZilla on my computer. And the udpates do not appear on my website and the source code on the website reflects the old file.

Also, when I opened FileZilla, I had to connect to my site. It did not connect automatically. I thought that it used to connect automatically when opening FileZilla. I may be remembering incorrectly here.

Thank you

Nikki Geannelis gnikki@…

I use the rename feature quite often within FileZilla and just recently it seems to not work properly. I change the name and it reverts back to the original name. After I select refresh the new name appears. So it seems to be updating the name but not showing on the screen. Please let me know if there is a fix. This just started with the latest update I downloaded.

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.

As of fileZilla version 3.35.2 the -s and --site-manager command line parameter switches do nothing when specified after the program path and name (out side of the ending double quote) in the properties box of a windows 10 desktop icon. I tried using -site-manager as well, but that gave me an unknown command message, but with either -s or --site-manager, no error message is displayed.

I expect that the -s and --site-manager switches should display the site manager dialog after fileZilla starts.

Here is the message I get when trying to download the new version.

Started update check on 2018-08-22 09:41:45 Own build type: official Downloading update.filezilla-project.org/update.php?platform=x86_64-w64-mingw32&version=3.32.0&product=3&osversion=10.0&osarch=64&updated=1&cpuid=sse,sse2,sse3,ssse3,sse4.1,sse4.2,avx,avx2,aes,pclmulqdq,rdrnd,bmi2,bmi2,adx&initial=0 Resolving address of update.filezilla-project.org Connecting to 136.243.154.122:443... Connection established, initializing TLS... Verifying certificate... TLS connection established, sending HTTP request File transfer successful, transferred 1,475 bytes in 1 second Parsing 1475 bytes of version information. Found new release 3.35.2 Downloading /FileZilla_Pro_3.35.2_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

I routinely use FileZilla client with two FTP servers. Immediately after updating the client to version 3.36.0 it started routinely crashing while "Retrieving directory listing..." from one of these servers. With the other server, I see no problem.

Hi,

Versions :

I'm using FTP 3.37.0 (compilation date 2018-09-17) under Windows 10 Enterprise (Version 1703, 15063.1324), all in french.

Settings:

I've a site registered :

• FTP Explicit with TLS if possible;
• Host name setup, no port setup (21 used)
• Normal authentication, login with a '|' and a regular password
• Second tab is left empty/default;
• Third tab is set to passive transfer mode, nothing else modified;
• 4th/last tab left as default.

It's not a public ftp so i can give it by mail but not in public.

Usage: The certificate is expired, and is well raised as expired with a pop-up, with expiratino date in red (level 0). But when i use the drop-down list to see intermediate certificate (n°1) and root certificate (n°2), the expiration date is colored red, even if their expiration date is in the future.

Abnormal behaviour: It seems that the red color of the 'expiration date' zone is kept red for other level than level 0, even if they are not... Shouldn't it be only the expired one that must be in red, and not the other ones ? If in red, we can think that it's expired, even if it's not ;-(

At your disposal.

Regards

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.

When uploading multiple folders from a Windows 7 Pro PC to a a Linux FTP Server some files are placed in the wrong folder and some files are not uploaded at all...

The attached log details a full upload of 577 files...

You can see one example of an incorrect placing in the log line: 2018-09-24 12:59:37 7140 5 Command: local:T:\!!!\sample\dir01\d1d01\d1d1d1\d1d1d1a\f038.txt => remote:/home/example/sample/dir07/d07d11/d7dbd2/f038.txt

3.37.0 & 3.37.1 only : random files not transfered without failure notice, files created with a size of 0 without failure notice, increase of failed transfers

With Filezilla client 3.37.0 and 3.37.1, when I upload large amount of files in several subfolders through an SFTP connection (to an openssh sftp server on debian jessie), I've got several problems :

• Some files go missing without any notice in the failed transfers panel (they appear in the "successful transfers" panel but are not on the server)
• Some files end up with a size of 0 on the server without any notice in the failed transfers panel (appear in the "successful transfers" panel but size 0 on the server)
• I get some "target file already exists" for some new file to create
• I noticed also an increase of failed transfers that I have to reset and requeue (though it didn't occur in the transfer which log is attached)

I could reproduce this problem several times when I upload a large amount of files with subfolder structure, but missing files and 0 size files are never the same and their number varies. It's generally about 4 or 5 for 2000 files to transfer.

I switched back to 3.36.0 and all those problem are not occuring anymore, and they never occured within the last 10/15 years I've been using Filezilla.

During the transfer related to the attached log file, I had 8 files in failed transfer. I reset and requeued and they uploaded correctly then. Those files are not the one that are missing after transfer is completed.

Missing files without error/notice /test/1346/slide/slide_555.jpg /test/1873/thumb/img_0100.jpg /test/1873/xlarge/img_0094.jpg /test/2033/thumb/img_0069.jpg /test/2033/thumb/img_0071.jpg

Size 0 files without notice /test/539/thumb/img_0042.jpg /test/2033/thumb/img_0051.jpg

Confirmed for overwriting after filezilla asked for overwriting an 'existing file', however folder was freshly created : /test/1346/thumb/img_0172.jpg /test/2033/xlarge/img_0044.jpg /test/2039/thumb/img_0035.jpg /test/2040/thumb/img_0030.jpg /test/539/thumb/img_0047.jpg /test/539/xlarge/img_0046.jpg /test/539/xlarge/img_0043.jpg /test/539/xlarge/img_0044.jpg

By the way, great job you are doing with filezilla ! Thanks for all !

Since I've upgraded macOS to mojave I can not move multiple items (single files or folders) from local drive to FTP server. Once I select more than 1 item FileZilla hangs or shuts down. I can transfer (by dragging) files only one by one. It takes forever. I have FileZilla client 3.37.1

Hi,

On the site panel, I have a "sent" directory into I drag and drop files that have been transferred.

When I try with V 3.37.3, the files are not moved.

Previously I was able to select some files or directories from the Remote Site window and drag/drop them into the Queued Files. That doesn't work anymore (nothing happens). To achieve that functionality now, I need to right-click the files and choose "Add Files to Queue".

Description:

As GnuTLS >= 3.6 drops OpenPGP certificates support, when Filezilla 3.37.4 is compiled with GnuTLS >= 3.6, connection with "FTP over TLS" will fail with "GnuTLS error -50 in gnutls_priority_set_direct: The request is invalid".

Connection error detail :

Status:	Resolving address of aaa.com
Status:	Connecting to 127.0.0.1:21...
Status:	Connection established, waiting for welcome message...
Status:	Initializing TLS...
Error:	GnuTLS error -50 in gnutls_priority_set_direct: The request is invalid.
Error:	Failed to initialize TLS.
Error:	Could not connect to server

Root cause:

After searching the code, it occured in file "/engine/tlssocket_impl.cpp"

char const ciphers[] = "SECURE256:+SECURE128:-ARCFOUR-128:-3DES-CBC:-MD5:+SIGN-ALL:-SIGN-RSA-MD5:+CTYPE-X509:-CTYPE-OPENPGP:-VERS-SSL3.0";

remove "-CTYPE-OPENPGP" will solve the problem.

char const ciphers[] = "SECURE256:+SECURE128:-ARCFOUR-128:-3DES-CBC:-MD5:+SIGN-ALL:-SIGN-RSA-MD5:+CTYPE-X509:-VERS-SSL3.0";

Test method:

Assue GnuTLS >= 3.6 is compiled in /opt/filezilla3, use gnutls-cli to test priority string:

[develop@test.com ~]$ PATH=/opt/filezilla3/bin:$PATH LD_LIBRARY_PATH=/opt/filezilla3/lib64:/opt/filezilla3/lib:$LD_LIBRARY_PATH /opt/filezilla3/bin/gnutls-cli  -l --priority="SECURE256:+SECURE128:-ARCFOUR-128:-3DES-CBC:-MD5:+SIGN-ALL:-SIGN-RSA-MD5:+CTYPE-X509:-CTYPE-OPENPGP:-VERS-SSL3.0"

The result contains error:

Cipher suites for SECURE256:+SECURE128:-ARCFOUR-128:-3DES-CBC:-MD5:+SIGN-ALL:-SIGN-RSA-MD5:+CTYPE-X509:-CTYPE-OPENPGP:-VERS-SSL3.0
Syntax error at: -CTYPE-OPENPGP:-VERS-SSL3.0

remove "-CTYPE-OPENPGP":

[develop@test.com ~]$ PATH=/opt/filezilla3/bin:$PATH LD_LIBRARY_PATH=/opt/filezilla3/lib64:/opt/filezilla3/lib:$LD_LIBRARY_PATH /opt/filezilla3/bin/gnutls-cli  -l --priority="SECURE256:+SECURE128:-ARCFOUR-128:-3DES-CBC:-MD5:+SIGN-ALL:-SIGN-RSA-MD5:+CTYPE-X509:-VERS-SSL3.0"

OK:

Cipher suites for SECURE256:+SECURE128:-ARCFOUR-128:-3DES-CBC:-MD5:+SIGN-ALL:-SIGN-RSA-MD5:+CTYPE-X509:-VERS-SSL3.0
TLS_AES_256_GCM_SHA384                            	0x13, 0x02	TLS1.3
TLS_CHACHA20_POLY1305_SHA256                      	0x13, 0x03	TLS1.3
TLS_AES_128_GCM_SHA256                            	0x13, 0x01	TLS1.3
TLS_AES_128_CCM_SHA256                            	0x13, 0x04	TLS1.3
TLS_ECDHE_ECDSA_AES_256_GCM_SHA384                	0xc0, 0x2c	TLS1.2
TLS_ECDHE_ECDSA_CHACHA20_POLY1305                 	0xcc, 0xa9	TLS1.2
TLS_ECDHE_ECDSA_AES_256_CBC_SHA1                  	0xc0, 0x0a	TLS1.0
TLS_ECDHE_ECDSA_AES_256_CCM                       	0xc0, 0xad	TLS1.2
TLS_ECDHE_ECDSA_AES_128_GCM_SHA256                	0xc0, 0x2b	TLS1.2
TLS_ECDHE_ECDSA_AES_128_CBC_SHA1                  	0xc0, 0x09	TLS1.0
TLS_ECDHE_ECDSA_AES_128_CCM                       	0xc0, 0xac	TLS1.2
TLS_ECDHE_RSA_AES_256_GCM_SHA384                  	0xc0, 0x30	TLS1.2
TLS_ECDHE_RSA_CHACHA20_POLY1305                   	0xcc, 0xa8	TLS1.2
TLS_ECDHE_RSA_AES_256_CBC_SHA1                    	0xc0, 0x14	TLS1.0
TLS_ECDHE_RSA_AES_128_GCM_SHA256                  	0xc0, 0x2f	TLS1.2
TLS_ECDHE_RSA_AES_128_CBC_SHA1                    	0xc0, 0x13	TLS1.0
TLS_RSA_AES_256_GCM_SHA384                        	0x00, 0x9d	TLS1.2
TLS_RSA_AES_256_CBC_SHA1                          	0x00, 0x35	TLS1.0
TLS_RSA_AES_256_CCM                               	0xc0, 0x9d	TLS1.2
TLS_RSA_AES_128_GCM_SHA256                        	0x00, 0x9c	TLS1.2
TLS_RSA_AES_128_CBC_SHA1                          	0x00, 0x2f	TLS1.0
TLS_RSA_AES_128_CCM                               	0xc0, 0x9c	TLS1.2
TLS_DHE_RSA_AES_256_GCM_SHA384                    	0x00, 0x9f	TLS1.2
TLS_DHE_RSA_CHACHA20_POLY1305                     	0xcc, 0xaa	TLS1.2
TLS_DHE_RSA_AES_256_CBC_SHA1                      	0x00, 0x39	TLS1.0
TLS_DHE_RSA_AES_256_CCM                           	0xc0, 0x9f	TLS1.2
TLS_DHE_RSA_AES_128_GCM_SHA256                    	0x00, 0x9e	TLS1.2
TLS_DHE_RSA_AES_128_CBC_SHA1                      	0x00, 0x33	TLS1.0
TLS_DHE_RSA_AES_128_CCM                           	0xc0, 0x9e	TLS1.2

Protocols: VERS-TLS1.3, VERS-TLS1.2, VERS-TLS1.1, VERS-TLS1.0, VERS-DTLS1.2, VERS-DTLS1.0
Ciphers: AES-256-GCM, CHACHA20-POLY1305, AES-256-CBC, AES-256-CCM, AES-128-GCM, AES-128-CBC, AES-128-CCM
MACs: AEAD, SHA1
Key Exchange Algorithms: ECDHE-ECDSA, ECDHE-RSA, RSA, DHE-RSA
Groups: GROUP-SECP384R1, GROUP-SECP521R1, GROUP-FFDHE8192, GROUP-SECP256R1, GROUP-X25519, GROUP-FFDHE2048, GROUP-FFDHE3072, GROUP-FFDHE4096, GROUP-FFDHE6144
PK-signatures: SIGN-RSA-SHA384, SIGN-RSA-PSS-SHA384, SIGN-RSA-PSS-RSAE-SHA384, SIGN-ECDSA-SHA384, SIGN-ECDSA-SECP384R1-SHA384, SIGN-RSA-SHA512, SIGN-RSA-PSS-SHA512, SIGN-RSA-PSS-RSAE-SHA512, SIGN-ECDSA-SHA512, SIGN-ECDSA-SECP521R1-SHA512, SIGN-RSA-SHA256, SIGN-RSA-PSS-SHA256, SIGN-RSA-PSS-RSAE-SHA256, SIGN-ECDSA-SHA256, SIGN-ECDSA-SECP256R1-SHA256, SIGN-EdDSA-Ed25519, SIGN-RSA-SHA1, SIGN-ECDSA-SHA1

Link:

​https://www.gnutls.org/manual/html_node/OpenPGP-certificates.html

the first file you create after opening FileZilla has the correct timestamp -- any additional files you may create will have the same timestamp as the first file you created. this issue does not apply when directories are created. i first noticed this issue today when a new file i created showed as being several hours old -- at first i thought maybe the server time zone was wrong, or that the FileZilla time zone offset was wrong, but i eventually determined the timestamp was based upon the first created file.

presumably this is due to FileZilla creating a single file and then reusing it, but it seems like a simple way to improve this would be just to "touch" the file to update it's timestamp before uploading it.

I just run into a problem when downloading (via sftp) multiple files simultaneously. When starting to precess the queue, the filezilla client crash after a few seconds. When downloading a singe file, there is no problem. It's reproducible, I've tried this three times (rebooted the system between, etc.).

After downgrade to 3.37.4 (win64) all is fine again.

I purchased Filezilla Pro so I could test out connectivity to our Openstack Swift storage ( we host three clusters around the world for our end users). I immediately run into an issue. We use Openstack Swift with the keystone identity service, with v2.0 being our standard identity protocol.

When I entered my project (aka tenent) and username and then hit connect, I got the following output:

00:47:34 Status: Resolving address of lax-staging.identity.example.com 00:47:34 Status: Connecting to 173.0.160.18:443... 00:47:34 Status: Connection established, initializing TLS... 00:47:34 Status: Verifying certificate... 00:47:34 Status: TLS connection established, sending HTTP request 00:47:35 Status: Resolving address of lax-staging.identity.example.com 00:47:35 Status: Connecting to x.x.x.x:443... 00:47:35 Status: Connection established, initializing TLS... 00:47:35 Status: Verifying certificate... 00:47:35 Status: TLS connection established, sending HTTP request 00:47:35 Command: POST /v2.0/tokens HTTP/1.1 00:47:35 Command: Connection: close 00:47:35 Command: Content-Length: 110 00:47:35 Command: Content-Type: application/json 00:47:35 Command: Host: lax-staging.identity.example.com:443 00:47:35 Command: User-Agent: FileZilla/3.38.1 00:47:35 Response: HTTP/1.1 200 OK 00:47:35 Response: Server: nginx/1.10.3 (Ubuntu) 00:47:35 Response: Date: Tue, 20 Nov 2018 08:47:35 GMT 00:47:35 Response: Content-Type: application/json 00:47:35 Response: Content-Length: 1508 00:47:35 Response: Connection: close 00:47:35 Response: Vary: X-Auth-Token 00:47:35 Response: X-Distribution: Ubuntu 00:47:35 Response: x-openstack-request-id: req-f760215c-4537-4ea8-8b17-05aca427fc 00:47:35 Error: Identity service did not return an auth token

If I typo the API KEY ( aka password) , I get 401. With all correct details, I get 200 OK as above, but it claims not to have a token, but it is returned. I've used Wireshark with the SSL decryption to confirm this.

The following JSON response was sent to Filezilla (I have changed the values but none of the keys ):

{"access": {"token": {"issued_at": "2018-11-20T08:28:45.000000Z", "expires": "2018-11-20T09:28:45.000000Z", "id": “blahbljbkgjbaekjrbgklaebgkjebgkjerbgejrkbgjkebgejkbg", "tenant": {"description": null, "enabled": true, "id": "6a4d4ca0536240a1b982391c88f0ec68", "name": “example"}, "audit_ids": [“Yrad3a_yx1e3l34"]}, "serviceCatalog": [{"endpoints": [{"adminURL": "​https://lax-proxy-staging.example.com", "region": "LAX", "internalURL": "​https://lax-proxy-staging.example.com/v1/AUTH_6a4d4ca0536240a1b982391c88f0ec68", "id": "ccb6cd9aba0f452db42b3d4f4a2c049e", "publicURL": "​https://lax-proxy-staging.example.com/v1/AUTH_b4e0f1ca0536240a1b982398"}], "endpoints_links": [], "type": "object-store", "name": "swift"}, {"endpoints": [{"adminURL": "​https://lax-staging.identity.example.com:35357/v2.0/", "region": "LAX", "internalURL": "​https://lax-staging.identity.example.com/v2.0/", "id": "4213934b23294a96b2b8c553dcf00551", "publicURL": "​https://lax-staging.identity.example.com/v2.0/"}], "endpoints_links": [], "type": "identity", "name": "keystone"}], "user": {"username": “david", "roles_links": [], "id": "4fae2db21d492881a68e4fe", "roles": [{"name": "_member_"}, {"name": "SwiftOperator"}], "name": “david"}, "metadata": {"is_admin": 0, "roles": ["9fe2ff9ee4384b1894a90878", "f3cdc7048c9945c56e108372"]}}}

'access' => 'tokens' => 'id' is the path to the valid token that would be accepted by swift for future requests ( as X-Auth-Token).

Since updating to the latest FileZilla, I am unable to use regular expressions with quick search. In the past, I would search for files using RegEx like so: 18121[7-9]|18122[0-3] This would filter all files with names except 181217 through 181223. Now when I try this, no files are shown. Thanks for any help.

In the transfer queue, if I rearrange the columns during a transfer, the direction arrows don't follow the source -> destination.

In the attached screenshot, I'm downloading files but, after rearranging the columns to match where I have my Remote and Local views, the arrows in the "Direction" column make it look like I'm uploading.

Love the program! Thank you!

Since the last version I can't edit files when I double clic on a file in the "server" columne. Before the last version I had no problem. It seems that the file is download but the associated program is don't launched, I have try to force the association for files with no success.

Error Program opens and connects to a remote Linux server successfully using SFTP on custom SSH port. Files dragged to destination and upon successful transfer of the entire queue the program immediately closes. No error messages in log file even in full debug mode. The program then has to be reopened to do more transfers.

I updated the FileZilla client to 3.41.0 this morning and am experiencing an issue during the directory retrieval process on 1 particular server. I regularly connect to about 12 different FTP servers on a daily basis and this is the only one giving me any issue.

Because of the sensitivity of information, I have obfuscated the host name, IP, username, and password in this public post. Happy to PM it to a tech for analysis if needed.

Status: Resolving address of ftp1.thehostname.com Status: Connecting to #.#.#.#:21... Status: Connection established, waiting for welcome message... Response: 220 TheRDNS.hostname.us Command: AUTH TLS Response: 500 AUTH not understood Command: AUTH SSL Response: 500 AUTH not understood Status: Insecure server, it does not support FTP over TLS. Command: USER * Response: 331 Password required for * Command: PASS Response: 230 User * logged in Status: Server does not support non-ASCII characters. Status: Logged in Status: Retrieving directory listing of "/ZZZ Mr Master/CDN Files delivered"... Command: CWD /ZZZ Mr Master/CDN Files delivered Response: 250 CWD command successful Command: TYPE I Response: 200 Type set to I Command: PASV Response: 227 Entering Passive Mode. (#,#,#,#,68,229) Command: MLSD Response: 150 Opening ASCII mode data connection for MLSD Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing

I have tried removing the remote directory that I am specifying in the site manager to land into, have tried forcing passive and active mode rather than auto-detect, have tried forcing UTF-8 instead of auto-detect, have tried checking bypass proxy, and have tried ALL available server types rather than auto-detect.

So far nothing has worked.

I can confirm that if I connect to this site from the command prompt ftp in windows 10 I am able to successfully connect and retrieve a directory listing.

I have inquired from the host as to what OS, FTP server, and version they are running to try to get more information. I'll update this ticket as I get more info.

I am certainly not alone as another user entered the IRC channel a little while ago with the identical issue, but he left before I was able to ask any questions.

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.

After upgrade from a previous version of Filezilla, upon opening the application an error message as follows appears:

"You can't use this version of the application 'FileZilla' with this version of macOS. You have macOS 10.13.6. The application requires macOS 10.14 or later."

In the Applications directory, the app symbol is shown with a semi-transparent crossed out symbol indicating that it cannot be used.

i am just update from 3.41.0 to 3.42.0 and have a little bug just know i am using google drive to upload file and when i click to team drive !st ok and when i click a folder is geting error and now i start to install the old version 3.37 please give me the link for 3.41.0 that is for me until abug being repair regards

Hi

Filezilla can't connect anymore through proxy HTTP/1.1.

This configuration worked fine since 8 years.

Filezilla : last version (3.42.1) (windows and linux tested)
Pure-ftpd : v1.0.36
Squid Cache: Version 3.1.23

Logs :

Squid (nothing wrong) :

1557475523.736  20091 IP.OF.CLIENT TCP_MISS/200 266 CONNECT HOST.FTP.SERVER:21 login.client DIRECT/IP.FTP.SERVER -

Filezilla debug mode :

Suivi :	CFtpControlSocket::ResetOperation(2114)
Suivi :	CControlSocket::ResetOperation(2114)
Suivi :	CFtpLogonOpData::Reset(2114) in state 1

I upgraded from 3.42.0 to 3.42.1 using FileZilla_3.42.1_macosx-x86_sponsored-setup.dmg and get the error that FileZilla 3.42.1 doesn't work with MacOS 10.13.6, required 10.14 or later. I'm using 10.13.6; 3.42.0 worked fine. The downloads page says "Requires OS X 10.9 or newer", https://filezilla-project.org/download.php?type=client. The release notes for 3.42.1 says it fixed a bug about compatibility with 10.13. However, the fix apparently made it impossible to work with 10.13. Does FileZilla no longer work with Mac OS X 10.13.6, or is a bug fix in the offing?

In the generated file src/interface/Makefile.in, there is not "--tag=CXX" argument in the filezilla_LINK variable, which makes linking fail in my environment because libtool complains about the missing tag.

I see that there are tries to add it in the corresponding Makefile.am but it's perhaps in the wrong variable? Anyway, I need the attached patch to compile filezilla.

When I change the priority of a file in the queue it is not recognized. As one file finishes the next file on the list is taken regardless of other files where the priority was set to "high"

FileZilla Client

Version: 3.42.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2019-05-08 Compiled with: x86_64-w64-mingw32-gcc (GCC) 6.3.0 20170516 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5 SQLite: 3.26.0 GnuTLS: 3.6.7

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 lm

When trying to look for a new update the program closes completely. After the last beta update FileZilla collapsed after starting. I deactivated the automatic search for updates and it stopped happening. When I go to check for updates manually (from the help menu), the search window starts but two or three seconds later the error occurs. If the automatic search for updates is not canceled, the program can not be used because it always collapses.

FileZilla Client

Version: 3.43.0-rc1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2019-06-19 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.28.0 GnuTLS: 3.6.8

Operating system:

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

Filezilla doesn't remember that I've told it to "Always allow insecure plain FTP for this server"

This happens if the site is configured as default, to use TLS if available. I would expect the warning to stop if I check the box on a server that will never support TLS. The checkbox does nothing.

It does appear to stop warning if you go in site manager and change it to use plain FTP only.

3.43.0

Hello,

The "Remember password until FileZilla is closed" checkbox used to be automatically ticked by default if this option was enabled last time the dialog was shown.

It doesn't seem to be the case anymore since version 3.44. Is it a bug or a feature (that would be too bad)?

Best regards, Underground78

As per subject: Clicking the Site Manager button closes FileZilla Client. FileZilla also closes if you go File->Site Manager

FileZilla Client

Version: 3.44.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2019-08-09 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.28.0 GnuTLS: 3.6.8

Operating system:

Name: Windows 10 (build 18362), 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 lm

Hi folks, In your latest version 3.44.2 Operating system: Windows 10 (build 17763), 64-bit edition

Version: 10.0 Platform: 64-bit system

I'm a keyboard kinda guy. When I fire up the site manager, I'll press 'P' to get to a site I have defined that starts with 'P', 'E' to the E's, etc. In prior versions, the blue highlight box would land on those sites. In this new version, a light rectangle will highlight the site I want, and it will connect if I hit a spacebar or enter, but the blue highlight stays on the last site I used a mouse to select. Thanks!

using from a long time filezilla .latest update has an issue /cannot select with ctrl (multiselect ).maby is just me ?

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"...

Failure to build from source, unable to find "unix/unix.h".

setting timestamp fails because "file doesn't exist".

file obviously exists locally and remotely because it just uploaded the file! what I'm not sure about is whether it doesn't see the local file or the remote file.

this doesn't happen in 3.46.0

Can't use SFTP on any version after 3.20.1 to the Lenovo ix2-dl NAS.

Status:	Connecting to xxx.ddns.net:1977...
Response:	fzSftp started, protocol_version=9
Command:	open "ftp@xxx.ddns.net" 1977
Command:	Pass: ********
Error:	FATAL ERROR: Remote side sent disconnect message
Error:	type 11 (by application):
Error:	"Unsupported protocol sequence"
Error:	Could not connect to server

Note: 1977 port is forwarded to 22 on router.

Works fine with 3.20.1 and below. Also tested with latest versions of other ftp clients such as CyberDuck and FireFTP and they work fine.

In the certificate details, if you're using TLS 1.3 and an ECDSA certificate, the key exchange will show "ECDHE-RSA", when it should be showing "ECDHE-ECDSA".

It only seems to happen when using TLS 1.3, prior TLS versions correctly display "ECDHE-ECDSA".

Hi,

I tried on Mageia Cauldron to build latest 3.47.0_rc1 release but it fails to build due to some missing headers in source:

-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__  -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -pthread   -I/usr/lib/wx/include/ -I/usr/lib/wx/include/gtk3-unicode-3.1 -I/usr/include/wx-3.1 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -Wall -c -o filezilla-aboutdialog.o `test -f 'aboutdialog.cpp' || echo './'`aboutdialog.cpp
aboutdialog.cpp:1:10: fatal error: filezilla.h: No such file or directory
    1 | #include <filezilla.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [Makefile:1191: filezilla-aboutdialog.o] Error 1
make[4]: Leaving directory '/home/iurt/rpmbuild/BUILD/filezilla-3.47.0-rc1/src/interface'
make[4]: *** Waiting for unfinished jobs....

If you look at "src/interface/" there are not any "*.h" headers files.

Regards, David

When logging in to the webserver the tree explorer is not working First level works for ex brusdata.se but clicking on next level public_html is not possible to set focus to. Operating system type on webserver is Linux

FileZilla client appears to have a bug in importing password-protected private keys for SFTP when encrypted with AES-256-CBC. I found no mention in docs re: the intentional exclusion of this cipher combination, plus no error message is returned, which suggests that this may be a bug. There are no relevant log entries or terminal output, even in debug mode. This was tested and confirmed on Linux, Mac OS X and Windows 10.

You can test by importing the following key through Settings > SFTP > Add key file...:

Proc-Type: 4,ENCRYPTED DEK-Info: AES-256-CBC,e2baef8c24ab9008854a80cae86f33ed

WT4xwn5Y4tgKp6qpFYOwJlzE22uJuw7dwbzmGqogC/nLeAOfl3SuUsWuNM5ORYh/ 29YbHN5BqeyiY9ANbz7777/gp5T2PdckdoVbMvFOYlgwq7DbDzrUBEJM3cq1quqe hHqKkcvOAX+XSnSMI4OTzBaN1Qd1V7QP+aFMeSWfzQdq8SHn9lxWqolTdLeYmEOR CFouROSf7YdD/HYx9gOmiNAwVtwZ+oSZY9hHPo7pfJ3DLO0oq+hbjYUexYZxQfUB 5x7ceJbbl+MyNr1n4juAf3e99c8BTTzEZBls7osXo/z+Rnn8qhYC8MfCt1RuFc xxClGlWvs0c2A14+epKwAcZq1aOueNgjKu5G9mQHkv7YmbK3dw60VEKhVh9imUuR oT2yGTOSH0B9B89T2wqz71xbGw0bPfbU9tRxx7oUeLSAVOant3DnAW+dcp2xQHjx r4l3NHy1+mtEpG0siqzLyM48YRam/I0y0dvExlvUuVZGCKazDKweOHvROfNRbL8g BYs8ept2qHj0xItqBLU+h1ikduEa9Pye1xalWW4KkX1D7QfACal3dO8HeM+bbMED SnSZ1Ujg1kvwPp1QrKzYF3DCTIhygtVmjc9THwUkV2qr9EZJwZAinUf+ijvHKmUw /wQCXsD0sDd/uZX4tE0hBgWuH2X/AAnD4tqYFY9aFhta9O37LE8X1PXSHcsDrcN/ Wc9AOlEFymJpohYGXDN3UxCy5W92Ht5w5RrnkYLVOLOhH2QtU5+2QaokUgXQINQ8 VKIgM+luBtnIFlv/jEL73ILUnkWqIpZZRKTKXDDndyYnF3w+47Y+YyK6fczPaf2q lv6LFJoZfK58lNP6XApnwCdwpzXIpE7FljlRlrgFW7y/bJ87lcs2u4uL4KODEBqt xsY0UGxrNuGfVY8OcNXGTSnakPGP4kKitMknu4WKfKU4NwcJ7v9kEwObt1zcpkM5 HM8BOwgnbXdS4CWZGJ5ximCYrPQ17URitvKktQ+FS1l0R5gvCmNhMmUx373VqOG6 K4I890jzvCdXRuTx0/2hbpJHHOqXD6thiTAKOQUOiRrt83iBKOxt0sOlSApxuCr6 3aYv1EbHAJLTnV1TUzg78Yh6GzUGdsoxD3WFjVIsw7EKb+VuCQbTEcu+kaz17U8G mBvoCHDRJAos6TMsJOF8IQHZFyAg7XfFTdTOuIc1zz6E7h+8j9foh9tR2Ct5K6s1 XlkP9kFmu2bqNQu6tkEb14f/S1cCBxoXCVs4ne75Oq/VLp1QO+U54QnabiVlv3H1 /89jGi/Sa/gSnyyCqyO2q65XUQ4GYoLWMurIWIqA8QcBQW3OB4GFvD0K0ilNfQQo Ytt+4xVBsHG+uFb89rnV0gzY94jltUq4CkB33AuzvxBwnGs5pPqrkF7XvhYIyrZR VxEQ2QMBDrHtjOBmO8/ihUDDP/nQTwVOga7gaj2sO7/acsjeZkp0ZxPcpXzXJzr+ xcVPkELhaJjBd+IEysPETk9HppaiA9NeYVm+0XFIHgKaWIRDtXG0mhkttjlssAYU 2amt78Mtt5RnAf+3mfP4O26d2GgfU/os3eTaD0ldO5DEdu+bukoAOl8QVUq6p9Wa

It does not return any error messages, nor any feedback whatsoever. A key encrypted with AES-128-CBC is imported successfully - it reports that it needs to be converted in PPK format, and then asks for a passphrase:

Proc-Type: 4,ENCRYPTED DEK-Info: AES-128-CBC,D05FFBBB1E6D76BBF75EFA96C24A3BD9

loGvARZjfLa2d/DQS3rQHAxdIe4g/UytBR3kdtKO65juYhZP6ntNvKBFbIMOJFZY KPabYyof8zYvQTXEIqAypmAMXU3J6/GISzW3wXe3ZvC/uTaFiTVSXCIRkfk72cOd 6aTAuo5xMXelmbdqwKu0FkrZgAMG7lDumClshTMG47+g7BxHrszr4yo3FkiRs5fN kFSJ+499wAZV0NOThkkQi28H/+6LzQ+5siNErJXkWTNk+G/f72xRfSkT9k5roQ/L ycS91sd8Xvrt1ywtvMvx7K1mta1rvHuqOMmGazsS4jVAo8xPn18KztyZLkyckDFE TpqP8Zji0+n7O+aCJmmWdqWLs4QeiovIlzO6BLXGkGAEf7AsB8qyTbEq9FRGPi7p fC6Ei+7zIquQy75A4H41NXMMoyMgOg0X1j6Mc9Hq/6tWhxrsAYEGygVE6WVG8YAD 01bTYuXf064v/lXPmtXOdbEFcGFgXtQ2OzRVTRvdF4v8uxlsdc0KmeqzuOD6Ux9r N+WDF5wAvab8P/S4zruxOnCqPJwKNTTZ/lFbD93BZqHu+kIvQwKna4oFIzT0Au6J u5+ZqCXSbdMdRO9goiVvGEXfJEGkMZG+GWp+whg/xnMmnUy0h0bLWSB1ERKSUvdA M9H5yCJungXUU1BPQ5h7OiA2b452S+ayMbmin+G3nuqcBQDoPH9kLakXjQCRRCd7 3I6QR7rsDFpkCGgwnEcKLpNteEb19Ce1PDpyXUhFypH2MHbuYRATP0FF++uvvxjf NUOvriQ54pw8jYve8L156DsH6x83xyXM1Q3/3rTjmKbi11qa+WpxTEbSe/Q/GXO5 ebhPWGSUKsnukQi+WMmW99nh2/WyTZpLF8Kc09LfVVHDHRiBZUDNzX3hfpRgaffs yL17jn6UgxVjGOXbQtBIlJs1J2UMg6wC7sClGmNviQNAvzrYxWwS2ewebVK6IB5w x/jLMEz85GuJkHljpml6FuSvVQQmNM8wC6y6NY90veTy38082Yz558RPvJlYRWJb VVHq3kjKjmULAfgSBGFtmh+kJ1YVACwEdzdj71DVDGyagsTiAVNEyvAn+gCOhxV/ umood21YxZyqxSD3MtTTwPAvMqf0LDJws7wTl+fuDd2E43LEXlh2ATyMe4+mvtTF zYYmSJGZeZekdxvyB8B8v0vEEQ7ontfKzloZkibJPq9610R7tQ1HvWmkiNUq9io+ iXUEeTLLL75jbAYpcyzJNIgu+98eeVQkDdkwbYIG4MKNvBv6vafLn0KqnPuo9T71 yRe4Ut0Uxz8kFOD4MLHae62HiL27V6RsntwSnhGDWmA9KgC16SJwqiSzIxjiKnnJ S3pgBSQ7vxMjr3DsKS6f/ZEPlq/Py3UCwjH0hXgI+NnD2WsS5Hfpf9eXOz/FIztq axe4JnzGyDZfb42G47Gll114lVVYUd2PEWUlFRT/OrgETsy/QN0QFbp2hQdWzb3u XxXpu6+yHb/mj+DhnohAN3cLlYxwAeJhTE2RZ2QhJmpFy19EFlmbxsiTxe7Puesu Wb8dxwcCrgoscxjzlCf9k6zNntCpm6al2uEtuEgjdd3KCbEoeSSwu+QO8NbTeO

Passphrase for both keys is test2020.

hi.

There is no problem with Google Drive FTP. Connecting. However, I cannot make transactions with Google Drive or Dropbox in "filezilla site manager synchronization". As you can see in the video, it makes you wait for minutes.

What should I do to back up my sites to Google Drive?

FileZilla Pro

Version: 3.47.2.1

Build information:

Compiled for: x86_64-apple-darwin19.3.0 Compiled on: x86_64-apple-darwin19.3.0 Build date: 2020-03-18 Compiled with: Apple clang version 11.0.0 (clang-1100.0.33.17) Compiler flags: -Werror=partial-availability -Wall -g

Linked against:

wxWidgets: 3.0.5 SQLite: 3.31.1 GnuTLS: 3.6.12

Operating system:

Name: Mac OS X (Darwin 19.4.0 x86_64) Version: 10.15 CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: /Users/barisyilmaz/Library/Containers/org.filezilla-project.filezilla.sandbox/Data/.config/filezilla/

Building the FileZilla client fails on aarch64 as observed on OpenBSD/arm64, but the problem is generic and should affect all Unix-style operating systems on aarch64 (64-bit ARM).

ld: error: undefined symbol: platform_aes_hw_available

referenced by sshaes.c

libfzputtycommon_a-sshaes.o:(aes_hw_new) in archive libfzputtycommon.a

...

Linking fails because the functions

platform_aes_hw_available() platform_sha1_hw_available() platform_sha256_hw_available()

are undefined.

The problem is in the included putty source. On aarch64 (#if HW_AES == HW_AES_NEON), the missing functions are called from sshaes.c, sshsha.c, sshsh256.c. In the original putty source, they are provided by unix/uxutils.c. However that file was omitted when the putty source was included in FileZilla.

Simply adding putty's unix/uxutils.c and adding it in Makefile.am will fix the problem.

I have tried putting the path in file associations but it doesnt work transfers to somewhere_{,I dont know where tho. Its many different pdfs, not just one. If I dont specifiy a path in file associations it tries to load in my default which is notepad++}

The following bug has appeared today, immediately after I had upgraded Filezilla to version 3.48.0. It didn't happen with previous versions (I have been using FZ daily for years --- thank you for creating this wonderful tool).

Now, whenever I doubleclick a LOCAL file in order to edit it, I get an error message popup reading "Opening failed: The file '[FILENAME HERE]' could not be opened: The associated command failed" (+ OK button). This is a spurious error message, as the file does open just fine. This happens with every local file I try to edit, forcing me to close this popup on every local file edit (a very common occurrence for me). It does not happen with files on the server.

My relevant settings are:

• File lists -> Double-click action on files -> View/Edit
• File editing -> Default editor -> use custom editor -> "C:\Program Files (x86)\Vim\vim74\gvim.exe"
• File editing -> Always use default editor

Additional observation:

• If instead of double clicking the local file, I right click it and select "Edit" the same error appears. However, if I select "Open" it does not.

P.S. Also posted this on the forum.

Whenever I right click and choose "Edit" menu for a file, for instance a txt file, although the file will open up in my Macbook Textedit app as usual, an error message following will popup says "Opening Failed.... 'file path' could not be opened: The Associated Command Failed".

File extension included txt php htm html etc.. Although I didn't setup any filetype association under the setting menu, it shouldn't behave like that. Also the filetype association command is not working too I had tried. It only happens in this latest app version for Mac.

Hello,

there is a problem with the program associated to a file (to open). By example I have created fils association for .lo and .txt, and what I get in the parameter widow is : log "C:\Program Files\Notepad++\notepad++.exe" %fphp "C:\Program Files\Notepad++\notepad++.exe" %ftxt "C:\Program Files\Notepad++\notepad++.exe"

So juste one string for both association. I think a \n is missign somewhere.

Wonderfull job by the way.

Codrescu Stefan

hi, whenever i try to open a new filetype with any programe like NotePad++ but it starts to show error, to fix it i have to go to Edit > settings > File type association and have to define each rule in new line.

by default the filezilla is adding it in same line which cause the error.

Solution: filezilla has to add a new line \n after each new rule to make it fixed.

EX:

bytes "C:\Program Files (x86)\Notepad++\notepad++.exe" conf "C:\Program Files (x86)\Notepad++\notepad++.exe" conf_letsencrypt "C:\Program Files (x86)\Notepad++\notepad++.exe" log "C:\Program Files (x86)\Notepad++\notepad++.exe" php "C:\Program Files (x86)\Notepad++\notepad++.exe" stpl "C:\Program Files (x86)\Notepad++\notepad++.exe" tpl "C:\Program Files (x86)\Notepad++\notepad++.exe"

FileZilla Client

Version: 3.48.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2020-04-27 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.31.1 GnuTLS: 3.6.12

Operating system:

Name: Windows 10 (build 18363), 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\Shiva\AppData\Roaming\FileZilla\

So i have reinstalled filezilla twice because i thought that could fix my issue. Not.

Im using the blackboard theme with multiple tabs for remote servers. The issues is when opening the client all windows tabs are sized to the previous use. Perfect. BUT upon opening a new server in a new tab the remote site window fills the entire right side. It ignores the window size i have set. This is really annoying because when connecting to allot of servers, you need to manually resize the remove site window again, and again, and again....

Under File search...

Search directory: string, not yet translatable.

Under Settings/File lists...

Name sorting mode: string, not yet translatable.

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

While working on files, saving then switching to FileZilla (FZ), FZ will prompt a message "File has changed".

This has the option "Upload this file back to the server: [] Finish editing and delete local file"

As I was completing the task, the checkbox "Finish editing and delete local file" was checked, then it occurred to me that I wanted to change something.

I pressed escape, canceling the operation. For me it was a bit of a surprise that the Escape button and the X on the right corner basicly perform the "No" action - therefor deleting the file - instead of canceling the operation as a whole.

Action: Esc (cancel) Expectation: close prompt, don't perform any action. Reality: Alias for pressing the "No" button, executing the selected checkbox.

Just updated a couple of times and now can't resize the center post. Here's what I know, and what I'm able to do. ​https://www.screencast.com/t/PObeHvriSR

Any help is appreciated.

Info from About: FileZilla Pro

Version: 3.50.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2020-08-31 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -O2 -g -Wall -Wextra -pedantic

Linked against:

wxWidgets: 3.0.6 SQLite: 3.31.1 GnuTLS: 3.6.14

Operating system:

Name: Windows 10 (build 19041), 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 bmi bmi2 adx lm Settings dir: C:\Users\Cenay Nailor\AppData\Roaming\FileZilla\

I noticed today an HMA VPN shortcut on my desktop. I did not install it.

Checking its directory in C:\Program Files, I find that it appeared on October 6. That is when I launched FileZilla after not having used it for a while. It prompted me to download and install an update to FileZilla, which I did.

Was HMA VPN bundled with that within-app update?

Thank you, Blake

When I try to connect to any SFTP server I get an error "fzsftp could not be started". Interestingly if I switch to Czech language I get an "fzputtygen could not be started" error (of course translated). It happens since 3.52.0 version. Version 3.51.0 works. My guess would be that the double slash in path to fzsftp is causing the problem

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/

file fi_FI.po?revision=9791

As can be seen below, lines 4263 and 4267 have same content, but they should not be the same. Line 4267 has incorrect translation.

Line 4267 should be "Suodata pois kohteet, jotka täsmäävät yhdenkin seuraavan kanssa"

4261 #: ../src/interface/filteredit.cpp:123 4262 msgid "Filter out items matching all of the following" 4263 msgstr "Suodata pois kohteet, jotka täsmäävät kaikkien seuraavien kanssa" 4264 4265 #: ../src/interface/filteredit.cpp:124 4266 msgid "Filter out items matching any of the following" 4267 msgstr "Suodata pois kohteet, jotka täsmäävät kaikkien seuraavien kanssa"

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.

After installing the latest version of FileZilla client, the file timestamp data is no longer preserved on the transferred files. Verified that the option is still set in the transfer options.

I have been using v3.51 and earlier versions to upload files to a server running SSH-2.0-OpenSSH_7.4 to support sftp/ssh file transfers.

since updating to v3.52.05 (and also with 3.52.2), I have been unable to upload or download files from the server. It appears to write and then I will see an error that the file transfer failed, and then when it retries, it brings up the overwrite dialog to try to overwrite the file I just uploaded or downloaded - the file that is on the server after the initial upload is 0kb in size.

Trace:	DuplicateHandle failed
Trace:	CControlSocket::ResetOperation(2)
Trace:	CSftpFileTransferOpData::Reset(2) in state 4

I have been able to workaround by downgrading back to 3.51.0 for the time being.

It appears that for both the 3.52.2 uploads and downloads, the following message appears after the put/get command respectively:

Attaching files with the debug logs for both upload and download in each version.

My Internet Connection has 5 MBit/s Upload limit.

I wanted some 1500 MBit/s upload speed. To achieve this I have to set Filezilla to 150 kBit/s in the speed limit dialog. See Screen Shots. When I set the speed limit to 600 kBit/s, FileZilla consumes the whole upload bandwidth.

This used to be working right in previous versions of FileZila Client

FZ will transfer all files but at the end the UI just drops out. I wish there would be a way to provide more details over and above what the "FileZilla.log" in "debug" mode can provide?

When I try to connect an error pops up: Error loading xml file invalid xml file

I've double checked that data is correct. I have tried uninstalling and reinstalling, disabling my antivirus, clearing my cache, deleting each xml file in the app data and every time I get the same error.