Custom Query (4044 matches)

FileZilla Client

Version: 3.63.2.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2023-03-03 Compiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110 Compiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type

Linked against:

wxWidgets: 3.2.1 SQLite: 3.39.4 GnuTLS: 3.8.0

Operating system:

Name: Windows 11 (build 22621), 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\TR\AppData\Roaming\FileZilla\

Issue-This version of Filezilla is not handling illegal characters correctly. Previous versions have not had this specific trouble to replace illegal characters from the server while transferring to a Windows system.

The attached screenshot shows 3 files that failed transfer from server to Windows directory due to the illegal Windows character colon (:) present in the 3 files. The first transfer initiated using the filezilla preference of Automatic for FTP File Types resulted in the 3 files failing.

When I changed the Filezilla preference to Binary for FTP File Types and retried the folder download, the same 3 files failed.

This is not correct behavior and is also strange because in the Filezilla queue area the illegal character colon has been replaced with underscore. You can confirm that the illegal character exists on the server by reviewing the 2 highlighted files on the server side of Filezilla remote window.

Local Directory

"T:\pathfinder\199800 Fantastic Four 1_2 (Wizard).cbr" "T:\pathfinder\199800 Generation X 1_2 02 of 02 covers.cbz" "T:\pathfinder\199800 Spider-Man 1_2 (Wizard) 02 of 02 covers.cbz"

Remote Directory

"\199800 Fantastic Four 1:2 (Wizard).cbr" "\199800 Generation X 1:2 02 of 02 covers.cbz" "\199800 Spider-Man 1:2 (Wizard) 02 of 02 covers.cbz"

Note: When I initially tried to download multiple directories that contained illegal characters, filezilla basically crashed (no further input or output from filezilla window). Filezilla needed to be closed completely and restarted in order to resume normal operations.

By trial and error I was able to figure out that the illegal characters in the directories was what Filezilla took issue with. I decided to download the files individually from the server to see if it could complete successfully and they did. (See the 3 files outside of the directories in the screenshot). So, Filezilla can transfer files with illegal characters correctly individually, but from within a directory queue Filezilla is failing to transfer correctly.

I also confirmed that the files could be downloaded successfully with the illegal characters replaced by installing WinSCP and queuing the 5 directories I tried with Filezilla. All directories were successfully downloaded using the Automatic File Type preference and the illegal colon (:) characters were replaced with %3A.

Since last week, one of my customer cannot connect to FileZilla server. Keep in mind that it was working before. One of her colleague is able to connect to the server on the same network and I can connect with her account on another network. In the window, it says:

AUTH TLS 502 - Auth command is not supported. 502 - Please contact your network administrtator to enable FTPS service

What cause this issue?

Seems like I'll have to upload the attachments afterwards.

I have uploaded a bunch of files to a server, with unicode characters in the file names.

I'll attach a screenshot of how such characters look like in fileziulla in the server panel.

For comparison, I'll attach a screenshot of a terminal where I'm connected via SSH to the very same server and I've run a "ls" command: you can see the unicode characters properly rendered in the output.

My problem is exactly as described in Bug Report 12199, but I could not find an answer to it. When connecting to the server the certificate shows that it is not trusted and the buttons to override that and force trust are greyed out. If I use OK and move on it does connect. I have had my ISP check that the certificate is correct, and it is. Sadly it cost me a lot of money to do that. See attachments. I am using the latest Filezilla (it automatically updates, so that is always the case). This happens on both my machines which are Windows 10 Pro 22H2 and Windows 10 Home 21H2.

File sizes on remove directory listing are off by 10^-1.

Only files over 100MB are affected.

Example, file on local dir listing is 100MB. File is transferred successfully. File size on remote listing is 10MB

Please see attached screenshot.

After connecting to a site from a bookmark let's say my local site pane has:

(bug seems to occurr with at least two nestings) d:\sites\foobar\

And remote site pane has:

/opt/webroot/

