Custom Query (8170 matches)
Results (2501 - 2600 of 8170)
Ticket | Summary | Owner | Type | Priority | Component | Resolution | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
#11646 | List of websites to connect with, panel (left) menu, is gone. | Bug report | critical | FileZilla Server | duplicate | |||||||||||||||||||
Description |
In the new version, 3.34.0 on a MBP High Sierra. The left panel is gone in the sitesconnectingmenu. So there is only on connection possible. But which. In the version 3.33.0 the connecting panel shows on the left site a list of available sites. This panel is misformed/gone in version 3.34.0 on the MBP. Tested on a Sierra MBP gives the same result. So version 3.34.0 is not good. See images: Last version screendump, 3.33.0: http://chromosomal-conject.000webhostapp.com/version333panelleft.png Latest version screendump 3.34.0: http://chromosomal-conject.000webhostapp.com/version334panelleft.png The panel is broken/miformed in the latest version |
|||||||||||||||||||||||
#11653 | Cant connect to the server | Other | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
can you please provide me with host address |
|||||||||||||||||||||||
#11699 | Need to disable TLs 1.0 support on FTPS Server | Patch | high | FileZilla Server | outdated | |||||||||||||||||||
Description |
Hello Filezilla Team, I am using Filezilla Server with FTPS. I was working on our one of the servers to disable TLs 1.0 and fix other security issues. 1) I found that Filezilla FTP server(FTPS 990) supports TLs 1.0 even though I disabled on windows server 2012 R2. 2) I disabled "Secure Client-Initiated Renegotiation" on my server, but while connecting FTPS (port 990) it is supporting "Secure Client-Initiated Renegotiation". Is there any way to disabled TLs 1.0 support and "Secure Client-Initiated Renegotiation " in Filezilla server by means of configuration. Or can you provide a hotfix for the same in software for configuration? Thank you in advance. -- Regards, Jignesh Patel |
|||||||||||||||||||||||
#11702 | Filezilla Server service becomes unresponsive | Bug report | critical | FileZilla Server | rejected | |||||||||||||||||||
Description |
After an undetermined amount of time running Filezilla Server as a service on Windows 2008 R2 in a KVM VPS (QEMU 2.5+, 3 vCPUs, 64-bit OS), the service, without any clear reason, stops responding. The administration interface loses its connection, tries to re-establish and hangs on authentication. Trying to restart the service fails when it's in this state; the service is completely locked and cannot be stopped or restarted. Only a complete reboot of the server solves the problem. Initially when I ran into this problems I was running an older version of Filezilla Server (0.9.52, I believe) which has been running fine on this same machine for a very long time. I tried updating to 0.9.60-2 but it didn't solve the problem. No changes were made to this server apart from regular Windows Updates. Our FTP traffic on that particular machine is low, maybe a dozen or 2 users per day. 24 user accounts, 1 group. |
|||||||||||||||||||||||
#11709 | error disk full | Feature request | high | FileZilla Server | rejected | |||||||||||||||||||
Description |
getting error disk full I cleaned up my Mac files and its still staying them same thing. I can longer upload or transfer files please help. I just updated to new version still saying dick full. yourgodash@… |
|||||||||||||||||||||||
#11726 | Several questions about the Beta version of FileZilla server software | Feature request | high | FileZilla Server | invalid | |||||||||||||||||||
Description |
|
|||||||||||||||||||||||
#11862 | akrlsmu01lep05 access issue | Bug report | critical | FileZilla Server | invalid | |||||||||||||||||||
Description |
I am unable to access akrlsmu01lep05 on my computer. Filezilla shows me 'nacread01/RF:permission denied' error. However it works on other computer. I have contacted security access team and Samsung IT help desk team also. Both teams have told me that its Filezilla issue. I have uninstalled and installed file FileZilla many times. Software also updated.I have also check and verified the setting. Still I am having issues with akrlsmu01lep05. I am using version 3.39.0. Please help me to fix this issue. I shall be thankful to you. |
|||||||||||||||||||||||
#11909 | Alias Not Working for Shared OneDrive Folder | Bug report | critical | FileZilla Server | fixed | |||||||||||||||||||
Description |
When I goto Users -> Shared Folders and try to create an alias to this OneDrive folder, it allows me to make the entry, but it does NOT work when connecting remotely to the server: f:\OneDrive - company-tech.net When connecting remotely to the shared folder, it will display the folder contents, but it won't allow a file transfer and fails. Filezilla Server reports this error: 550 Could not open file for reading. But if I create the alias to this folder name, it will work: f:\OneDrive So I believe Filezilla Server is having an issue with the hyphen or period in the folder name. I would use the simpler folder name, however, OneDrive does not allow me to change the name of the folder as that belongs to the OneDrive account name, which in this case is "company-tech.net". |
|||||||||||||||||||||||
#11927 | Use more memory to reduce drive load | Feature request | low | FileZilla Server | rejected | |||||||||||||||||||
Description |
Currently when I am uploading a large file, FZ server seems to spin up the drive, load one chunk/packet into memory, close the file, upload the file and then repeat. It does this a 2~3 times a second until the file is finished uploading (perhaps several hours later). This is a waste of power and needlessly wears the drive (in the case of a physical drive). I would love if you could buffer significantly more (many megabytes) into memory to avoid this. But... obviously pretty low priority given that it sounds difficult to code for the amount of visible payoff. Think of it as helping the environment? For my case use alone it could allow at least one drive to be turned off/spun down several more hours a day. |
|||||||||||||||||||||||
#11985 | can anyone help me with this error | Bug report | normal | FileZilla Server | outdated | |||||||||||||||||||
Description |
Command: MLSD Error: GnuTLS error -110: The TLS connection was non-properly terminated. Status: Server did not properly shut down TLS connection Error: The data connection could not be established: ECONNABORTED - Connection aborted Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing |
|||||||||||||||||||||||
#12014 | Password and access level permission suggestion | Feature request | low | FileZilla Server | rejected | |||||||||||||||||||
Description |
I use FileZilla for uploading managing and files and folders in multiple sites on my laptop for multiple clients. Sometimes I leave my laptop at hotel or a coffee shop, etc I am suggesting to add an option to ask for password if FileZilla is inactive for certain time like 30 minutes. Admins can change or de-activate it at any time. Also, it would be good to add different access level for file and folder management & access like allowing multiple users accessing a site, yet each person only can access and manage certain file and folders. It would be a great security resource for larger projects. Thx, Matt |
|||||||||||||||||||||||
#12045 | Data connection TLS warning: SSL3 alert write: fatal: bad record mac | Bug report | normal | FileZilla Server | outdated | |||||||||||||||||||
Description |
All of a sudden I start seeing this error in the log and the connections are being dropped: Data connection TLS warning: SSL3 alert write: fatal: bad record mac The only major change was the installation of the regular Windows updates the day before. I've updated to the latest version 0.9.60 but that also has the same problem. This was previously reported in tickets #8771 and #4626 but it looks like we have something similar again. |
|||||||||||||||||||||||
#12197 | Error | Other | low | FileZilla Server | invalid | |||||||||||||||||||
Description |
Tengo un servidor de minecraft de Box To play. La app de FileZilla me da un error:Error: No se pudo conectar al servidor Estado: Esperando para reintentar... Lleva 1h para reintentar. ¿Que puedo hacer para que funcione? |
|||||||||||||||||||||||
#12261 | ftp user created by API is disabled by default | Bug report | high | FileZilla Server | rejected | |||||||||||||||||||
Description |
In Filezilla server version 0.9.60 When creating a new user by Miracle.FileZilla.Api the user is registered by default as disabled + ForceSSL Even though in the server interface they appear as enabled and without SSL but in .xml file these users are registered with different values. Just after clicking on the user and then closing the interface with OK button the parameters as displayed are updated in .xml file I had to explicitly add these parameters when calling the api. I could not find where these default values are configured. |
|||||||||||||||||||||||
#12286 | Clamd Files? | Bug report | high | FileZilla Server | rejected | |||||||||||||||||||
Description |
A new file has been added to all of my websites on the server side called "clamd". Has this file been added by Filezilla, or have I been hacked? I removed the file from each website and changed my password, but it has reappeared, so I wanted to check with your company to see if it has come from you before I figure out what to do next. |
|||||||||||||||||||||||
#12309 | Unable to connect to FileZilla | Bug report | critical | FileZilla Server | worksforme | |||||||||||||||||||
Description |
Hi Team, I am unable to connect to FileZilla. I am getting error. Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server |
|||||||||||||||||||||||
#12340 | Cannot Login Anymore | Other | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
Early last week, I started getting an error and I could not login to my accound. I have been working with my hosting company and still can't figure out what the problem is. Here is the current error that I'm seeing: Command: PWD Response: 257 "/" is your current location Command: TYPE I Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (212,16,184,190,214,132) Command: MLSD Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing Is there any way that you can help me? I have spent 5 hours now talking with tech support and have made zero progress. My FileZilla version is the latest one. |
|||||||||||||||||||||||
#12401 | 421 Could not create socket error | Other | high | FileZilla Server | worksforme | |||||||||||||||||||
Description |
Dear Team, We are using Filezilla FTP server on Passive mode with one static IP on the server. Actually we are facing an issue "421 Could not create socket" error. Kindly let us know any solution to resolve this issue. |
|||||||||||||||||||||||
#12402 | Critical Error | Bug report | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
Resolving address of private.djzone.me Status: Connecting to 212.32.241.214:21... Status: Connection established, waiting for welcome message... Response: 530 Sorry, the maximum number of connections (5) from your host are already connected. Error: Critical error: Could not connect to server |
|||||||||||||||||||||||
#12486 | 1.0.0-rc2 Log Files | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
1) Issue 1 I can not read log files created by Filezilla Server version 1.0.0-rc2. I have unsufficient permissions for log files, even as an admin. Not even rotated logs. It appears that log files do not inherit permissions from Logs-folder, they have their own ambiguous permissions. 2) Where does server store server settings file? 3) Log level explanations needed E.g. Log level 3: What is logged and what is not logged? |
|||||||||||||||||||||||
#12503 | 550 delete error when trying to delete config file | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
I am trying to remove a folder called "DungeonCrawl" from the config directory for my server. It contains a file named "config.json" which I am unable to delete. I would like to remove this file from the server. Every time I try, I get this response: Command: DELE config.json Response: 550 Delete operation failed. Thank you. |
|||||||||||||||||||||||
#12532 | The TLS connection was non-properly terminated | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
When I connect to Filezilla Server using Filezilla Client and then disconnect, there is the following error (IP address and username obscured) 2021-09-21T14:01:06.306Z !! [FTP Session 653 192.168.XXX.XXX XXXX] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated. 2021-09-21T14:01:06.306Z == [FTP Session 653 192.168.XXX.XXX XXXX] Client did not properly shut down TLS connection 2021-09-21T14:01:06.306Z !! [FTP Session 653 192.168.XXX.XXX XXXX] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted. 2021-09-21T14:01:06.306Z !! [FTP Server] Session ended with error from source 0. Reason: ECONNABORTED - Connection aborted. FileZilla Server versio 1.0.1 FileZilla Client version 3.55.1 Both running in Windows 10 Pro x64 version 10.0.19043.1237 I don't know whether this is a bug in server or client, I just reported it for the server. |
|||||||||||||||||||||||
#12542 | Critical error: Could not connect to server | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
I am unable to connect to the server. Commands are; Command: PASS * Response: 503 Bad sequence of commands Error: Critical error: Could not connect to server Status: Disconnected from server Status: Resolving address of mars.securejgs.net Status: Connecting to 137.117.144.181:21... Status: Connection established, waiting for welcome message... Status: Insecure server, it does not support FTP over TLS. Command: USER jgftpMars Response: 331 Password required Command: PASS * Response: 503 Bad sequence of commands Error: Critical error: Could not connect to server |
|||||||||||||||||||||||
#12544 | hard crash - Faulting module name: libstdc++-6.dll | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
The filezilla logfile is empty, all i have is this in the windows eventlog: Faulting application name: filezilla-server.exe, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: libstdc++-6.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x000000000001f70a Faulting process id: 0x5f8 Faulting application start time: 0x01d7b11f4c9119a6 Faulting application path: C:\Program Files\FileZilla Server\filezilla-server.exe Faulting module path: C:\Program Files\FileZilla Server\libstdc++-6.dll Report Id: e5e5db18-1fa7-11ec-8123-0026824f9497 Faulting package full name: Faulting package-relative application ID: |
|||||||||||||||||||||||
#12547 | New Server setting SMB path | Feature request | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
With New FileZilla Server 1.0.1 want to setting " \ \IP\shareFolderName\path" to Native path, but return Error Message "Path must be absolute". I shotdown the server, and modify "users.xml" in AppData, then restart server, the SMB path is work correctly. Can fix the warning message and SMB path is ok in interface? |
|||||||||||||||||||||||
#12548 | Cannot connect to my product account via 43 port using the "Quick Connect" | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
We cannot connect to our product via 43 port using the "Quick Connect" in the Filezilla with correct credentials. Note! We can connect with the same credentials using the Site Manager. |
|||||||||||||||||||||||
#12558 | Re: Files fail to upload. The server shows a folder with 2 dots after it Empty Directory Listing | Bug report | high | FileZilla Server | invalid | |||||||||||||||||||
Description |
Reporting a Bug I use FZ to upload files to 3 websites. 2 of the sites are fine in Filezilla but the 3rd website is experiencing problems when uploading to the remote server. Files fail to upload. The server shows a folder with 2 dots after it saying Empty Directory Listing Upload of files now fails. I get the message, Transfers Finished “All transfers have finished 1 file could not be transferred” Example 1 Command: CWD /htdocs Response: 250 OK. Current directory is /htdocs Command: TYPE I Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (213,171,193,5,32,7) Command: STOR sean courtney berwick.jpg Response: 553-Can't open that file: Invalid argument Response: 553 Rename/move failure: No such file or directory Error: Critical file transfer error all i get in the server window is a folder with 2 dots after it and a note saying "Empty Directory Listing" Here is another example: - Example 2 I tried to upload a jpg called “Odsal Bulletin” it failed saying: - Command: STOR odsal bulletin.jpg Response: 553 Rename/move failure: Success Error: Critical file transfer error Status: Disconnected from server The FZ local and remote server windows show the following:- see file attached[[Image] 1jpeg attached The 2 examples shown above returned different responses but both ended with the same result Error: Critical file transfer error and the Empty directory listing message in the remote server window with the folder and 2 dots. Example 3 I tried sending 3 files up but FileZilla said: - Command: STOR odsal bulletin.jpg Response: 553-Can't check for file existence: No such file or directory Response: 553 Rename/move failure: No such file or directory Error: Critical file transfer error I tried the Zilezilla Client Support forum and got the following answer from an apparent expert called BOCO Re: Files fail to upload. The server shows a folder with 2 dots after it Looks like the server is on the fritz. It responds to the upload command with error messages. Code: Select all Command: STOR sean courtney berwick.jpg Response: 553-Can't open that file: Invalid argument Response: 553 Rename/move failure: No such file or directory That's a case for the server support. You need to send a bug report their way. From John Skinner Email jskinner06@… Date 16/10/2021 |
|||||||||||||||||||||||
#12570 | changed behavior RETR on nonexisting file | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
In FileZilla Server 1.1.0 the behavior changed if a client sends an RETR for a nonexistant file. behavior prior to version 1.1.0: RETR file_that_does_not_exist 550 No such file behavior in version 1.1.0: RETR file_that_does_not_exist 150 Starting data transfer. 425 Error reading from file: 5 this is a big problem, because our clients (not our software) make RETR until a service on that server created this file. with the new responses the clients send a quit after they get the 425 |
|||||||||||||||||||||||
#12591 | Filezilla returns with "504 UTF8 mode cannot be disabled" when sending an "OPTS MLST type;size;modify;perm" | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
My FTP-client is trying to connect to a FileZilla server 1.0.1 that is not under my control and runs into trouble when trying to find out if MLSD/MLST is supported by the server (this is done because there are servers out there announcing support in FEAT but actually can't). Here is a snippet from the trace: *** Opened trace file at Wed Nov 24 13:06:12 CET 2021 <-- 220-FileZilla Server 1.0.1 <-- 220 Please visit https://filezilla-project.org/ [...] Check UTF-8 support ---> FEAT <-- 211-Features: <-- MDTM <-- REST STREAM <-- SIZE <-- MLST type*;size*;modify*;perm*; <-- MLSD <-- AUTH SSL <-- AUTH TLS <-- PROT <-- PBSZ <-- UTF8 <-- TVFS <-- EPSV <-- EPRT <-- MFMT <-- 211 End Trying to switch to UTF-8 for control channel ---> OPTS UTF8 ON <-- 202 UTF8 mode is always enabled. No need to send this command Switch control channel to UTF-8 Check support for MLST/MLSD MLST support is announced in features. Trying to set info-parts ---> OPTS MLST type;size;modify;perm <-- 504 UTF8 mode cannot be disabled Server answered MLST option request with an error, disabling feature ---> SYST <-- 215 UNIX emulated by FileZilla. The 504-answer lets the client fall back to use NLST which fails leading to a non-interop situation: ---> NLST * <-- 450 No such file So FileZilla is actually incapable of handling MLST and the error-message is wrong or there is some race condition leading to a 504 if an "OPTS UTF8 ON" is sent and another OPTS being followed directly afterwards. Version 1.1.0 seems to have the same problem (the trace is done with 1.0.1 on the other side) |
|||||||||||||||||||||||
#12593 | pb caractère générique * et ? avec la commande mget avec la version 1.1.0 | Bug report | normal | FileZilla Server | wontfix | |||||||||||||||||||
Description |
pb caractère générique * et ? avec la commande mget Depuis un client FTP sur Microsoft Windows server 2012 vers un serveur FTP FileZilla Version 1.1.0 sous Windows server 2012 lors de l'éxcution de la commande mget te*.txt j'obtiens l'erreur suivante :
425 Error reading from file: 5 |
|||||||||||||||||||||||
#12598 | Critical error: Could not connect to server | Bug report | normal | FileZilla Server | outdated | |||||||||||||||||||
Description |
When trying to connect to the server, I receive the following error: "Critical error: Could not connect to server" |
|||||||||||||||||||||||
#12611 | Not able to access folder shared via Filezilla | Bug report | normal | FileZilla Server | duplicate | |||||||||||||||||||
Description |
Hi Team, We have shared some file/folder via Filezilla to our clients but some of them are getting permission issue. Can we get assistance for same. |
|||||||||||||||||||||||
#12615 | Feature Request: provide a milllisecond delay parameter to session termination after 'Goodbye.' | Feature request | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
We have a contact using a 'slow' system that sends us small EDI files and after our upgrade to 1.1.0 started to received errors at the end of the session. We suspect that during the session termination protocol Filezilla closes the socket quickly - creating a socket termination error on their side because they are still processing the 'Goodbye.' acknowledgement Would you please consider adding a timeout value in MS (up to say, 5000 or more) in the configuration to allow for the client to process and disconnect from their side prior to the session destroy? Everything still works, but it generates a non-critical error for each session Thanks 2021-12-23T18:45:25.704Z >> [FTP Session 858 198.162.220.218 wfm_prod] QUIT 2021-12-23T18:45:25.704Z << [FTP Session 858 198.162.220.218 wfm_prod] 200 Goodbye.
2021-12-23T18:45:25.704Z II [FTP Session 858 198.162.220.218] Session 0x2d44db7560 with ID 858 destroyed. 2021-12-23T18:47:39.812Z II [FTP Session 859 198.162.220.218] Session 0x2d44db7560 with ID 859 created. |
|||||||||||||||||||||||
#12617 | Server version 1.1.0 - 550 Couldn't open the file or directory | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
It seems as though updating from 1.0.1 to 1.1.0 has given me this bug If I make a user, make a group for that user, then mount a drive as /group it will receive this error The only way it works is if something in the group is mounted as "/" Workaround seems to be to mount an empty folder as "/" then I can mount each folder Is there something wrong with the way I'm doing things or is this a bug? |
|||||||||||||||||||||||
#12621 | Not able to access folder shared via Filezilla | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
We have shared some folder using FileZilla server to our client , so that they can have access to the folder. However, the client is getting an error(Screenshot attached). Using latest filezilla version. |
|||||||||||||||||||||||
#12631 | images will not upload | Bug report | critical | FileZilla Server | outdated | |||||||||||||||||||
Description |
I am logged in, checked to make sure that the program was connected. made a new directory in public_html called image-files dragged the images from the left pane to the right pane. Would not dray. Then deleted failed attempts 3 times and still cannot drag the files into that folder. Please help. Thank you, Madeline PS: I don't know what how to determine the information you want: component version, operating system version. I am using a PC if that helps. |
|||||||||||||||||||||||
#12637 | Entry "has empty native path and no mount nodes: this should never happen... | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
Error occurs when trying to perform a file transfer from Rebex C# emdedded client using FTP over TLS protocol. Command prior to the error is "MLSD." After error message is "550 Couldn't open the file or directory. No logs were created by Filezilla to post. Embedded client error when trying to transfer the file was "15:52:59.656 Error Info: Rebex.Net.FtpException: Couldn't open the file or directory (550)." Both a virtual and Native path were entered in the Users section - that do exist with full control to the user logging into via the FTP client. |
|||||||||||||||||||||||
#12640 | Error connecting to server | Bug report | critical | FileZilla Server | rejected | |||||||||||||||||||
Description |
hello for some reason when i try to connect to my dayz server it says my ip is banned i have had this happen before trying to connect but then later it let me just trying to figure out why it keeps doing this |
|||||||||||||||||||||||
#12644 | Support LIST -a | Feature request | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
Hello, When using curlftpfs or gio (gnome library to access ftp) to connect to a FileZilla Server running on Windows they fail to list the contents of any directory because they use the 'LIST -a' command which is not accepted by the server. Is it possible to just ignore the non-standard '-a' flag and the command to behave just like regular 'LIST' ? Best regards, Hristo Stefanov |
|||||||||||||||||||||||
#12656 | localhost | Bug report | normal | FileZilla Server | invalid | |||||||||||||||||||
Description |
www.localhost.com
|
|||||||||||||||||||||||
#12661 | LIST * -> 450 Couldn't open the file or directory | Bug report | high | FileZilla Server | invalid | |||||||||||||||||||
Description |
After the upgrade from FileZilla Server 0.9.60 to 1.2.0 my FTP client can not list an existing folder. With old FileZilla Server version it works. This bug breaks our automation processes. Please fix it. You find the error 450 in the logs: 2022-02-12T15:50:10.322Z II [FTP Session 12 10.115.89.8] Session 0x17dc9d9d4c0 with ID 12 created. 2022-02-12T15:50:10.373Z >> [FTP Session 12 10.115.89.8] AUTH TLS 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] securer(1) ENTERING state = 0 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] calling tls_layer_->set_certificate_file("C:\Program Files (x86)\FileZilla Server\certificate-2020.crt", "C:\Program Files (x86)\FileZilla Server\certificate-2020.crt", "****") 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] securer(1) EXITING state = 1 2022-02-12T15:50:10.373Z << [FTP Session 12 10.115.89.8] 234 Using authentication type TLS. 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] ~securer(1) ENTERING state = 1 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] calling tls_layer_->set_alpn("ftp") 2022-02-12T15:50:10.373Z VV [FTP Session 12 10.115.89.8] tls_layer_impl::server_handshake() 2022-02-12T15:50:10.373Z VV [FTP Session 12 10.115.89.8] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] ~securer(1) EXITING state = 2 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] tls_layer_impl::on_send() 2022-02-12T15:50:10.373Z VV [FTP Session 12 10.115.89.8] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] tls_layer_impl::on_read() 2022-02-12T15:50:10.373Z VV [FTP Session 12 10.115.89.8] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Received CLIENT HELLO 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Processed CLIENT HELLO 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: About to send SERVER HELLO 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Sent SERVER HELLO 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: About to send CERTIFICATE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Sent CERTIFICATE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: About to send SERVER KEY EXCHANGE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Sent SERVER KEY EXCHANGE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: About to send SERVER HELLO DONE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Sent SERVER HELLO DONE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] tls_layer_impl::on_read() 2022-02-12T15:50:10.373Z VV [FTP Session 12 10.115.89.8] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Received CLIENT KEY EXCHANGE 2022-02-12T15:50:10.373Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Processed CLIENT KEY EXCHANGE 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] tls_layer_impl::on_read() 2022-02-12T15:50:10.436Z VV [FTP Session 12 10.115.89.8] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Received FINISHED 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Processed FINISHED 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] TLS handshakep: About to send FINISHED 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] TLS handshakep: Sent FINISHED 2022-02-12T15:50:10.436Z II [FTP Session 12 10.115.89.8] TLS Handshake successful 2022-02-12T15:50:10.436Z II [FTP Session 12 10.115.89.8] Protocol: TLS1.2, Key exchange: ECDHE-SECP256R1-RSA-SHA512, Cipher: AES-256-CBC, MAC: SHA1 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] tls_layer_impl::on_read() 2022-02-12T15:50:10.436Z >> [FTP Session 12 10.115.89.8] USER my_user 2022-02-12T15:50:10.436Z << [FTP Session 12 10.115.89.8] 331 Please, specify the password. 2022-02-12T15:50:10.436Z DD [FTP Session 12 10.115.89.8] tls_layer_impl::on_read() 2022-02-12T15:50:10.436Z >> [FTP Session 12 10.115.89.8] PASS **** 2022-02-12T15:50:10.623Z DD [File-based Authenticator] authenticate: is_from_system: 0, impersonation_token: { username: "", home: "" } 2022-02-12T15:50:10.623Z << [FTP Session 12 10.115.89.8 my_user] 230 Login successful. 2022-02-12T15:50:10.623Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.623Z >> [FTP Session 12 10.115.89.8 my_user] PBSZ 0 2022-02-12T15:50:10.623Z << [FTP Session 12 10.115.89.8 my_user] 200 PBSZ=0 2022-02-12T15:50:10.623Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.623Z >> [FTP Session 12 10.115.89.8 my_user] PROT P 2022-02-12T15:50:10.623Z << [FTP Session 12 10.115.89.8 my_user] 200 Protection level set to P 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] SYST 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 215 UNIX emulated by FileZilla. 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] TYPE I 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 200 Type set to I 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] FEAT 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 211-Features: 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 211 End 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] PWD 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 257 "/" is current directory. 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] TYPE I 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 200 Type set to I 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] CWD /transfer/out 2022-02-12T15:50:10.639Z DD [File-based Authenticator/impersonator client, user: <not impersonating>] info(C:\transfer\out): result: 0 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 250 CWD command successful 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] PWD 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 257 "/transfer/out" is current directory. 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] SYST 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 215 UNIX emulated by FileZilla. 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] PASV 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] Trying: data_listen_socket_->listen(1, 0) 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 227 Entering Passive Mode (192,168,1,114,200,32) 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] LIST TEST*.txt 2022-02-12T15:50:10.639Z DD [File-based Authenticator/impersonator client, user: <not impersonating>] info(C:\transfer\out\TEST*.txt): result: 6 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 450 Couldn't open the file or directory 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] session::on_socket_event(): source = data listen, flag = 2, error = 0, state = -1 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] Client wants a secure data connection. 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] securer(1) ENTERING state = 0 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] calling tls_layer_->set_certificate_file("C:\Program Files (x86)\FileZilla Server\certificate-2020.crt", "C:\Program Files (x86)\FileZilla Server\certificate-2020.crt", "****") 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] securer(1) EXITING state = 1 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] Making the data connection secure. 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] ~securer(1) ENTERING state = 1 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::server_handshake() 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] ~securer(1) EXITING state = 2 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_send() 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] TLS handshakep: Received CLIENT HELLO 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] TLS handshakep: Processed CLIENT HELLO 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] TLS handshakep: About to send SERVER HELLO 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] TLS handshakep: Sent SERVER HELLO 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] TLS handshakep: About to send FINISHED 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] TLS handshakep: Sent FINISHED 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::continue_handshake() 2022-02-12T15:50:10.639Z DD [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::on_read() 2022-02-12T15:50:10.639Z >> [FTP Session 12 10.115.89.8 my_user] QUIT 2022-02-12T15:50:10.639Z << [FTP Session 12 10.115.89.8 my_user] 200 Goodbye. 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::shutdown() 2022-02-12T15:50:10.639Z VV [FTP Session 12 10.115.89.8 my_user] tls_layer_impl::continue_shutdown() 2022-02-12T15:50:10.639Z II [FTP Session 12 10.115.89.8] Session 0x17dc9d9d4c0 with ID 12 destroyed. 2022-02-12T15:47:23.467Z >> [FTP Session 11 10.115.89.8 my_user] LIST * 2022-02-12T15:47:23.467Z DD [File-based Authenticator/impersonator client, user: <not impersonating>] info(C:\transfer\out\*): result: 6 2022-02-12T15:47:23.467Z << [FTP Session 11 10.115.89.8 my_user] 450 Couldn't open the file or directory |
|||||||||||||||||||||||
#12664 | Can't get current version | Bug report | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
Have tried to download the current version numerous times and while the download shows up on my download list on the computer it continues to be stuck on version 46. I cannot get on the server. |
|||||||||||||||||||||||
#12676 | Compile Error | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
I want to compile FZ Server myself.But I got compile error,I think is easy to resolve,just lines of code maybe.But I am not a CPP developer,so I can not solve it. /bin/bash ../../libtool --tag=CXX --mode=compile g++ -std=c++17 -DHAVE_CONFIG_H -I. -I../../src -I/usr/local/include -I/usr/include/p11-kit-1 -fno-exceptions -g -O2 -MT acme/libfilezilla_common_la-client.lo -MD -MP -MF acme/.deps/libfilezilla_common_la-client.Tpo -c -o acme/libfilezilla_common_la-client.lo `test -f 'acme/client.cpp' || echo './'`acme/client.cpp libtool: compile: g++ -std=c++17 -DHAVE_CONFIG_H -I. -I../../src -I/usr/local/include -I/usr/include/p11-kit-1 -fno-exceptions -g -O2 -MT acme/libfilezilla_common_la-client.lo -MD -MP -MF acme/.deps/libfilezilla_common_la-client.Tpo -c acme/client.cpp -fPIC -DPIC -o acme/.libs/libfilezilla_common_la-client.o In file included from acme/../http/client.hpp:13, from acme/client.hpp:10, from acme/client.cpp:1: acme/../http/../util/options.hpp: In instantiation of ‘fz::util::options<Holder>::opt<Value>::opt(fz::util::options<Holder>::opt<U>&&) [with U = fz::util::options<fz::http::client::options, void, 18446744073709551615>::empty; Value = std::function<void(fz::http::response&&)>; Holder = fz::http::client::options]’: acme/../http/client.hpp:36:55: required from here acme/../http/../util/options.hpp:30:37: error: call of overloaded ‘function(std::remove_reference<fz::util::options<fz::http::client::options, void, 18446744073709551615>::empty&>::type)’ is ambiguous , holder_(std::move(rhs.holder_)) ^ In file included from /usr/include/c++/8/functional:59, from /usr/local/include/libfilezilla/thread.hpp:6, from /usr/local/include/libfilezilla/event_loop.hpp:8, from /usr/local/include/libfilezilla/event_handler.hpp:4, from /usr/local/include/libfilezilla/socket.hpp:13, from /usr/local/include/libfilezilla/tls_layer.hpp:8, from acme/client.hpp:8, from acme/client.cpp:1: |
|||||||||||||||||||||||
#12682 | 1.3.0 server crashes | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
Hi, while I can't repro on demand (yet), I am having server crashes. The error suggests it's a memory access violation (Sig[6].Value=c0000005) I was running a VERY old version of the server. I recently installed 1.3.0 and since I did, I get the same crashes on both servers. I am attaching the windows crash report. Happy to provide any more data that i can. Server : windows server 2022 standard ram: 8gig configured, utilization never jumps over 50% of the ram cpu: 4 cores When they crash, only a single client is connected, uploading via single thread. |
|||||||||||||||||||||||
#12685 | Could Not Connect To Server | Bug report | normal | FileZilla Server | outdated | |||||||||||||||||||
Description |
Tried multiple times to connect to the server and it keeps giving me an error |
|||||||||||||||||||||||
#12687 | Different behavior with wrong path input | Bug report | normal | FileZilla Server | invalid | |||||||||||||||||||
Description |
Recently one of our customers changed his servers and so we wanted to change from FileZilla Server Version 0.9.43 to 1.3.0, but we encountered a tricky behavior, which prevented that. He uses an old Software on Windows CE and this program transfer's files trough FTP, but we recently found out, that the path in the PUT Command is wrong. They use backslash \ instead of slash /. Example: PUT 250122033146874.bmp \unterschriften\250122033146874.bmp And here is the tricky part, with Version 0.9.43 it changes the backslash to slash according to the log and so the file transfer works. (000003)01.04.2022 14:33:17 - zmde ( )> CWD \unterschriften\ (000003)01.04.2022 14:33:17 - zmde ( )> 250 CWD successful. "/unterschriften" is current directory. (000003)01.04.2022 14:33:18 - zmde ( )> PASV (000003)01.04.2022 14:33:18 - zmde ( )> 227 Entering Passive Mode (10,207,102,20,192,16) (000003)01.04.2022 14:33:20 - zmde ( )> STOR 250122033146874.bmp (000003)01.04.2022 14:33:20 - zmde ( )> 150 Opening data channel for file upload to server of "/unterschriften/250122033146874.bmp" (000003)01.04.2022 14:33:22 - zmde ( )> 226 Successfully transferred "/unterschriften/250122033146874.bmp" (000003)01.04.2022 14:33:22 - zmde ( )> PASV (000003)01.04.2022 14:33:22 - zmde ( )> 227 Entering Passive Mode (10,207,102,20,192,17) (000003)01.04.2022 14:33:24 - zmde ( )> RETR \unterschriften\250122033146874.bmp (000003)01.04.2022 14:33:24 - zmde ( )> 150 Opening data channel for file download from server of "/unterschriften/250122033146874.bmp" (000003)01.04.2022 14:33:24 - zmde ( )> 226 Successfully transferred "/unterschriften/250122033146874.bmp" (000003)01.04.2022 14:33:32 - zmde ( )> QUIT (000003)01.04.2022 14:33:32 - zmde ( )> 221 Goodbye But with Version 1.3.0 we get Error 550 Invalid Filename, what's correct because the command itself is wrong. As we can't change the old software and we didn't found any configuration in the new Version to allow such a behavior, we changed back to Version 0.9.43. If it's a bug or a new feature I can't decide and I just wanted to let you know of this different behavior. |
|||||||||||||||||||||||
#12689 | FileZilla Server 1.3.0 no features reported after FEAT command | Bug report | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
When the client is asking for the supported features of the FTP server ( Command = FEAT ), the answer is : 211-Features: 211 End Please can you add at least the list of supported commands over here ? |
|||||||||||||||||||||||
#12713 | SSH Connection and Certificates | Other | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
How do setup certificates for SSH connection |
|||||||||||||||||||||||
#12716 | could not connect to server | Other | normal | FileZilla Server | rejected | |||||||||||||||||||
Description |
Good morning I am following all details from a Filezilla pdf to connect. protocol SFTP na-sftp.elekta.com after my windows ID and password But I am receiving a message authentication failed critical error could not connect to server Can I have some help please |
|||||||||||||||||||||||
#12732 | loungerie_6151427 | Feature request | high | FileZilla Server | invalid | |||||||||||||||||||
Description |
Usuário: 6151427 Não estamos conseguindo baixar os arquivos da GetNet pelo aplicativo Filezilla e precisamos de um suporte, poderiam nos ajudar? Por favor. |
|||||||||||||||||||||||
#12733 | loungerie_6151427 | Feature request | high | FileZilla Server | invalid | |||||||||||||||||||
Description |
Usuário: 6151427 Não estamos conseguindo baixar os arquivos da GetNet pelo aplicativo Filezilla e precisamos de um suporte, poderiam nos ajudar? Por favor. |
|||||||||||||||||||||||
#12734 | loungerie_6151427 | Feature request | high | FileZilla Server | invalid | |||||||||||||||||||
Description |
Usuário: 6151427 Não estamos conseguindo baixar os arquivos da GetNet pelo aplicativo Filezilla e precisamos de um suporte, poderiam nos ajudar? Por favor. |
|||||||||||||||||||||||
#12757 | Use the following host | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
In Filezilla server 1.5.1 the field called use the following host (leave empty to use the default one) doesn't appear to be working correctly. I believe that before version 1 that field was the Get External IP. When trying to setup a passive FTP session I get an error back that server sent an unrouteable address. It sends back an RFC1918 address. When I try to paste in the original http://ip.filezilla-project.org/ip.php I get connected but I get errors on the client that it cannot prepare for the data connection. If I enter in my dynamic DNS name in that field I get the same result. The only way to get it to work is to put in my public IP in that field which is a dynamic IP. When I go to http://ip.filezilla-project.org/ip.php I get an error NET::ERR_CERT_COMMON_NAME_INVALID You cannot visit ip.filezilla-project.org right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later. |
|||||||||||||||||||||||
#12769 | not connecting | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
Hi, Filezilla won't connect. I get "status:connecting to lime.myseedbox.site..." but it just stays there and doesn't connect. It has been doing this for 2 days. I am using the latest version. |
|||||||||||||||||||||||
#12786 | command ls -l not working since version 1.5.1 | Bug report | low | FileZilla Server | rejected | |||||||||||||||||||
Description |
Hello, Since version 1.5.1, the "ls -l" command no longer works. We have a program that uses the "ls -l" command to list files with creation date information. Can you correct this please? Do you need additional information? Best regards, |
|||||||||||||||||||||||
#12801 | The wildcard "*" with ls command does not working | Bug report | blocker | FileZilla Server | rejected | |||||||||||||||||||
Description |
Hello, Since the new version of FileZilla Server the wildcard does not working. Example : ls *.pdf Is it normal or intentional? If not can you fix it? If so, can you explain why? and what do you suggest as an alternative? |
|||||||||||||||||||||||
#12809 | Filezlilla server crashes Faulting module name: ntdll.dll | Bug report | normal | FileZilla Server | outdated | |||||||||||||||||||
Description |
HI support i I' am sturggling with random filezlilla crashes. Operating system: Winows server 2016. Filezilla server 1.5.1 (also 1.3) . It happend every 2 or 3 days . Windows event log: Faulting application name: filezilla-server.exe, version: 1.5.1.0, time stamp: 0x00000000 Faulting module name: ntdll.dll, version: 10.0.14393.0, time stamp: 0x578997b2 Exception code: 0xc0000005 Fault offset: 0x000000000002f21b Faulting process id: 0x4fac Faulting application start time: 0x01d8f4368a80e1b3 Faulting application path: C:\Program Files\FileZilla Server\filezilla-server.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 00a31ecc-071a-4fee-95d7-f3ff974af84a Faulting package full name: Faulting package-relative application ID: I've got also dump file if it helps. I would be grateful if someone could help Daniel |
|||||||||||||||||||||||
#12814 | FZ Server 1.5.1 Directory Listing fails | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
A client app submits "LIST SESS*.REQ". FZ 1.5.1 answers: "550 Couldn't open the file or directory". (there was a file SESS0099.REQ in the user's home-dir (Native path)). I tried to track the problem down using Sysinternals Procmon and compared it to FZ 0.9.60.2: obviously Fz 0.9.60.2 executes the "LIST SESS*.REQ" differently to FZ 1.5.1. (see attached files) Attached files should clarify the issue. |
|||||||||||||||||||||||
#12832 | FileZilla server cannot be compiled with libfilezilla 0.39.2 | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
FileZilla Server 1.6.1 fails to be compiled with libfilezilla version 0.39.2 (the latest available version). Compilation fails because the "fz::strtokenizer" function is missing from libfilezilla 0.39.2 sources. Should the libfilezilla version used to build the "official" FileZilla Server be also released? |
|||||||||||||||||||||||
#12846 | Wrong data returned (possibly after an ABOR command) | Bug report | high | FileZilla Server | fixed | |||||||||||||||||||
Description |
It appears that after an ABOR command, incorrect data may be returned. In my specific case, I was trying to download file chunks, and providing offsets to FileZilla. The first chunk returned (offset 0) is correct. However, subsequent downloads return incorrect data. This is the C# pseudocode used: [code] public async Task TestFileZilla() {
} code I asked the Rebex support staff to verify their library is issuing the correct calls, and this is their response: So this indeed looks like a FileZilla issue, and it occurs even when I use an offset of “1” every time. To rule out a client-side issue, I captured the FTP traffic using Wireshark and analyzed it. The control connection looks OK, with the client attempting to download the same file twice: TYPE I 200 Type set to I PASV 227 Entering Passive Mode (10,0,0,196,230,208) REST 1 350 Restarting at 1 RETR /incoming/Artifacts.zip 150 Starting data transfer. ABOR 426 Data connection closed; transfer aborted. 226 ABOR command successful. PASV 227 Entering Passive Mode (10,0,0,196,230,209) REST 1 350 Restarting at 1 RETR /incoming/Artifacts.zip 150 Starting data transfer. ABOR 426 Data connection closed; transfer aborted. 226 ABOR command successful. However, data that was transmitted over the second data connection is clearly wrong. Apparently, instead of sending file data that starts at offset 1, FileZilla sends data from seemingly semi-random offsets such as 0x40001 or 0xA0001. So interestingly, FileZilla got the lower 16 bits of the offset correctly, but then used wrong value for the next 16 bits. Out of interest, I added ftpClient.GetList() as the first call in your “for (var i = 0; i < 10; i++)“ loop, and the results were even weirder – on the second iteration, the server actually transmitted some part of Artifacts.zip data instead of the directory listing. Because I also had “ftpClient.LogWriter = new ConsoleLogWriter(LogLevel.Debug)“ in the code, this actually showed up like this:
2023-01-09 17:00:52.526 INFO Ftp(1)[1] Command: TYPE A
2023-01-09 17:00:52.527 INFO Ftp(1)[1] Response: 200 Type set to A
2023-01-09 17:00:52.527 INFO Ftp(1)[1] Command: PASV
2023-01-09 17:00:52.528 INFO Ftp(1)[1] Response: 227 Entering Passive Mode (10,0,0,196,236,89)
2023-01-09 17:00:52.528 INFO Ftp(1)[1] Command: REST 0
2023-01-09 17:00:52.529 INFO Ftp(1)[1] Response: 350 Restarting at 0
2023-01-09 17:00:52.529 DEBUG Ftp(1)[1] Info: Establishing data connection to 10.0.0.196:60505.
2023-01-09 17:00:52.530 DEBUG Ftp(1)[1] Proxy: Connecting to 10.0.0.196:60505 (no proxy).
2023-01-09 17:00:52.531 DEBUG Ftp(1)[1] Proxy: Connection established.
2023-01-09 17:00:52.535 DEBUG Ftp(1)[1] Info: Established data connection from 10.0.0.196:64571.
2023-01-09 17:00:52.535 INFO Ftp(1)[1] Command: MLSD
2023-01-09 17:00:52.536 INFO Ftp(1)[1] Response: 150 Starting data transfer.
2023-01-09 17:00:52.537 DEBUG Ftp(1)[1] Info: Data transfer started.
2023-01-09 17:00:52.537 INFO Ftp(1)[1] Response: 226 Operation successful
Q#D?G?+c?*9?Py?~??mEq?E+???e‼??(+W?F▼?G??t??_?X?♥????]&_?8????▲?♦uP?&u???¶♣Ow?S?h▲??E♂c??}I??↑j?L???♥?Y?ZM??1↑??w0h?♠8?‼?Y??G?w(?DCp??◄g?o???m?# ??r????i?⌂P So please do open a FileZilla ticket for this – it looks like something very wrong is going on at the server indeed! My guess is that it has something to do with “ABOR” command – apparently, although it does stop the current transfer (before all data has been transmitted), part of the remaining data remains in some buffer and is later sent via data connection belonging to a subsequent command. |
|||||||||||||||||||||||
#12870 | Autoban does not reset counter after successful login | Bug report | high | FileZilla Server | fixed | |||||||||||||||||||
Description |
The issue is in the SFTP Authentication. If someone wants to authenticate with a public key or a password, the Server logs at first a failed authentication and then a succesfull one. This example is with password authentication: <Date> Info [Type] Message <14-02-2023 11:10:13> SSH SFTP Session 224 * [Command] SSH User Authentication [type=4, user=*, service=ssh-connection] <14-02-2023 11:10:13> SSH SFTP Session 224 * [Command] SSH User Authentication [type=4, user=*, service=ssh-connection] <14-02-2023 11:10:13> SSH SFTP Session 224 * [Error] User authentication attempt failed [user=*] [next_types=0x1] [error=4] <14-02-2023 11:10:13> SSH SFTP Session 224 * [Command] SSH User Authentication [type=1, user=*, service=ssh-connection] <14-02-2023 11:10:13> SSH SFTP Session 224 * [Command] SSH User Authentication [type=1, user=*, service=ssh-connection] <14-02-2023 11:10:13> SSH SFTP Session 224 * * [Status] User authenticated successfully [user=*] If one uses a public key, it would be the same except the type is 3. This authentication attempt will count as one failed login attempt, even tho the auth ended beeing successful. Assuming that one configured AutoBan with 2 failed login attempts, its very likely that on the next Login Attempt (like uploading/downloading a File) will trigger AutoBan since the authentication will be the exact same. Therefore either an authentication attempt like this should either count as successfull or after a successfully login attempt it should reset the AutoBan Counter |
|||||||||||||||||||||||
#12873 | FileZilla won't upload files | Bug report | high | FileZilla Server | rejected | |||||||||||||||||||
Description |
I keep getting a 552 Disk Full error and says critical file transfer error. I've downloaded the newest version, restarted, tried on a different computer and I still keep getting this issue. However, if I go into my cpanel File Manager, I can upload it that way. Not sure exactly where this issue lies. |
|||||||||||||||||||||||
#12891 | Wrong answer on 'SIZE' command | Bug report | normal | FileZilla Server | outdated | |||||||||||||||||||
Description |
Hello, i have a CCTV system from TANTOS solutions with ability to upload files to FTP server when alarm triggers. I have own FileZilla FTP server with next parameters: OS: Windows 10 Pro (build 19044.2728) FileZilla: 0.9.41 beta I have separated account for my CCTV system with all permissions on its home directory. My CCTV recorder can connect to my FTP server successfully, but it can not upload files on it. When it tries to test connection i have following messags on logs: (001186)SUN 26.3.23 18:46:14 - (not logged in) (IP hidden)> Connected, sending welcome message... (001186)SUN 26.3.23 18:46:14 - (not logged in) (IP hidden)> USER login hidden (001186)SUN 26.3.23 18:46:14 - (not logged in) (IP hidden)> 331 Password required for login hidden (001186)SUN 26.3.23 18:46:14 - (not logged in) (IP hidden)> PASS * (001186)SUN 26.3.23 18:46:14 - login hidden (IP hidden)> 230 Logged on (001186)SUN 26.3.23 18:46:14 - login hidden (IP hidden)> PWD (001186)SUN 26.3.23 18:46:14 - login hidden (IP hidden)> 257 "/" is current directory. (001186)SUN 26.3.23 18:46:14 - login hidden (IP hidden)> QUIT (001186)SUN 26.3.23 18:46:14 - login hidden (IP hidden)> 221 Goodbye (001186)SUN 26.3.23 18:46:14 - login hidden (IP hidden)> disconnected. When my CCTV recorder tries to upload files i have following messages in logs: (001187)SUN 26.3.23 19:10:08 - (not logged in) (IP hidden)> Connected, sending welcome message... (001187)SUN 26.3.23 19:10:08 - (not logged in) (IP hidden)> USER login hidden (001187)SUN 26.3.23 19:10:08 - (not logged in) (IP hidden)> 331 Password required for login hidden (001187)SUN 26.3.23 19:10:08 - (not logged in) (IP hidden)> PASS * (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 230 Logged on (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> PWD (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 257 "/" is current directory. (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> CWD / (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 250 CWD successful. "/" is current directory. (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> CWD ./IP hidden/2023-03-26/03 (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 250 CWD successful. "/IP hidden/2023-03-26/03" is current directory. (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> size 03_A_20230326_190937.dav (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 550 File not found (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> TYPE I (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 200 Type set to I (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> PASV (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 227 Entering Passive Mode (IP hidden,236,205) As you can see the problem is in 550 response of FTP server because it can not return a size of file. (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> size 03_A_20230326_190937.dav (001187)SUN 26.3.23 19:10:08 - login hidden (IP hidden)> 550 File not found I have tested this behavior on other servers and it were succcessfull. The problem is only with FileZilla solution. Also i sent a support request to my CCTV system manufacturer and they says, that this issue in my FTP server software. |
|||||||||||||||||||||||
#12895 | purchase of Filezilla enterprise version | Other | low | FileZilla Server | invalid | |||||||||||||||||||
Description |
we need FTP server with more secured and various user level permissions, we require a below options.
If the above options are available with FileZilla enterprise, we are okay to purchase it. Do you have the trial version for the enterprise server? |
|||||||||||||||||||||||
#12934 | Issue in Windows-Installer V1.7.2 | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
Hello, there is a "major" bug in the Windows-Exe as describes as followed: We usally roll out updates while using the /S switch, which worked until 1.6.1 fine. But V1.7.2 has the issue to REMOVE the service so that the ftp-Server dowes not run any longer! While manuelly running the setup the service is recreated fine again. This might not be as wanted ;-) |
|||||||||||||||||||||||
#12945 | ssh-2.0-Filezilla_3.65.0 | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
<Date/Time> Info [Type] Message <10-07-2023 16:52:26> FTP Session 25 192.168.1.139 [Response] 220-FileZilla Server 1.7.2 <10-07-2023 16:52:26> FTP Session 25 192.168.1.139 [Response] 220-Please visit https://filezilla-project.org/ <10-07-2023 16:52:26> FTP Session 25 192.168.1.139 [Response] 220 Private Server <10-07-2023 16:52:26> FTP Session 25 192.168.1.139 [Command] SSH-2.0-FileZilla_3.65.0 <10-07-2023 16:52:26> FTP Session 25 192.168.1.139 [Response] 500 Wrong command. <Date/Time> Info [Type] Message <10-07-2023 16:53:11> FTP Session 26 192.168.1.139 [Error] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted. I'm using latest versions for both client(3.65.0) and server(1.7.2). What can be done to remedy this? FileZilla Client Version: 3.65.0 Build information:
Linked against:
Operating system:
|
|||||||||||||||||||||||
#12959 | "User is enabled" unticked - and the XML file proves - but user can still login | Bug report | normal | FileZilla Server | invalid | |||||||||||||||||||
Description |
I just wanted to disable an user to login in our FTP server. I've even checked the XML file if the user is set to "disabled". It is, but this configuration seems to be ignored. I've restarted the FTP server and the FileZilla Server service but I see on the interface and in the logs, that the user can still login. Is that maybe a bug? Best regards |
|||||||||||||||||||||||
#12970 | Server and File Zilla Upgrade | Other | high | FileZilla Server | rejected | |||||||||||||||||||
Description |
Previously, we had Version 0.9.41 beta installed on Windows Server 2008 R2 Enterprise OS. We are updating our Server to 2019 and have installed the 1.7.2 version of Filezilla. Some systems connecting to our server is having problems with commands. Previously, the system would allow you to setup the ability to Read/Write/Delete/Append for Files and also Create/Delete/List/+Subdirs for Directories. It seems as though they are allowed to create a new directory, and copy a file to it, but when it tries to access a file inside the new directory, it is giving permission error. The same scripts were running on the previous version, but seem to fail on the new version. Please help, as we must update our PROD server by Oct of 2023. We are currently having issues on a test server. 2023-08-23T19:15:00.412Z << [FTP Session 22892 10.0.248.11] 220-FileZilla Server 1.7.2 2023-08-23T19:15:00.412Z << [FTP Session 22892 10.0.248.11] 220-Please visit https://filezilla-project.org/ 2023-08-23T19:15:00.412Z << [FTP Session 22892 10.0.248.11] 220 Hello and Wecome to Thermo Fisher EDI System for ETO 2023-08-23T19:15:00.412Z >> [FTP Session 22892 10.0.248.11] USER ROCSAPFTP 2023-08-23T19:15:00.412Z << [FTP Session 22892 10.0.248.11] 331 Please, specify the password. 2023-08-23T19:15:00.412Z >> [FTP Session 22892 10.0.248.11] PASS 2023-08-23T19:15:00.459Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 230 Login successful. 2023-08-23T19:15:00.459Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] SYST 2023-08-23T19:15:00.459Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 215 UNIX emulated by FileZilla. 2023-08-23T19:15:00.459Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RNFR Inbound 2023-08-23T19:15:00.459Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 350 Directory exists, ready for destination name. 2023-08-23T19:15:00.459Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RNTO Intemp 2023-08-23T19:15:00.459Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Permission denied 2023-08-23T19:15:00.459Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] MKD Inbound 2023-08-23T19:15:00.459Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 257 "/Inbound" created successfully. 2023-08-23T19:15:00.459Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] CWD /Intemp 2023-08-23T19:15:00.459Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 CWD command successful 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] CDUP 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 CDUP command successful 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RMD Intemp 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RNFR Status 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 350 Directory exists, ready for destination name. 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RNTO Stattemp 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 File or directory renamed successfully. 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] MKD Status 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 257 "/Status" created successfully. 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] CWD /Stattemp 2023-08-23T19:15:00.475Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 CWD command successful 2023-08-23T19:15:00.475Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] CDUP 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 CDUP command successful 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RMD Stattemp 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 Directory deleted successfully. 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RNFR LSB_Inbound 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 350 Directory exists, ready for destination name. 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RNTO LSB_Intemp 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Permission denied 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] MKD /LSB_Inbound 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 257 "/LSB_Inbound" created successfully. 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] CWD /LSB_Intemp 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 CWD command successful 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.490Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.490Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.506Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.506Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:15:00.506Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:15:00.506Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.506Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] CDUP 2023-08-23T19:15:00.506Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 250 CDUP command successful 2023-08-23T19:15:00.506Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] RMD /LSB_Intemp 2023-08-23T19:15:00.506Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:15:00.506Z >> [FTP Session 22892 10.0.248.11 ROCSAPFTP] QUIT 2023-08-23T19:15:00.506Z << [FTP Session 22892 10.0.248.11 ROCSAPFTP] 221 Goodbye. 2023-08-23T19:15:00.506Z == [FTP Server] Session 22892 ended gracefully. 2023-08-23T19:25:00.633Z << [FTP Session 23862 10.0.248.11] 220-FileZilla Server 1.7.2 2023-08-23T19:25:00.633Z << [FTP Session 23862 10.0.248.11] 220-Please visit https://filezilla-project.org/ 2023-08-23T19:25:00.633Z << [FTP Session 23862 10.0.248.11] 220 Hello and Wecome to Thermo Fisher EDI System for ETO 2023-08-23T19:25:00.633Z >> [FTP Session 23862 10.0.248.11] USER ROCSAPFTP 2023-08-23T19:25:00.633Z << [FTP Session 23862 10.0.248.11] 331 Please, specify the password. 2023-08-23T19:25:00.633Z >> [FTP Session 23862 10.0.248.11] PASS 2023-08-23T19:25:00.696Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 230 Login successful. 2023-08-23T19:25:00.696Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] SYST 2023-08-23T19:25:00.696Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 215 UNIX emulated by FileZilla. 2023-08-23T19:25:00.696Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RNFR Inbound 2023-08-23T19:25:00.696Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 350 Directory exists, ready for destination name. 2023-08-23T19:25:00.696Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RNTO Intemp 2023-08-23T19:25:00.696Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 File or directory renamed successfully. 2023-08-23T19:25:00.696Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] MKD Inbound 2023-08-23T19:25:00.711Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 257 "/Inbound" created successfully. 2023-08-23T19:25:00.711Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] CWD /Intemp 2023-08-23T19:25:00.711Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 CWD command successful 2023-08-23T19:25:00.711Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.711Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.711Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.711Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.711Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.711Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.711Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] CDUP 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 CDUP command successful 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RMD Intemp 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RNFR Status 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 350 Directory exists, ready for destination name. 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RNTO Stattemp 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 File or directory renamed successfully. 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] MKD Status 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 257 "/Status" created successfully. 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] CWD /Stattemp 2023-08-23T19:25:00.727Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 CWD command successful 2023-08-23T19:25:00.727Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] CDUP 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 CDUP command successful 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RMD Stattemp 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 Directory deleted successfully. 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RNFR LSB_Inbound 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 350 Directory exists, ready for destination name. 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RNTO LSB_Intemp 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 File or directory renamed successfully. 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] MKD /LSB_Inbound 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 257 "/LSB_Inbound" created successfully. 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] CWD /LSB_Intemp 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 CWD command successful 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] EPSV
2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] NLST * 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] CDUP 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 250 CDUP command successful 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] RMD /LSB_Intemp 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 550 Couldn't open the file or directory 2023-08-23T19:25:00.742Z >> [FTP Session 23862 10.0.248.11 ROCSAPFTP] QUIT 2023-08-23T19:25:00.742Z << [FTP Session 23862 10.0.248.11 ROCSAPFTP] 221 Goodbye. 2023-08-23T19:25:00.742Z == [FTP Server] Session 23862 ended gracefully. |
|||||||||||||||||||||||
#12976 | SFTP Server support with new 1.8.0-rc1 ? | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
Hi, Into the recent FileZilla Server 1.8.0-rc1 changelog, I read : "UI: fixed bug that made it impossible to switch the type of a listener from FTP to SFTP." So, there is a SFTP server (SSH FTP) ? It can really interest me. If not (mistake into the changelog), please, is this planned ? Thank you so much, Maxime |
|||||||||||||||||||||||
#13012 | Linux : User's "mount point" location problem | Bug report | normal | FileZilla Server | wontfix | |||||||||||||||||||
Description |
Arch Linux + GNOME. Filezilla Server : 1.7.3 (AUR) Bug Menu : Server - Configure... - Right management - Users - General - Mount points. I can't view Mount point location. So I can't add/remove Mount point location. I'll attach screenshot file if I can. Thank you. |
|||||||||||||||||||||||
#13027 | Max 1000 items in a folder | Bug report | normal | FileZilla Server | worksforme | |||||||||||||||||||
Description |
Greetings! There is a situation that item tree folder in your FileZilla shows ONLY 1000 items. I need much more! Please, correct. My hosting company allaws to use 3000 it. in a folder!!!! |
|||||||||||||||||||||||
#13028 | Data peer IP error which aborts the data connection - reproducible with AWS EC2 | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
This error message came up for me today after upgrading to the latest FileZilla Server. <Date/Time> Info [Type] Message <08-12-2023 07:15:38> FTP Session 3 34.xxx.xxx.12 (snip username) [Error] Data peer IP [172.xx.xx.xx] differs from control peer IP [34.xxx.xxx.12]: this shouldn't happen, aborting the data connection. How to reproduce this error You need two AWS EC2 machines which happen to be in the same region. Put FileZilla server on one of them. Put ncFtpPut client on the other one. ( Download the client from https://www.ncftp.com/ncftp/ ) When ncFtpPut tries to connect, probably due to some AWS routing optimizations, it comes through using the private IPv4 of the client machine instead of using the public IPv4. This accounts for the difference. Hope that helps. |
|||||||||||||||||||||||
#13045 | bug:the virtual path is not valid | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
In the "Groups" or "Users" setting, the "virtual path" entering "/02市场拓展部" results in an error message: "the virtual path is not valid. Character '\' is not allowed in the path..." preventing further progress. However, entering "/02市场拓展部s" is succeed. |
|||||||||||||||||||||||
#13064 | filezilla-server.exe service stop automatic. | Bug report | normal | FileZilla Server | fixed | |||||||||||||||||||
Description |
Dear Team, We observed that filezilla-server.exe service stop automatically. end log found Faulting application name: filezilla-server.exe, version: 1.7.3.0, time stamp: 0x64ff8683 Faulting module name: libfilezilla-40.dll, version: 0.44.0.0, time stamp: 0x64ff8683 Exception code: 0xc0000005 Fault offset: 0x000000000004a7c1 Faulting process id: 0xa64 Faulting application start time: 0x01da2cb4c4df6088 Faulting application path: C:\Program Files\FileZilla Server\filezilla-server.exe Faulting module path: C:\Program Files\FileZilla Server\libfilezilla-40.dll Report Id: 2f63b6da-c0b7-43b1-abbc-67274b7db30d Faulting package full name: Faulting package-relative application ID: Please help to resolve below issue. Regards Santosh Prasad 9971249710 |
|||||||||||||||||||||||
#195 | Changing netware servers (and downloading files) | Bug report | normal | FileZilla Client | rejected | |||||||||||||||||||
Description |
When logged into a netware server it is possible to also access other servers in the same tree. This is done with the command CD servername/volumename/directoryname/ etc. etc. Filezilla removes the first / and sends /servername/volumename/directoryname/ which of course fails. Some way to override the default behaviour so that the other servers can be accessed is required. |
|||||||||||||||||||||||
#230 | View / Edit | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
The menu option "View / Edit" should use the windows explorer default editor if "File viewing / editing" doesn't have a program manually configured to view/edit the file... Thanks. |
|||||||||||||||||||||||
#366 | FTP upload to Xbox slow | Bug report | normal | FileZilla Client | outdated | |||||||||||||||||||
Description |
Using FileZilla 2.1.4b, I can FTP files to Xbox normallyat a high speed, like several Mbps. Upgrading to FileZilla 2.1.5 and higher (I tried the latest 2.1.8b) the FTP uploads slow down to around 20-70K/sec. FTP downloads to PC are fast and it is just the uploads that are slow in later versions. I am using EvolutionX and XBMP 2.4 as FTP server. |
|||||||||||||||||||||||
#461 | installer doesn't install to All Users profile | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
When installing FileZilla-2.2.0 (on a WinXP box) it offers no capability to install for "All Users", and instead unconditionally installs Start menu items in the current users' start menu (whether they be an administrator or not). FileZilla-2.1.7 had a similar bug. It installed to "All Users" but the permission of the files were set to be unreadable by anyone other than the user who installed them. |
|||||||||||||||||||||||
#524 | date parsing on LIST command | Bug report | low | FileZilla Client | rejected | |||||||||||||||||||
Description |
When the LIST command is responded to by an FTP server (as the result of getting the list of files in a directory), certian date formats are not parsed correctly: Example:
abort.txt is parsed correctly, but
is not parsed correctly. The end result is the file name is listed in the GUI as:
abort.txt" which make file tranfer impossible. |
|||||||||||||||||||||||
#779 | Local server destination problem | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
May I respectfully submit a possible bug?
Although you can navigate to a (Windows)
I installed 2.2.9 over 2.2.8 and so deleted/uninstalled everything and tried again. No joy. I'm not very sure but I think that this has worked fine in the past. best. Fantastic Application. Al. |
|||||||||||||||||||||||
#780 | Change password does not work in 2.2.9 | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
If I try to change password with server\change password reports that odl password is not correct. If I try chmod works fine. This is because Filezilla adds quote on begining and end of paasword phrase. Exp. chmod passold passnew - this is right, but filezilla sends to server chmod "passold" "passnew" - wrong. You have to sent without quotes. Then works. |
|||||||||||||||||||||||
#781 | leading blank in filename causes critical transfer error | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
when you have a leading blank in a filename, filezilla cannot download ist (i made this experience with files in a very long path) - i have the latest version 2.2.9 work around: manual editing of source filename in queue xml file solves the problem |
|||||||||||||||||||||||
#782 | Site Manager cannot use empty password in Filezilla 2.2.9 | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
In Site Manager, if you specify an ftp site and use 'Normal' Logontype and presses the 'Connect' button, the 'Enter your password' dialog box must use non-null (non-empty) password string, otherwise the 'OK' button will be greyed out and cannot complete the login process. |
|||||||||||||||||||||||
#784 | Permission Error | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Hi, I've found a bug while trying to transfer a file from a Solaris 8 system to a Win2k3 system (NTFS). I had no permission on the windows machine but FileZilla transfered the file anyway. When I looked into the transfered directory the file wasn't there although the FileZilla log indicated that the file transfer was completed successfully. When I tried it again it prompted me that the file is already there and would I like to override it - which can't be true (as you can rembere I don't have any writing permissions on the windows machine). Ronen. |
|||||||||||||||||||||||
#785 | no "@" in host adress ??? | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
i enjoied FileZilla untill today. i registerd webspace by a new provider. my ftp host is "blablabla@…". FileZilla is not able to connect to this host. unknown syntax is the error. he will axcept the @ only in use with "user:pass@". but that is not the way i need. maybe you can correct this in a newer version. thanks a lot for your good work !!! |
|||||||||||||||||||||||
#788 | Settings import does not work properly | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Hi, there is propably a bug in the import function. I noticed a few weeks ago in the .9 version that importing the ftp sites does not work if you import the settings right after it and then close the programm and reopen it. I thought i did somehthing wrong, but now i just installed version .10 and the same happend again. |
|||||||||||||||||||||||
#789 | Typo in uninstall dialog | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
When you uninstall FileZilla, a dialog is displayed that says: "Delete all Registry keys...(including Site Mannager..." Mannager should be spelled: Manager |
|||||||||||||||||||||||
#790 | FileZilla strips leading / character | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Novell's FTP server software allows one to access the files on ANY Novell file server in the directory tree, using this syntax: cwd server/volume/dir/subdir When I enter such a path in FileZilla (2.2.10), such as "admin/ groups/registrar", it strips the first '/' character, changing the string I entered to "/admin/groups/registrar", and as such returns a '550 invalid path' error. Another FTP client, NCFtp (www.ncftp.com) had the same issue a few versions back, but has since been fixed. WS_FTP on Windows, Fetch and Transmit on Mac OSX, and the command line FTP program on any Mac/Linux/Windows system all work correctly with this functionality and do not have this issue. Please take a look at it. We really like FileZilla, but with that problem accessing Novell's FTP server, we have to steer clear of it for now. I can provide a test account to our Novell server if you don't have one available to test against. Thanks! |
|||||||||||||||||||||||
#791 | filezilla 2.2.8d deletes config file when crashing | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
The other day i ran out of HD space. Filezilla was crashed . after reboot filezilla had erased my config file/replaced it with a new one. Im using filezilla 2.2.8d (can't dl the newest version). and windows xp sp 2 I lost all my logins... sigh... maybe a backup file should be created whenever a write lock is made on the config file? |
|||||||||||||||||||||||
#794 | SFTP download fails with "no such file or directory" | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
I have tried to get support for this at the forum, but no ideas. See the thread at: http://filezilla.sourceforge.net/forum/viewtopic.php? t=606&highlight=sftp The problem appears to be with SFTP in particular. The connection to the users home directory works fine, but issuing "download" in the home directory fails. Text from the thread: We are trying to pull files down to the client via Filezilla's SFTP client and we are having a problem. The server is OpenSSH 3.7.1p2. When doing view/edit or download all return the following output: Status: Starting download of /home/username/test.ksh Command: GET test.ksh C:\Documents and Settings\username.domain\Desktop\test.ksh FALSE Response: /home/usernametest.ksh: no such file or directory Error: Download failed It looks like the response is missing a / between the directory and the filename. Is this a known issue? FYI...I tried to do the same transfer with the PuTTy client directly with the same results. I have been successful with the ssh.com client and OpenSSH commandline client from UNIX. I am attaching a debug trace if it helps. This is hight priority for us as we can't donwload any files through SFTP using Filezilla. I have tested with the same results on Filezilla 2.2.8a through 2.2.10. The problem still exists. Cheers, Keehan P.S. From the thread...it is interesting to note the same problem directly in puTTY. Perhaps the problem is puTTY directly. |
|||||||||||||||||||||||
#796 | uploading files with name starting com1 | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
When trying to upload files that are named "com1.anything" the program show an error and doesn't upload nothing. |
|||||||||||||||||||||||
#802 | some files and folders do not display in solaris 5.8 | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
I have a problem with solaris 5.8 ftp server. Some files and folders do not display. I have been reviewing past versions and in the begining i have the same problem, but worst because i couldnt see the most of the files and folders in this operating system. I have no personal firewall. It is in the local network. and I have tried the passive option with no positive results. |
|||||||||||||||||||||||
#804 | Upload of modified file doesn't work for non-default program | Bug report | normal | FileZilla Client | outdated | |||||||||||||||||||
Description |
The capability to upload a modified file appears only to work for the default program to edit/view files. For example, I have my text editor as the default program. If I modify a .txt/.log/.ini file on the server, when I save and close it asks if I want to upload the modified file to the server. I also have an association for .xls files to excel. I am not prompted for the automatic upload if I change one of these files. If, however, I set Excel to be my default program and set up the .txt/.log/.ini files as non-default associations, the behavior is reversed. Excel files will prompt me for automatic upload when changed, but the text files will not. It just seems like it should work for all files, whether they are opened by the default view/edit program or not. Thanks, Sammy |
|||||||||||||||||||||||
#807 | "Use multiple connections"-setting | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
If you remove the hook in the menu "Queue"->"Use multiple connections" and enter the settings menu after it "Edit"->"Settings..."->"File transfere settings" the hook at "Use multiple connections to transfere files" is still there. If you click "ok" now, the hook in the menu will also be there again and the programm will use 2 connections again. |
|||||||||||||||||||||||
#817 | Slow local list view when network drive | Bug report | normal | FileZilla Client | wontfix | |||||||||||||||||||
Description |
The local list view is extremly slow when using a network drive. Switching between directories needs some 1-3 seconds, which is much slower than the remote side via FTP! I have this problem on a Windows XP SP2 while the network drive is a Linux samba share. Version FileZilla 2.2.10 (but I remember, it was that slow in many versions before) |
|||||||||||||||||||||||
#823 | Can't handle space at the end of the address | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Version 2.2.11 I copied and pasted a URL into the Address field but got a space at the end. FileZilla couldn't connect until the space was removed. |
|||||||||||||||||||||||
#824 | usernames with slash doesn't work | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Until now we used total commander for ftp uploads which works very good but Filezilla has become at least equal so we decided to change. After creating the ftp accounts we realized that filezilla can't handle usernames with slashes ("/") in it. We always get the server message "password or username wrong". The account works with the same config in Total Commander and in IE. Because of that we have to stay on Total Commander which isn't so good :) By the way thanks for your great work. cu Mokierer |
|||||||||||||||||||||||
#828 | Failure when trying to upload file | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Filezilla crashes when attempting to resume on server that has weird directory permissions, if i upload entire contents of directory, it eventually hangs after about 30 seconds. Bandwidth throttling is on, and server has wstrange permissions. NOt sure what other information I can obtain. Exception report created by FileZilla version 2.2.12 =================================================== System details: Operating System: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Processor Information: Vendor: GenuineIntel, Speed: 2399MHz, Type: Intel Pentium compatible, Number Of Processors: 1, Architecture: Intel, Level: Unknown 15, Stepping: 5-19 Memory Information: Memory Used 49%, Total Physical Memory 785904KB, Physical Memory Available 397976KB, Total Virtual Memory 2097024KB, Available Virtual Memory 2051428KB, Working Set Min: 200KB Max: 1380KB . Exception Details: Exception code: C0000005 ACCESS_VIOLATION |
|||||||||||||||||||||||
#829 | Application Error Event ID: 1000 | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 03/13/05 Time: 8:26:55 AM User: N/A Computer: 3ASFSHJ587RT562 Description: Faulting application filezilla.exe, version 2.2.12.100, faulting module filezilla.exe, version 2.2.12.100, fault address 0x0000166b. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 66 69 6c ure fil 0018: 65 7a 69 6c 6c 61 2e 65 ezilla.e 0020: 78 65 20 32 2e 32 2e 31 xe 2.2.1 0028: 32 2e 31 30 30 20 69 6e 2.100 in 0030: 20 66 69 6c 65 7a 69 6c filezil 0038: 6c 61 2e 65 78 65 20 32 la.exe 2 0040: 2e 32 2e 31 32 2e 31 30 .2.12.10 0048: 30 20 61 74 20 6f 66 66 0 at off 0050: 73 65 74 20 30 30 30 30 set 0000 0058: 31 36 36 62 0d 0a 166b.. |
|||||||||||||||||||||||
#832 | Cannot abort pauzed queue item | Bug report | normal | FileZilla Client | ||||||||||||||||||||
Description |
When trying to abort an upload or download which is paused, nothing happens, after resuming the download/upload, aborting is possible again. Looks like a small problem to me good luck bugsmashing :) |