GnuTLS error -53: Error in the push function

[greyambience]

I fixed this on my FTP.

It was a firewall/port forward problem.

I had a Qnap Nas behind a Asus RT-56U router

This is how I configured my router;

Under PORT FORWARDING

WRONG Got error 53
Port range: 55536,56559
Adress: 192.168.0.XXX
Local port: 55536
Protocol: BOTH


CORRECT
Port range: 55536,56559
Adress: 192.168.0.XXX
Local port: *leave it blank*
Protocol: TCP


That local port messed it up.

[surferride]

Hi, I am having the same problem and I tried with the port range forwarding but still didnt work.

Any ideas what it could be? This happens with one particular FTP Server and the Hosting provider says its my connection, not theirs.

This is what FileZilla shows (By the way I tried different computers and FTP clients and the same (or similar) errors occur)

Command: MLSD
Response: 150 Accepted data connection
Response: 226-Options: -a -l
Response: 226 24 matches total
Command: PASV
Response: 227 Entering Passive Mode (217,26,52,15,192,226)
Command: REST 513163264
Response: 350 Restarting at 513163264
Command: STOR backup.tar
Response: 150 Accepted data connection
Error: GnuTLS error -53: Error in the push function.
Response: 226-Error during write to file
Response: 226-Transfer aborted
Response: 226 0.493 seconds (measured here), 97.27 Kbytes per second
Error: File transfer failed after transferring 327,680 bytes in 1 second

Thanks for your help!

Surferride

[botg]

Response: 226-Error during write to file

That server is FUBAH, fucked up beyond all hope. It encounters a fatal error and responds with success[*], a natural born top manager.

[*]226 means the transfer finished successfully.

[surferride]

Thanks for your comments, the host finally found what the problem was.

While they were blaming to me because of firewall issues, the problem was that I am using a trial account which size was limited to 500 MB and I was trying to upload a file of 1 GB. When the file reached half of it, it started "bouncing"because of lack of space.

I m a little bit frustrated with their services already and haven't even yet started to host with them...not a very good sign.

Thanks for your comments on my question.

Surferride

[boco]

But that doesn't change the fact that the server is broken.

[surferride]

Thanks good that I haven't choose that host then!

To understand what's the problem? It's incorrectly configured ?

Thanks !

Surferride

[boco]

It sends a 226 reply code (which means success) even though the transfer failed. Since FTP clients only evaluate the code, not the reply text (well, there are very few exceptions to that rule), the transfer is registered as successful. That might give you a lot of broken/truncated transfers.

The correct reply code would be 426.