It happens 100% of the times to me that if I right click the "directory listing filters" icon in the toolbar to enable the filters, the local site pane changes to something different, such as:

d:\sites\another-site\

filezilla client connected, but the not listing the directory. Error " Could not retrieve directory listing Error listing directory '/'."

Kindly help me resolve this issue

02 May - please see attached file. FileZilla is not working on my machine & IT and cybersecurity have exhausted all options.

I downloaded FileZilla Pro earlier this week and had NO issues with it until yesterday. I kept getting the "421 Proxy is closed" error. I upgraded to the newest version of FileZilla yesterday, checked all my network connections, etc. and roped in IT--they couldn't find any issues and were already allowing the app. I've run every diagnostic and nothing is working. Like I mentioned before, I don't have an IT background & have tried just about everything. Any suggestions? Below is the message log...

Status: Connecting to <server name>... Response: fzSftp started, protocol_version=11 Command: open "<server name>" 22 Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server Status: Disconnected from server Status: Resolving address of <server name> Status: Connecting to 52.227.72.32:21... Status: Connection established, waiting for welcome message... Response: 421 Proxy is closed Error: Could not connect to server Status: Waiting to retry... Status: Resolving address of <server name> Status: Connecting to 52.227.72.32:21... Status: Connection established, waiting for welcome message... Response: 421 Proxy is closed Error: Could not connect to server Top

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 :)

FTBFS 3.64.0 using libfilezilla 0.43.0 on GCC 12.2 (Debian unstable).

