Custom Query (8117 matches)
Results (85 - 87 of 8117)
Since I updated Filezilla, I get the following error reports : Statut : Résolution de l'adresse de ftp.evrypalestine.org Statut : Connexion à 18.104.22.168:21... Erreur : Délai d'attente expiré Erreur : Impossible d'établir une connexion au serveur
I tried with another FTP client, and it works. so the problem seems to be with Filezilla. Regards, Bertrand bertrand.heilbronn@…
|#11130||rejected||Error on loading|
Getting a strange message suddenly. I installed the lastest version and still getting it. Please see a copy of the error message attached.
|#9816||rejected||Incorrect timestamp YEAR applied by client 22.214.171.124|
I use the FileZilla client to both place and retrieve files on a secure server.
The client is changing the YEAR portion of the timestamp on files from 2014 to 2013.
I have my settings to "preserve timestamp" and the month, day and time remain correct, but the YEAR is changed from 2014 to 2013.
When I transfer a file from my network location to the server, the YEAR changes to 2013.
When I transfer a file from the server to my network, the same thing happens.
When I simply VIEW files newly placed on the server by a sender other than myself, in FileZilla the YEAR appears changed to 2013. However, when I VIEW that same file on the server with a different FTP tool (such as WinSCP) the YEAR on the file correctly appears as 2014.
Files on my own network that I simply VIEW in FileZilla remain unchanged with the correct 2014 YEAR. The YEAR on my files changes from 2014 to 2013 when I transfer to the server side using FileZilla.
This is NOT solely a display issue, because on files I transfer off the server to my network, the YEAR is actually changed on the file timestamp.
FileZilla Client Version Information: