GnuTLS error -9: TLS packet with unexpected length

[juancarletto]

Hey! Somebody listening? Is this a FileZilla bug or not? Need more data? Please, let me know... Thanks a lot!

[botg]

I don't have the slightest idea what the problem might be. I don't have access to any affected server.

[juancarletto]

I could grant access to my server for you, if this could be of help. Please, contact me privately so we can arrange things. I think that you can, as a site admin, access to my personal data. You have my permission

[botg]

I would need a complete development environment on the server so that I can run it in the debugger and if needed make changes and recompile it.

[juancarletto]

Please, let me know what you need. The server runs a Debian testing, so let me know what packages and privileges you need so I can consider the issue.

[botg]

Easiest would be root access so that I can install the missing tools, start/stop the FTP server at will and attach with gdb when needed.


At the very least I require all build dependencies for the server and the used TLS library as well of the sources for both. gdb also needs to be installed alongside permission to attach to running processes.

[Respectable]

Although my own experience with 'unexpected packet length' is not exactly pertinent, I did encounter the error and did overcome it.

My cert had been converted to .pem from .pfx using the openSSL tool. Not being familiar with the tool, when I entered the path to its output in the 'Edit Server' dialog, I put the same file name for both key file and cert file.

When I ran a second conversion with DigiCert's tool, it made two files clearly marked as 'key' and 'cert'

When I entered them in the properly places in the SSL dialog of the server, everything was hunky dory.

[juancarletto]

No, that's not the problem. I've just solved this issue by changing the FTP client.

In Linux, both KFTPgrabber and ftp-ssl (from command line) worked fine. In Windows the free version of CoreFTP (LE) works also fine. But the solution for users was to use FireFTP (https://addons.mozilla.org/en-US/firefox/addon/fireftp/) and add-on for firefox that works OK. Because there are versions of firefox both for Windows and Linux, users only have to install this add-on so they can use a graphical ftp client (inside a tab of the browser) to connect to my server using TLS, etc.

Maybe in the future, Filezilla developers may solve the bug. Thanks a lot!

[mcgyver83]

Hi to all, I ran today in this error.
I have a filezilla server on win7 and i'm using filezilla client 3.5.1 from ubuntu 10.10
Here client and server log:

cline:

Status: Starting upload of /media/ACER/Mcg/Film/Nuovi/pippo.jpg
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,10,30,249)
Command: STOR pippo.jpg
Error: GnuTLS error -9: A TLS packet with unexpected length was received.
Status: Server did not properly shut down TLS connection
Response: 150 Connection accepted
Response: 550 can't access file.
Error: File transfer failed
Status: Starting upload of /media/ACER/Mcg/Film/Nuovi/pippo.jpg
Status: Retrieving directory listing...
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,10,30,248)
Command: MLSD
Response: 150 Connection accepted
Response: 226 Transfer OK
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,10,30,249)
Command: STOR pippo.jpg
Error: GnuTLS error -9: A TLS packet with unexpected length was received.
Response: 150 Connection accepted
Response: 550 can't access file.
Error: File transfer failed
Status: Starting upload of /media/ACER/Mcg/Film/Nuovi/pippo.jpg
Status: Retrieving directory listing...
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,10,30,248)
Command: MLSD
Response: 150 Connection accepted
Response: 226 Transfer OK
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,10,30,249)
Command: STOR pippo.jpg
Error: GnuTLS error -9: A TLS packet with unexpected length was received.
Response: 150 Connection accepted
Response: 550 can't access file.
Error: File transfer failed
Status: Retrieving directory listing...
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,10,30,248)
Command: MLSD
Response: 150 Connection accepted
Response: 226 Transfer OK
Status: Directory listing successful

Sever

(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> PASV
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> 227 Entering Passive Mode (192,168,1,10,30,249)
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> STOR pippo.jpg
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> 150 Connection accepted
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> 550 can't access file.
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> PASV
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> 227 Entering Passive Mode (192,168,1,10,30,248)
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> MLSD
(000022)09/07/2012 15:00:58 - userName (192.168.1.4)> 150 Connection accepted
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> SSL connection for data connection established
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 226 Transfer OK
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> PASV
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 227 Entering Passive Mode (192,168,1,10,30,249)
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> STOR pippo.jpg
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 150 Connection accepted
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 550 can't access file.
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> PASV
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 227 Entering Passive Mode (192,168,1,10,30,248)
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> MLSD
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 150 Connection accepted
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> SSL connection for data connection established
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 226 Transfer OK
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> PASV
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 227 Entering Passive Mode (192,168,1,10,30,249)
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> STOR pippo.jpg
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 150 Connection accepted
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 550 can't access file.
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> PASV
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 227 Entering Passive Mode (192,168,1,10,30,248)
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> MLSD
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 150 Connection accepted
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> SSL connection for data connection established
(000022)09/07/2012 15:00:59 - userName (192.168.1.4)> 226 Transfer OK
(000023)09/07/2012 15:01:44 - userName (192.168.1.4)> disconnected.
(000022)09/07/2012 15:01:59 - userName (192.168.1.4)> disconnected.
(000021)09/07/2012 15:02:42 - userName (192.168.1.4)> 421 Connection timed out.
(000021)09/07/2012 15:02:42 - userName (192.168.1.4)> disconnected.

Any hints?

[boco]

Response: 550 can't access file.

Looks like the server service cannot physically access or create the file in that directory. You must make sure the user account the server runs under has full privileges to the shared directories.