Custom Query (8025 matches)


Show under each result:

Results (313 - 315 of 8025)

Ticket Resolution Summary Owner Reporter
#4046 invalid Error on upload to our web servers John S.

I love your product and have recently had this issue:

11:23:01 Response: 220 imoweb2 Microsoft FTP Service (Version 5.0). 11:23:01 Command: USER imof2008 11:23:01 Response: 331 Password required for imof2008. 11:23:01 Command: PASS * 11:23:04 Response: 230 User imof2008 logged in. 11:23:04 Status: Connected 11:23:04 Status: Starting upload of L:\Database files\11-17-08\LMRP\adm4_lmrp_prod.dmp.gz 11:23:04 Command: CWD /Medications/IMO Medications Core/Test 11:23:04 Response: 250 CWD command successful. 11:23:04 Command: TYPE I 11:23:04 Response: 200 Type set to I. 11:23:04 Command: PASV 11:23:04 Response: 227 Entering Passive Mode (192,168,30,46,16,126). 11:23:04 Command: STOR adm4_lmrp_prod.dmp.gz 11:23:04 Response: 125 Data connection already open; Transfer starting. 11:26:36 Error: Could not write to transfer socket: ECONNRESET - Connection reset by peer

This happens on both servers. Please let me know if there is anything I need to do on my side. Thanks.

#10335 worksforme filezilla site manager FTP Account password changed to base64 format after updating to latest version r.e.vijaykumar

After the latest updation of FileZilla client (3.10.2), all of my FTP Account Password information changed from normal open password mode to secure base64 password format and also connection mode changed to use explicit FTP over TLS if available. Due to this I am unable to connect the FTP Servers for file transfer processes.

After I re-enter all of the information it seems to be saving now, but we now need to track down all of the information that is missing.

Currently I don't have backup of the Site Manager Information before updation to latest version.


#10376 rejected Latest Released Version (3.10.*) Bug and Site Manager Entries Not being taken backup by Filezilla during Updation of new version r.e.vijaykumar

I am also a victim of latest released version of Filezilla FTP Client 3.10.* bug which totally crashed/changed all of my FTP account informations (nearly 100 +) stored in the SiteManager.xml file encoded with base64 secure password mode from normal insecure mode and also changed each/every encryption mode to Use Explicit FTP over if TLS available.

I have seen lot of tickets raised by so many users regarding the latest release version bug and response/reply provided by Filezilla Development team for the tickets showing their irresponsibility, inability, incapability and inexperience in handling/ providing a solution for the reported issue. Also trying to escape from the issue without providing a solid/concrete solution.

Why wouldn't the process of automated backup of SiteManager file not being included for each and every updation of filezilla FTP client. If it is included or available which keeps avoiding many complications occur after updation and also easiest for the users to revert back to working version using the backup-ed version of sitemanager without spending so much time in research process after updation and waiting to hear an permanent solution from your end which never going to happen.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.