Custom Query (8169 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (499 - 501 of 8169)

Ticket Resolution Summary Owner Reporter
#8383 fixed Filezilla client Feature request - retain open sessions upon restart apicton
Description

I always have about 6 connections in my filezilla client for the projects I'm working on.

Each time my MS updates force a system reboot overnight, I have to try and remember what connections I had open and re-open them. Of course I just realized that I can store a local default directory for each connection, so that is a great help...but is it possible to store open connection tabs upon shutdown so they are ready when I re-open filezilla? Even if they just re-open on the screen without making an active connection, that would be huge.

Thanks for reading and keep up the great work. Filezilla is the best.

thanks, Andy

#8396 fixed Issue while upgrading Filezilla client version from 3.5.3 to 3.6.0.2 winadmin
Description

Hi support,

Good Evening ! Recently i upgraded filezilla client version from 3.5.3 to 3.6.0.2 .

While using FileZilla client version 3.6.0.2 ( upload or download files and folder ) but i got below error :-- --- Error: GnuTLS error -110: The TLS connection was non-properly terminated. Error: Could not connect to server Status: Waiting to retry... Status: Connecting to 65.182.191.177:990... Status: Connection established, initializing TLS... Error: GnuTLS error -110: The TLS connection was non-properly terminated. Error: Could not connect to server


While Using same details i used in filezilla client version 3.5.3 , it was working fine / i successfully connected to FTP server.

Note :-- Secure FTP configured on the server (FTPS) . port - 990 allowed in firewall in server.

I don't understand , is it a bug in filezilla client version 3.6.0.2 or there is any setting missing on server side.

Kindly provide me resolution / Workaround for the same ASAP. I will be thankful for the same .

Regards,

Sahil Dua

#8401 fixed Client crash when open non-English local folder/directory using "Open" in the right-click pop-up context menu Emil Chou
Description

Client version: 3.6.0.2 Character set for non-Unicode programs: Traditional Chinese - Taiwan (950)

Crash happens when try to open a local folder with non-English path in Windows Explorer, using the "Open" function in the right-click pop-up context menu. Crash happens both in the file pane and the directory pane.

Specifically, crash happens when opening the folder path that contains non-English and not-within-the-default-language characters. For example, when opening the folder path contains Simplified Chinese or Japanese characters, the client crashes. But when opening the folder path contains Traditional Chinese characters, the client does not crash, but still does not open the folder in Windows Explorer.

I tried this bug on two different computers, and both has this problem. Both machines are using Windows 7 Pro SP1 x64.

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