sftp/sftpcontrolsocket.cpp: In member function 'virtual int CSftpControlSocket::DoClose(int)':
sftp/sftpcontrolsocket.cpp:514:63: error: 'typedef class std::deque<std::tuple<fz::event_handler*, fz::event_base*, bool> > fz::event_loop::Events' is private within this context
  514 |                 auto threadEventsFilter = [&](fz::event_loop::Events::value_type const& ev) -> bool {
      |                                                               ^~~~~~
In file included from /usr/include/libfilezilla/event_handler.hpp:4,
                 from sftp/../../include/misc.h:6,
                 from sftp/../../include/libfilezilla_engine.h:25,
                 from sftp/../filezilla.h:1,
                 from sftp/sftpcontrolsocket.cpp:1:
/usr/include/libfilezilla/event_loop.hpp:116:75: note: declared private here
  116 |         typedef std::deque<std::tuple<event_handler*, event_base*, bool>> Events;
      |                                                                           ^~~~~~
sftp/sftpcontrolsocket.cpp: In lambda function:
sftp/sftpcontrolsocket.cpp:515:32: error: 'const std::deque<std::tuple<fz::event_handler*, fz::event_base*, bool> >::value_type' {aka 'const class std::tuple<fz::event_handler*, fz::event_base*, bool>'} has no member named 'first'
  515 |                         if (ev.first != this) {
      |                                ^~~~~
sftp/sftpcontrolsocket.cpp:518:37: error: 'const std::deque<std::tuple<fz::event_handler*, fz::event_base*, bool> >::value_type' {aka 'const class std::tuple<fz::event_handler*, fz::event_base*, bool>'} has no member named 'second'
  518 |                         else if (ev.second->derived_type() == CSftpEvent::type() || ev.second->derived_type() == CSftpListEvent::type()) {
      |                                     ^~~~~~
sftp/sftpcontrolsocket.cpp:518:88: error: 'const std::deque<std::tuple<fz::event_handler*, fz::event_base*, bool> >::value_type' {aka 'const class std::tuple<fz::event_handler*, fz::event_base*, bool>'} has no member named 'second'
  518 |                         else if (ev.second->derived_type() == CSftpEvent::type() || ev.second->derived_type() == CSftpListEvent::type()) {
      |                                                                                        ^~~~~~
sftp/sftpcontrolsocket.cpp: In member function 'virtual int CSftpControlSocket::DoClose(int)':
sftp/sftpcontrolsocket.cpp:524:43: error: cannot convert 'CSftpControlSocket::DoClose(int)::<lambda(const std::deque<std::tuple<fz::event_handler*, fz::event_base*, bool> >::value_type&)>' to 'const std::function<bool(fz::event_handler*&, fz::event_base&)>&'
  524 |                 event_loop_.filter_events(threadEventsFilter);
      |                                           ^~~~~~~~~~~~~~~~~~
      |                                           |
      |                                           CSftpControlSocket::DoClose(int)::<lambda(const std::deque<std::tuple<fz::event_handler*, fz::event_base*, bool> >::value_type&)>
/usr/include/libfilezilla/event_loop.hpp:65:86: note:   initializing argument 1 of 'void fz::event_loop::filter_events(const std::function<bool(fz::event_handler*&, fz::event_base&)>&)'
   65 |         void filter_events(std::function<bool (event_handler*&, event_base&)> const& filter);
      |                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
make[4]: *** [Makefile:1292: sftp/libfzclient_private_la-sftpcontrolsocket.lo] Error 1

When start drag from my PC and the cursor fall over (not drop) the tree of remote server the software give the error "Drag & drop failed"

The remote server on Linux RH.

Steps to reproduce

1. Upload a large file (I tried a 1 TiB file) to a proftpd server with "slow" disks using default settings in active mode.
2. Once all disk caches on the server are filled (which happened always somewhere around 12 GiB) and the server has to sync the data to disk, it'll set the TCP Window Size to 0 while the data is written and synced.
3. After that, it'll increase the window size again to continue the transfer.

Expected behavior

FileZilla should consider this an active connection (as long as the tcp window size probes are still ACked ofc), report a 0 byte/s current transfer speed, and continue normally once the window size has been increased again.

Current behavior

FileZilla terminates the file transfer with the reason "connection timed out", probably because of oversight within the timeout logic. It probably only checks for 0 bytes/s transferred instead of also checking if the TCP connection is still alive and only set to a window size of 0. Funnily FileZilla tries to restart the connection but then fails because the temporary ".in.*" file still exists (A 2nd bug, or do we hit some kind of edge case here?) Also noteworthy, the retry setting was set to 5, but FileZilla did only one automatic retry and then failed the transfer. Also, the 10-second delay between retries was not honored here, as the retry happened instantly after the reset was sent to the server. And also noteworthy is that FileZilla will delete the partial upload from the server once it failed the transfer...

Workaround

Go into the options and set the timeout to 0.

But this has still undesirable side effects like no timeouts are detected anymore and the transfer will therefore get stuck completely once an actual timeout happens.

(Admittedly, another workaround is to set the delay kinda high to 5 minutes or so, but even though it would work for this connection, it'll unnecessarily slow down other transfers to different servers and also not correctly detect the connection state. It'd only work if the server manages to sync and accept data again within 5 minutes.)

Proposed fix

1st Add a TCP connection state check into the timeout detection logic (not a timeout if still packages are exchanged, see screenshot for example connection) 2nd And (maybe) add an additional option within the connection timeout section for backward compatibility like "☑️ treat a Zero TCP Window Size as timed out" with a default value of being unchecked (Enabling this option will result in the current behavior again). 3rd (purely visual), fix the connection speed that is shown in the UI, currently it never shows 0, not even if "Display momentary transfer speed instead of average speed" is enabled. 4th If the reconnect logic triggers a reset of an active file transfer, it should expect the temporary ".in.*" file already be present and automatically resume it instead of failing the transfer because it already exists. (My default file exists action is set to "Ask for action" btw, but it also didn't ask, it just failed the (unnecessarily triggered) retry) 5th honor the reconnect settings also for automatic reconnects (amount and delay in-between).

Suddenly cannot upload newly created files from my local directory to remote directory. If it is an old file/already on the remote side it has no problem uploading and rewrites it again. Regardless of file extension.

full error messages:

15:48:49 Status: Starting upload of /Users/Jones/Documents/My Websites/clipfreefunnyvideo.com/footerads.php 15:48:49 Command: cd "/home1/clipfree/public_html" 15:48:50 Response: New directory is: "/home1/clipfree/public_html" 15:48:50 Command: put "/Users/Jones/Documents/My Websites/clipfreefunnyvideo.com/footerads.php" "footerads.php" 15:48:50 Error: /home1/clipfree/public_html/footerads.php: open for write: received failure with description 'Failure' 15:48:50 Error: File transfer failed

I just updated my FileZilla client for the first time in a while (via the prompt on startup), and after that it started giving me an error message every time it started or closed the program. The error on starting was:

An error occurred loading the transfer queue from
"C:\Users\myusername\AppData\Roaming\FileZilla\queue.sqlite3".
Some queue items might not have been restored.

The error on closing was almost identical:

An error occurred saving the transfer queue to
"C:\Users\myusername\AppData\Roaming\FileZilla\queue.sqlite3".
Some queue items might not have been saved.

Additional information:

• The program is installed to a different drive than the folder it is trying to write to. It is located at "E:\Program Files\FileZilla FTP Client" and the folder it is trying to write to is on the C drive (listed above). Not sure if this is relevant or not, but you said to be verbose.

• The file did exist in the location the program was looking, and the previous version of the client could read and write to it just fine.

• The error messages stopped showing up when I deleted queue.sqlite3 and let the program regenerate the file, although I have kept the old queue.sqlite3 just in case. This means that the issue is solved for me, but I figured you might still want to know that this file isn't always compatible if you forget to update for a while and then go up by a couple versions at once.

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.

Hi!

I regularly package Filezilla for XtraDeb.net. Filezilla version 3.64.0 built fine on Ubuntu 22.04 but version 3.65.0 is breaking with the following error:

configure: error: Boost Regex 1.76 or higher not found.

You can find attached the full build log.

I'm also able to build fine on Ubuntu 23.04 (lunar) after adding libboost1.81-dev. Unfortunately, this package does not exist on Ubuntu 22.04. It only has libboost1.74-dev.

I think the error might be related to revision 10985. Would it be possible to patch back Filezilla 3.65.0?

Thank you! Jhonny Oliveira @ ​https://xtradeb.net

Also affects filezilla 3.65.0.

Debian maintainer can easily reproduce this issue.

Debian bug: ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043556

Report:

Filezilla crashes when you go to Settings -> Transfers -> FTP: File Types -> Treat the following filetypes as ASCII files. And then remove all the filetypes except one from the list, and then click the last filetype.

Video showing the crash attached.

Backtrace attached.

Settings checkbox for "Display momentary transfer speed..." indicates opposite of its value.

In Settings, under Interface, in the box headed "Transfer Queue," the checkbox for "Display momentary transfer speed instead of average speed" actually toggles the opposite of what it states (ie, it shows momentary speed when unchecked, and average speed when it is checked).

This is a legacy bug that has been around for quite some time. This bug does not affect functionality, so marked as low priority.

When I try to set an Active mode IP address, I get an error message saying "Associated program not found".

When I check Filetype associations, I see the following:

txt "C:\Program Files\WindowsApps\Microsoft.WindowsNotepad_11.2305.18.0_x648wekyb3d8bbwe\Notepad\Notepad.exe" %f

If I change it to this, everything works:

txt "C:\Windows\Notepad.exe" %f

Does this imply the installer has a bug?

Hi team,

I have my version to not to check for updates, and yet everytime I start up FileZilla it tells me there is an update available.

I'm running FileZilla 3.62.2

We run it on computers that need admin access to update and so it's just an extra step each day to remove the pop up prompt.

Cheers, Steve

FileZilla Client

Version: 3.62.2

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2022-11-22 Compiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110 Compiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type

Linked against:

wxWidgets: 3.0.6 SQLite: 3.39.4 GnuTLS: 3.7.8

Operating system:

Name: Windows Server 2016 (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 bmi bmi2 lm Settings dir: C:\Users\steve\AppData\Roaming\FileZilla\

Dear good morning, for some time it is impossible for me to see the download of files from the server to the local folder tree. Im use Windows 7

When downloading a file from an IBM Z/OS mainframe to a PC using the Mac client (3.63.2) if the file contains a Carrot, which is 0xB0 in EBCDIC and 0x5E in ASCII, the character does not get converted resulting in a non-printable 0xB0 on the Mac file. This can create issues with other programs trying to process the file. Is it possible to update the ASCII translations to properly handle this character?

FileZilla Client

Version: 3.63.2

Build information:

Compiled for: x86_64-apple-darwin22.3.0 Compiled on: x86_64-apple-darwin22.3.0 Build date: 2023-02-23 Compiled with: Apple clang version 14.0.0 (clang-1400.0.29.202) Compiler flags: -O2 -g -Wall -Wextra -pedantic -O2 -g -Wall -Wextra -pedantic -mmacosx-version-min=10.13.0 -Werror=partial-availability

Linked against:

wxWidgets: 3.2.1 SQLite: 3.39.4 GnuTLS: 3.8.0

Operating system:

Name: macOS Ventura Version 13.3.1 (Build 22E261) Version: 13.3 CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 aes pclmulqdq lm Settings dir: /Users/<redacted>/.config/filezilla/

When changing file name on remote, if you press <return> to finalize change, causes crash. If you click out of that file name, change is ok-no crash.

Hello,

We are using minio cluster and activated ftp feature. Then we tried to connect with filezilla on a windows machine. It is connecting successfully, and listing buckets fine. But when we tried to get in a bucket, we can't see folders.

PS: When we use MacoS everything is fine. On windows , when we try winscp, it is listing successfully. Only filezilla can't.

FileZilla installer FileZilla_3.65.0_win64_sponsored2-setup.exe has viruses:

CrowdStrike Falcon Win/grayware_confidence_60% (D)

ESET-NOD32 A Variant Of Win32/PlayaNext.B Potentially Unwanted

Rising PUA.PlayaNext!8.188A6 (CLOUD)

I am trying to launch the FileZilla Client and keep receiving the error message below. It has been updated to the latest version and we are still unable to connect.

Error: Could not connect to server Status: Waiting to retry... Status: Resolving address of ftp.cognitionlms.com Status: Connecting to 23.253.25.67:21... Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server". Error: Could not connect to server

Filezilla client v3.64.0 under Windows asks me to update almost every time I launch it, because there's a new version available, but: 1) Check for FileZilla updates automatically is set at "NEVER". 2) It doesn't even know what the new version is and only shows "Unfortunately information about the new update could not be retrieved." If an user chooses to not automatically check for updates, why is Filezilla spamming them with a new update dialog that doesn't even contain any useful information to begin with?

Steps to reproduce:

• Run FileZilla
• Connect to an FTP server
• Upload anything (now systray icon appears)
• Exit FileZilla

Ooops... icon in systray stil exists and disappears only after hovering mouse over it. Taskmon shows that FileZilla already unloaded and not running.

It starts after upgrading to 3.65.0 (from 3.64.x I suppose) and still exists on 3.66.1.

I keep receiving the 403 forbidden error

I updated FZ to 3.66.1 and when I try connect (sftp ssh protocol) I receive the same error message:

Status: Connecting to (IP)... Response: fzSftp started, protocol_version=11 Command: open "(IP)" port Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server Status: Waiting to retry... Status: Connecting to (IP)... Response: fzSftp started, protocol_version=11 Command: open "(IP)" (port) Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server

I have tried from another PC and have the same problem after update. I did not have this problem with the previous version of the client.

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,

Hi,

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

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

When using the file comparison feature, files are marked lightgreen when they in fact are not the same size and/or have different dates and times. Happens on different webhosters in different transfer modes SFTP, FTP and FTP/TLS. I realized this a few months ago, but thought the failure would be fixed shortly. Seems not.

FileZilla seems to check for updates even if I set the option to "Never" and it pops up "New version available" window at startup which is very annoying when you launch FZ to do something urgently.

FileZilla Client

Version: 3.65.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2023-07-10 Compiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110 Compiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type

Linked against:

wxWidgets: 3.2.1 SQLite: 3.39.4 GnuTLS: 3.8.0

Operating system:

Name: Windows 7 (build 7601, Service Pack 1), 64-bit edition Version: 6.1 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq lm

When navigating the main window of the client with tab and shift+tab, navigation seems to get stuck in the log. In other words, when keyboard focus is on the log, nothing happens when I press tab or shift+tab. I review the log often and I use a screen reader, so being able to use this kind of navigation is critical, and many screen reader users don't use a mouse at all. I discovered it is still possible to use the F6 key to move away from the log, which is a good workaround but not one that will be obvious to many. I do not know if this occurs on non-Windows operating systems but I did verify it on two Windows 10 machines. Marking high priority because even if it affects a small number of people, not being able to exit the log is arguably a blocker to being able to successfully use the client, and on the development side it seems like a small regression.

Original issue was that I had FileZilla displaying on 2nd monitor attached to my notebook. Thereafter, without 2nd monitor attached, FileZilla displayed at the extreme right edge of the screen and I was unable to drag it over.

This is the kind of situation a clean reinstall should resolve, but after uninstall, reboot, and reinstall, the problem persisted. I had to go through Windows registry and delete every FileZilla key I could find to resolve the issue.

Then it displayed correctly upon reinstall, but another problem appeared, as reported in bug #13048 "new Bug report". I was getting "error loading the transfer queue from "C:\User\patri\AppData\Roaming\FileZilla\queue.sqlite3".

This required uninstalling again, then deleting the FileZilla folder at C:\Users\userAppData\Roaming\.

After another uninstall, reboot, reinstall, finally everything working well.

Hello, I downloaded and installed the latest Windows 64-bit FileZilla v3.66.5 yesterday and have discovered the filezilla.exe executable contains no version information as existed in the previous versions Without this version information it is not possible to detect the correct version has been installed with automated deployment tools (such as SCCM or Intune) FileZilla.exe v3.66.5 properties will be attached as an image once the ticket has been created

Just downloaded FileZilla Client to my new computer and I'm seeing an issue I've never had before. In the "View" tab I have Tool bar and Quickconnect bar checked but they are not showing on my screen, so I have no way to connect to any servers. My computer and FileZilla are both totally up to date and I've played around with other settings. I've also looked through the forums and can't seem to find anything related to this. Any help is greatly appreciated!

If I export my connections list, which have some passwords stored, the XML generated has the passwords publicly displayed. I think there should be, at least, an obfuscation on that, since its easy to find out someones' password (which is obfuscated in the program) just by exporting its connections and looking through the XML.

Updates that show up even when "Never" is set in the drop down box. I do not need to be reminded for something that I do not need.

In relation to ticket 13070 being closed without resolution, I think it is time to say good-bye to filezilla.

I am on the paid MacOS client from the App Store.

FZ has worked perfectly for years, but broke after my upgrade to Sonoma 14.4. (I understand that this is a buggy release from Apple.)

As the attached image shows, neither file pane populates.

Both MacOS and FZ have been updated as of March 22 2024.

Please assist.

(BTW, I tried and failed to find similar tickets. I must say that the Trac site is poor.)

Not able to uninstall after upgraded to latest version Error says that I don’t have sufficient access to remove FileZilla (I am local administrator) Getting same error on both windows 10 and 11 Never had any issues with earlier versions of FileZilla

Installer was downloaded from https://filezilla-project.org/download.php?platform=win64