Moderator: Project members
-
eleonard
- 500 Command not understood
- Posts: 1
- Joined: 2015-01-14 23:24
- First name: Elizabeth
- Last name: Leonard
- Location: COLORADO
GnuTLS error -110: The TLS connection was non-properly terminated
#1
Post
by eleonard » 2015-01-14 23:54
Can anyone tell me if this is strictly a server issue. I have been with our IT Dept and they are saying no, the Vender in which I use this software to remote is saying yes. Help!!!! 
This is the new version downloaded Jan2015, using windows 7
«Status: Connecting to ???.???.?.??:21…
Status: Connection established, waiting for welcome message…
Status: Initializing TLS…
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
Status: Waiting to retry…
Status: Connecting to ???.???.?.??:21…
Status: Connection established, waiting for welcome message…
Response: 220 CODELSO FTP server (Version 4.2 Mon Sep 10 17:32:06 CDT 2012) ready.
Command: AUTH TLS
Response: 234 Using authentication type TLSv1
Status: Initializing TLS…
Error: GnuTLS error -110: The TLS connection was non-properly terminated.»
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
-
botg
- Site Admin
- Posts: 34944
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#2
Post
by botg » 2015-01-15 08:50
Most likely a server issue. Unfortunately the hostname has been removed from the log so I can’t analyze this further.
-
elmar112
- 500 Command not understood
- Posts: 2
- Joined: 2015-01-26 16:25
- First name: Elmar
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#3
Post
by elmar112 » 2015-01-26 16:32
I had a simillar issue.
Turned out that the client was outdated.
did not work with Filezilla 3.6.0.3 & GnuTLS 3.1.4, but worked fine with Filezilla 3.7.4.1 and gnuTLS 3.1.11.
hth
-
botg
- Site Admin
- Posts: 34944
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#4
Post
by botg » 2015-01-26 16:46
Speaking of outdated, that too are heavily outdated versions.
-
alexander.oss
- 500 Command not understood
- Posts: 1
- Joined: 2015-01-30 21:29
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#5
Post
by alexander.oss » 2015-01-30 21:33
I’m using FileZilla 3.10.0.2 with GnuTLS 3.2.20 (current, if I’m not mistaken) and I’m getting the same error (which has for quite some time forced me to use CoreFTP instead of FileZilla to connect to this server):
Status: Connecting to 208.75.145.17:990…
Status: Connection established, initializing TLS…
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
Is that enough information to diagnose the problem?
Thanks!
-
botg
- Site Admin
- Posts: 34944
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#6
Post
by botg » 2015-01-31 10:28
@alexander.oss: Your server does not seem to support strong cryptography, it only seems to support deprecated and insecure algorithms.
-
rachelinsall
- 500 Command not understood
- Posts: 1
- Joined: 2015-02-04 15:11
- First name: Rachel
- Last name: Insall
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#7
Post
by rachelinsall » 2015-02-04 15:20
I installed a FileZilla update this morning. Now I cannot log in and am getting the above error.
I seem to have version 3.10.1.1 (c) 2004-2015
this version seems to have been built 02/01/2015
wxWidgets: 3.0.3
GnuTLS: 3.2.21
SQLite: 3.8.8.2
I run Windows 7 64-bit system
I have completely uninstalled & re-installed FileZilla in an effort to resolve.
I do not have on-site IT support as we are a very small business. I’m not sure what my next steps should be.
-
MrDK
- 500 Command not understood
- Posts: 1
- Joined: 2015-02-11 14:50
- First name: Peter
- Last name: Petersen
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#8
Post
by MrDK » 2015-02-11 14:57
rachelinsall wrote:I seem to have version 3.10.1.1 (c) 2004-2015
this version seems to have been built 02/01/2015
wxWidgets: 3.0.3
GnuTLS: 3.2.21
SQLite: 3.8.8.2
I run Windows 7 64-bit system
I have the same versions and builds as rachaelinsall and is getting the same errors.
One thing worth noting is that is has been working fine at home, but now two days later I am on a different network (hotel) connecting to the same server.
I can upload files using CPanel, but that is a single file at a time.
ANY setting I can change to bypass whatever prevents me to use FileZilla with default settings?
-
boco
- Contributor
- Posts: 26606
- Joined: 2006-05-01 03:28
- Location: Germany
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#9
Post
by boco » 2015-02-11 15:22
Do you really want to give up on security in a public network? Then set the Encryption for your server entry in Site Manager back to Plain FTP.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Please do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
jasoncollege24
- 500 Command not understood
- Posts: 1
- Joined: 2015-07-01 07:00
- First name: Jay
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#10
Post
by jasoncollege24 » 2015-07-01 07:23
While setting the connection to plain FTP does work, this is not a good idea. Also, since this seems to be a wide spread issue on many servers, where the client is using filezilla, where other clients work fine, I believe this is a problem with filezilla, and not a server side issue.
i have exactly the same issue on a cPanel enabled server where I have root access. The server is using Pure-FTPD (default for cPanel servers)
This happens with file transfers, using filezilla 3.11.0.2
Since this FTP server is the default for cPanel servers, and this problem is wide spread, perhaps this should be seen as a bug in the filezilla client.
Just my 2 cents
##Begin Sig Block##
The name is Jay
Simple guy, with simple needs
##End Sig Block##
-
boco
- Contributor
- Posts: 26606
- Joined: 2006-05-01 03:28
- Location: Germany
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#11
Post
by boco » 2015-07-02 10:37
It has been explained multiple times why it is a problem with the servers and not with FileZilla, but here, again:
FileZilla asks if FTP over TLS is supported. The server replies: Yes. Then, FileZilla actually attempts to use FTP over TLS and the server craps out, because it is not properly configured despite saying so.
Solution: The server should either properly support FTP over TLS, or tell FileZilla that it doesn’t support it (by denying the AUTH command).
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Please do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
dominicg
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-09 12:21
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#12
Post
by dominicg » 2015-07-09 15:49
boco, I do belive you are right. It is not a problem with Filezilla but with the servers. However, given that many many servers are still not configured the proper way as for example intranet FTP servers which may not have had that requirement before or simply because of a lack of proper configuration, I think a better explanation is deserved.
The fact is that with previous versions of Filezilla, the default Encryption type for sites was «Plain FTP». All my sites were set this way. I’ve recently updated my Filezilla from 3.5.1 to 3.10.3 and I started to get the error we are talking about here. Of course, I did not notice that change in the default Encryption setting after the update. After some googling, I found out that the error has been caused by Filezilla’s new version which has now changed it’s default Encryption type to «Use explicit FTP over TLS if available». This change has been automatically applied to all the sites under our Site Manager. It is not a bug with Filezilla. It’s just that Filezilla has decided to implement this ahead of everyone else I believe. I’ve tried other clients and the default «FTP over TLS» is not attached to sites by default. It is still «Plain FTP» so all sites are connecting as expected. This is probably the reason why several users are blaming Filezilla rather than pinpoint the real issue.
Despite the fact that it is a very good approach to strenghten the security by default, several users (including myself) who upgraded with a more recent version of Filezilla were faced with this error for each and every site we were trying to connect to since some or all of our sites were previously set to connect by default with Encryption set to «Plain FTP». I’m in a large corporation (30 000 employees) and have no access to any of the FTP servers we are hitting because they are supported by another department. So, I need to switch back the Encryption settings to «Plain FTP» for all my sites. So be it… Because as you can imagine, I cannot request a nation-wide change to be applied to our numerous servers because Filezilla said so.
Therefore, I do believe that some of us here in this post are trying to figure out why this is happening and unfortunately all the evidences are pointing to Filezilla as the source of the problem which is not true. Clarifications are required which you did not mind posting…
I’m no big fan of your type of support since you seem to prefer to be rude rather than actually give better and constructive explanations. This is not acceptable in my opinion. Nevertheless, I still find that Filezilla is a very good product.
-
boco
- Contributor
- Posts: 26606
- Joined: 2006-05-01 03:28
- Location: Germany
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#13
Post
by boco » 2015-07-10 00:37
I do not know what your perception of ‘rude’ is, but if you mean the fact that we won’t spoon-feed everyone, you’re right.
We do not have the time to do individual customer care. At the same time, the target audience for FileZilla are advanced users. So we expect users to at least read a little and search for their problem before asking the same questions that have been answered already hundreds of times. There’s the FAQ and the Wiki, for exactly that reason.
tl;dr: «Customer Care» and «Technical Support» are different things. Tech-support sounds harsh often because there’s no mincing words with icing on top. 
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Please do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
dominicg
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-09 12:21
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#14
Post
by dominicg » 2015-07-10 12:08
boco, if you are assuming that your target audience is advanced users, you missed your target. Not sure if you read the subject but to my understanding, it says: «GnuTLS error -110: The TLS connection was non-properly terminated». I’ve searched the FAQ and Wiki and haven’t found any reference to this error. According to the first replies to this post, even botg was not even clear on what was going on:
Most likely a server issue. Unfortunately the hostname has been removed from the log so I can’t analyze this further
and you are assuming that everyone should be able to figure this out themselves? When a massive load of users are asking the same question here and there, how hard is it to post a link explaining why this happens and how this can be resolved?
Since you don’t seem to «care» or «support» much, I will post a «bug report» right here for users who are looking for some kind of «explanation» of the source of the problem. This should show you how smoothly «advanced users» were able to handle this. It will also show you the users how convinced Filezilla guys are that everyone in the world should follow Filezilla’s new feature when they release it. Because when Filezilla makes a change, it becomes officially the new internationally approved standard, right?
https://trac.filezilla-project.org/ticket/9995
-
botg
- Site Admin
- Posts: 34944
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#15
Post
by botg » 2015-07-10 12:49
Ticket 9995 is a good example how users disregard objective facts presented by an expert on the topic.
Instead of addressing the root of the problem these users instead want to shoot the messenger.
They keep arguing and arguing the same uninformed nonsense, constantly attempting to shift blame away from cause the problem and instead towards the trigger of the symptoms.
They don’t understand the problem and actively refuse to learn new things. On top of it they reject whatever those that do understand the problem have to say.
I think there’s a fitting quote for this kind of situation:
Isaac Asimov wrote:Anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that ‘my ignorance is just as good as your knowledge.’
Всегда спокойно подключался через этот фтп клиент, и соответственно в настройки никогда не лазил. Сейчас попробывал подключиться и вылетает такая ошибка
Статус: Соединение установлено, ожидание приглашения…
Ответ: 220 ProFTPD 1.3.5a Server (ProFTPD) [194.58.97.43]
Команда: AUTH TLS
Ответ: 234 AUTH TLS successful
Статус: Инициализирую TLS…
Ошибка: Ошибка GnuTLS -110: The TLS connection was non-properly terminated.
Статус: Сервер неверно закрыл TLS соединение
Ошибка: Невозможно подключиться к серверу
PS через pspad нормально подключился
I observed that one of my Windows Services was not connecting to an FTP location on a Unix Server, I ran the executable on my PC as the dev didn’t log any error and i was getting timeout error on trying to get response from an FTPWebRequest Object in C#.
On trying to access the FTP location using Filezilla I am getting the error
GnuTLS error -110: The TLS connection was non-properly terminated.
Using SFTP does not give this error and also using FTP in plain text(insecure) also does not.
I really do not understand this and note that the application has been running fine for years and this just suddenly happens on like 4 servers.
asked Aug 20, 2015 at 8:19
GnuTLS error -110: The TLS connection was non-properly terminated.
That just means that the peer just closed the socket and did not do a proper TLS shutdown. Some broken clients or servers do this. Assuming that this message relates to a data transfer you can usually ignore this because the transfer was finished anyway, so no data got lost.
Using SFTP does not give this error and also using FTP in plain text(insecure) also does not.
Of course you don’t get it, since SFTP is using the SSH protocol instead of TLS and plain FTP does no encryption at all, so no TLS too. And if there is no TLS involved you can not get any TLS errors.
I really do not understand this and note that the application has been running fine for years and this just suddenly happens on like 4 servers.
It might simply be that the servers changed, i.e. either they never supported FTPS (i.e. FTP with TLS, not to be confused with SFTP) before or they now switched to a broken implementation.
answered Aug 20, 2015 at 9:10
Steffen UllrichSteffen Ullrich
112k10 gold badges130 silver badges171 bronze badges
2
If you are connecting to a cPanel server then you can temporarily fix this issue by enabling «Broken Client Compatibility» in Pure-FTP settings in WHM.
answered Dec 21, 2015 at 6:23
TechiescornerTechiescorner
7692 gold badges11 silver badges25 bronze badges
Older version of Filezilla may be responsible for the said error. Faced the same error on 3.4 version issue was resolved after downloading the 3.6 one.
answered Jul 20, 2022 at 18:17
Всегда спокойно подключался через этот фтп клиент, и соответственно в настройки никогда не лазил. Сейчас попробывал подключиться и вылетает такая ошибка
Статус: Соединение установлено, ожидание приглашения...
Ответ: 220 ProFTPD 1.3.5a Server (ProFTPD) [194.58.97.43]
Команда: AUTH TLS
Ответ: 234 AUTH TLS successful
Статус: Инициализирую TLS...
Ошибка: Ошибка GnuTLS -110: The TLS connection was non-properly terminated.
Статус: Сервер неверно закрыл TLS соединение
Ошибка: Невозможно подключиться к серверу
задан 21 окт 2015 в 20:13
Гошка ТарасовГошка Тарасов
1,2584 золотых знака19 серебряных знаков45 бронзовых знаков
2
Получилось решить проблему только переключением способа шифрования — вместо «Использовать явный FTP через TLS если доступен» ставлю «Использовать обычный FTP (небезопасно)».
ответ дан 2 ноя 2015 в 13:02
I am trying to download some files from a server using FileZilla 3.9.0.5, using regular FTP over explicit TLS. Many files download just fine. It refuses to download certain files, however, giving me messages like the following:
Status: Starting download of /public_html/foo/bar/baz.php
Command: PASV
Response: 227 Entering Passive Mode (***my server IP***)
Command: RETR baz.php
Response: 150-Accepted data connection
Response: 150 13.0 kbytes to download
Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Response: 226-File successfully transferred
Response: 226 0.000 seconds (measured here), 26.04 Mbytes per second
Error: File transfer failed after transferring 13,653 bytes in 1 second
The server in question is a CentOS/cPanel box.
Can someone tell me how to resolve this?
EDIT: Some additional insight: the files on which FileZilla melted down had some hard tabs (character 9). I replaced all hard tabs with 4 spaces in the copies of these files on the server, then was able to download them just fine. Maybe something about the tab characters caused the problem?
EDIT 2: The server logs just have lots of entries like this:
Sat Sep 13 18:24:26 2014 0 ****** 13682 /home/******/public_html/foo/bar/baz.php a _ o r ****** ftp 1 * c
The ******s above represent the IP, username, and username again for the account in question. Except for the time stamp and number of bytes transferred, the entries for failed transfers are identical to the successful ones.
- Forums
- FTP
- [SOLVED] FileZilla Error: Gnutls Error -8: A Packet With Illegal Or Unsuported Version Was Received
This page has the solition for a filezilla error you might be getting with your FTP client that says GnuTLS error -8: A packet with illegal or unsuported version was received Connection attempt failed with «ECONNABORTED» — Connection aborted [4962], Last Updated: Sat Oct 08, 2022
edwin
Thu Nov 04, 2021
5 Comments
8224 Visits
Are you seeing the following error in your FileZilla FTP client? If so, I have the solution for you.
Status: Connection established, waiting for welcome message…
Status: Initializing TLS…
Status: Verifying certificate…
Status: TLS connection established.
Status: Logged in
Status: Starting download of /domains/taskini/.htaccess
Status: File transfer successful, transferred 260 bytes in 1 second
Status: Disconnected from server
Response: 421 Timeout — try typing a little faster next time
Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Response: 421 Timeout — try typing a little faster next time
Error: GnuTLS error -8: A packet with illegal or unsuported version was received
Status: Connection attempt failed with «ECONNABORTED» — Connection aborted
Error: Disconnected from server
This is what happened to me. Last week, I opened the FileZilla FTP client to connect to a customer’s website and it prompted me to upgrade. I did my work and upgraded after I was done.
The following week, I tried to connect to my server and I couldn’t I kept getting an errors:
Error: GnuTLS error -8: A packet with illegal or unsuported version was received
Status: Connection attempt failed with «ECONNABORTED» — Connection aborted
Error: Disconnected from server
The solution:
I downgraded from Version FileZilla_3.56.2_win64-setup.exe to FileZilla_3.55.1_win64-setup.exe
Now it works. Hope that helps.
Moderator: Project members
-
eleonard
- 500 Command not understood
- Posts: 1
- Joined: 2015-01-14 23:24
- First name: Elizabeth
- Last name: Leonard
- Location: COLORADO
GnuTLS error -110: The TLS connection was non-properly terminated
#1
Post
by eleonard » 2015-01-14 23:54
Can anyone tell me if this is strictly a server issue. I have been with our IT Dept and they are saying no, the Vender in which I use this software to remote is saying yes. Help!!!! This is the new version downloaded Jan2015, using windows 7
«Status: Connecting to ???.???.?.??:21…
Status: Connection established, waiting for welcome message…
Status: Initializing TLS…
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
Status: Waiting to retry…
Status: Connecting to ???.???.?.??:21…
Status: Connection established, waiting for welcome message…
Response: 220 CODELSO FTP server (Version 4.2 Mon Sep 10 17:32:06 CDT 2012) ready.
Command: AUTH TLS
Response: 234 Using authentication type TLSv1
Status: Initializing TLS…
Error: GnuTLS error -110: The TLS connection was non-properly terminated.»
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
-
botg
- Site Admin
- Posts: 34713
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#2
Post
by botg » 2015-01-15 08:50
Most likely a server issue. Unfortunately the hostname has been removed from the log so I can’t analyze this further.
-
elmar112
- 500 Command not understood
- Posts: 2
- Joined: 2015-01-26 16:25
- First name: Elmar
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#3
Post
by elmar112 » 2015-01-26 16:32
I had a simillar issue.
Turned out that the client was outdated.
did not work with Filezilla 3.6.0.3 & GnuTLS 3.1.4, but worked fine with Filezilla 3.7.4.1 and gnuTLS 3.1.11.
hth
-
botg
- Site Admin
- Posts: 34713
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#4
Post
by botg » 2015-01-26 16:46
Speaking of outdated, that too are heavily outdated versions.
-
alexander.oss
- 500 Command not understood
- Posts: 1
- Joined: 2015-01-30 21:29
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#5
Post
by alexander.oss » 2015-01-30 21:33
I’m using FileZilla 3.10.0.2 with GnuTLS 3.2.20 (current, if I’m not mistaken) and I’m getting the same error (which has for quite some time forced me to use CoreFTP instead of FileZilla to connect to this server):
Status: Connecting to 208.75.145.17:990…
Status: Connection established, initializing TLS…
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
Is that enough information to diagnose the problem?
Thanks!
-
botg
- Site Admin
- Posts: 34713
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#6
Post
by botg » 2015-01-31 10:28
@alexander.oss: Your server does not seem to support strong cryptography, it only seems to support deprecated and insecure algorithms.
-
rachelinsall
- 500 Command not understood
- Posts: 1
- Joined: 2015-02-04 15:11
- First name: Rachel
- Last name: Insall
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#7
Post
by rachelinsall » 2015-02-04 15:20
I installed a FileZilla update this morning. Now I cannot log in and am getting the above error.
I seem to have version 3.10.1.1 (c) 2004-2015
this version seems to have been built 02/01/2015
wxWidgets: 3.0.3
GnuTLS: 3.2.21
SQLite: 3.8.8.2
I run Windows 7 64-bit system
I have completely uninstalled & re-installed FileZilla in an effort to resolve.
I do not have on-site IT support as we are a very small business. I’m not sure what my next steps should be.
-
MrDK
- 500 Command not understood
- Posts: 1
- Joined: 2015-02-11 14:50
- First name: Peter
- Last name: Petersen
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#8
Post
by MrDK » 2015-02-11 14:57
rachelinsall wrote:I seem to have version 3.10.1.1 (c) 2004-2015
this version seems to have been built 02/01/2015
wxWidgets: 3.0.3
GnuTLS: 3.2.21
SQLite: 3.8.8.2
I run Windows 7 64-bit system
I have the same versions and builds as rachaelinsall and is getting the same errors.
One thing worth noting is that is has been working fine at home, but now two days later I am on a different network (hotel) connecting to the same server.
I can upload files using CPanel, but that is a single file at a time.
ANY setting I can change to bypass whatever prevents me to use FileZilla with default settings?
-
boco
- Contributor
- Posts: 26431
- Joined: 2006-05-01 03:28
- Location: Germany
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#9
Post
by boco » 2015-02-11 15:22
Do you really want to give up on security in a public network? Then set the Encryption for your server entry in Site Manager back to Plain FTP.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
jasoncollege24
- 500 Command not understood
- Posts: 1
- Joined: 2015-07-01 07:00
- First name: Jay
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#10
Post
by jasoncollege24 » 2015-07-01 07:23
While setting the connection to plain FTP does work, this is not a good idea. Also, since this seems to be a wide spread issue on many servers, where the client is using filezilla, where other clients work fine, I believe this is a problem with filezilla, and not a server side issue.
i have exactly the same issue on a cPanel enabled server where I have root access. The server is using Pure-FTPD (default for cPanel servers)
This happens with file transfers, using filezilla 3.11.0.2
Since this FTP server is the default for cPanel servers, and this problem is wide spread, perhaps this should be seen as a bug in the filezilla client.
Just my 2 cents
##Begin Sig Block##
The name is Jay
Simple guy, with simple needs
##End Sig Block##
-
boco
- Contributor
- Posts: 26431
- Joined: 2006-05-01 03:28
- Location: Germany
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#11
Post
by boco » 2015-07-02 10:37
It has been explained multiple times why it is a problem with the servers and not with FileZilla, but here, again:
FileZilla asks if FTP over TLS is supported. The server replies: Yes. Then, FileZilla actually attempts to use FTP over TLS and the server craps out, because it is not properly configured despite saying so.
Solution: The server should either properly support FTP over TLS, or tell FileZilla that it doesn’t support it (by denying the AUTH command).
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
dominicg
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-09 12:21
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#12
Post
by dominicg » 2015-07-09 15:49
boco, I do belive you are right. It is not a problem with Filezilla but with the servers. However, given that many many servers are still not configured the proper way as for example intranet FTP servers which may not have had that requirement before or simply because of a lack of proper configuration, I think a better explanation is deserved.
The fact is that with previous versions of Filezilla, the default Encryption type for sites was «Plain FTP». All my sites were set this way. I’ve recently updated my Filezilla from 3.5.1 to 3.10.3 and I started to get the error we are talking about here. Of course, I did not notice that change in the default Encryption setting after the update. After some googling, I found out that the error has been caused by Filezilla’s new version which has now changed it’s default Encryption type to «Use explicit FTP over TLS if available». This change has been automatically applied to all the sites under our Site Manager. It is not a bug with Filezilla. It’s just that Filezilla has decided to implement this ahead of everyone else I believe. I’ve tried other clients and the default «FTP over TLS» is not attached to sites by default. It is still «Plain FTP» so all sites are connecting as expected. This is probably the reason why several users are blaming Filezilla rather than pinpoint the real issue.
Despite the fact that it is a very good approach to strenghten the security by default, several users (including myself) who upgraded with a more recent version of Filezilla were faced with this error for each and every site we were trying to connect to since some or all of our sites were previously set to connect by default with Encryption set to «Plain FTP». I’m in a large corporation (30 000 employees) and have no access to any of the FTP servers we are hitting because they are supported by another department. So, I need to switch back the Encryption settings to «Plain FTP» for all my sites. So be it… Because as you can imagine, I cannot request a nation-wide change to be applied to our numerous servers because Filezilla said so.
Therefore, I do believe that some of us here in this post are trying to figure out why this is happening and unfortunately all the evidences are pointing to Filezilla as the source of the problem which is not true. Clarifications are required which you did not mind posting…
I’m no big fan of your type of support since you seem to prefer to be rude rather than actually give better and constructive explanations. This is not acceptable in my opinion. Nevertheless, I still find that Filezilla is a very good product.
-
boco
- Contributor
- Posts: 26431
- Joined: 2006-05-01 03:28
- Location: Germany
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#13
Post
by boco » 2015-07-10 00:37
I do not know what your perception of ‘rude’ is, but if you mean the fact that we won’t spoon-feed everyone, you’re right.
We do not have the time to do individual customer care. At the same time, the target audience for FileZilla are advanced users. So we expect users to at least read a little and search for their problem before asking the same questions that have been answered already hundreds of times. There’s the FAQ and the Wiki, for exactly that reason.
tl;dr: «Customer Care» and «Technical Support» are different things. Tech-support sounds harsh often because there’s no mincing words with icing on top.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
dominicg
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-09 12:21
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#14
Post
by dominicg » 2015-07-10 12:08
boco, if you are assuming that your target audience is advanced users, you missed your target. Not sure if you read the subject but to my understanding, it says: «GnuTLS error -110: The TLS connection was non-properly terminated». I’ve searched the FAQ and Wiki and haven’t found any reference to this error. According to the first replies to this post, even botg was not even clear on what was going on:
Most likely a server issue. Unfortunately the hostname has been removed from the log so I can’t analyze this further
and you are assuming that everyone should be able to figure this out themselves? When a massive load of users are asking the same question here and there, how hard is it to post a link explaining why this happens and how this can be resolved?
Since you don’t seem to «care» or «support» much, I will post a «bug report» right here for users who are looking for some kind of «explanation» of the source of the problem. This should show you how smoothly «advanced users» were able to handle this. It will also show you the users how convinced Filezilla guys are that everyone in the world should follow Filezilla’s new feature when they release it. Because when Filezilla makes a change, it becomes officially the new internationally approved standard, right?
https://trac.filezilla-project.org/ticket/9995
-
botg
- Site Admin
- Posts: 34713
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: GnuTLS error -110: The TLS connection was non-properly terminated
#15
Post
by botg » 2015-07-10 12:49
Ticket 9995 is a good example how users disregard objective facts presented by an expert on the topic.
Instead of addressing the root of the problem these users instead want to shoot the messenger.
They keep arguing and arguing the same uninformed nonsense, constantly attempting to shift blame away from cause the problem and instead towards the trigger of the symptoms.
They don’t understand the problem and actively refuse to learn new things. On top of it they reject whatever those that do understand the problem have to say.
I think there’s a fitting quote for this kind of situation:
Isaac Asimov wrote:Anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that ‘my ignorance is just as good as your knowledge.’
Всегда спокойно подключался через этот фтп клиент, и соответственно в настройки никогда не лазил. Сейчас попробывал подключиться и вылетает такая ошибка
Статус: Соединение установлено, ожидание приглашения...
Ответ: 220 ProFTPD 1.3.5a Server (ProFTPD) [194.58.97.43]
Команда: AUTH TLS
Ответ: 234 AUTH TLS successful
Статус: Инициализирую TLS...
Ошибка: Ошибка GnuTLS -110: The TLS connection was non-properly terminated.
Статус: Сервер неверно закрыл TLS соединение
Ошибка: Невозможно подключиться к серверу
задан 21 окт 2015 в 20:13
Гошка ТарасовГошка Тарасов
1,2583 золотых знака19 серебряных знаков44 бронзовых знака
2
Получилось решить проблему только переключением способа шифрования — вместо «Использовать явный FTP через TLS если доступен» ставлю «Использовать обычный FTP (небезопасно)».
ответ дан 2 ноя 2015 в 13:02
Question
We have FTPS configured on port 21 (security ALLOWED) and on port 990 (Security REQUIRED/Implicit). Filezilla connects successfully to the z/OS FTP server by using TLS to secure the control connection. But Filezilla cannot list the contents of a directory by using a TLS protected data connection.
The screen shot shows these Filezilla client messages:
Response: 125 List started OK
Error: GnuTLS error -110 in gnu_tls_record_recv: The TLS
Connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED -
Connection aborted
Response: 250 List completed successfully.
Error: Failed to retrieve directory listing
We verified that there is no firewall between the client and the mainframe. We also verified that the customer can connect to port 21 in the clear but receives an error on the same client if they try to use SSL/TLS (active FTP).
Answer
In this situation it was found that the FTP server was configured (defaulted) to the draft level of the FTP/TLS RFCs. One effect of this is that the session is simply closed instead of first sending an SSL Close Alert message first.
If your TLSRFCLEVEL is configured as DRAFT, change it to TLSRFCLEVEL RFC4217. If it defaulted to DRAFT, add a TLSRFCLEVEL RFC4217 statement to the server’s FTP.DATA input to change this behavior.
Specification of the TLSRFCLEVEL does not affect the initial SSL handshake or encryption of traffic; it changes the behavior when a session (or at least, SSL) ends. Specifically, configuring TLSRFCLEVEL RFC4217 will cause an SSL Close alert packet to be sent before actually closing the TCP connection (sending the FIN). Apparently the GnuTLS
code used by FileZilla is strictly enforcing receipt of the alert, and errors out when a FIN arrives without the alert. So adding that configuration statement should resolve the problem with FileZilla not getting the LIST output.
[{«Business Unit»:{«code»:»BU054″,»label»:»Systems w/TPS»},»Product»:{«code»:»SSSN3L»,»label»:»z/OS Communications Server»},»Platform»:[{«code»:»PF035″,»label»:»z/OS»}],»Component»:»»,»Version»:»»,»Line of Business»:{«code»:»LOB35″,»label»:»Mainframe SW»}}]
Product Synonym
ZOSCS COMMSERVER
I am trying to download some files from a server using FileZilla 3.9.0.5, using regular FTP over explicit TLS. Many files download just fine. It refuses to download certain files, however, giving me messages like the following:
Status: Starting download of /public_html/foo/bar/baz.php
Command: PASV
Response: 227 Entering Passive Mode (***my server IP***)
Command: RETR baz.php
Response: 150-Accepted data connection
Response: 150 13.0 kbytes to download
Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Response: 226-File successfully transferred
Response: 226 0.000 seconds (measured here), 26.04 Mbytes per second
Error: File transfer failed after transferring 13,653 bytes in 1 second
The server in question is a CentOS/cPanel box.
Can someone tell me how to resolve this?
EDIT: Some additional insight: the files on which FileZilla melted down had some hard tabs (character 9). I replaced all hard tabs with 4 spaces in the copies of these files on the server, then was able to download them just fine. Maybe something about the tab characters caused the problem?
EDIT 2: The server logs just have lots of entries like this:
Sat Sep 13 18:24:26 2014 0 ****** 13682 /home/******/public_html/foo/bar/baz.php a _ o r ****** ftp 1 * c
The ******s above represent the IP, username, and username again for the account in question. Except for the time stamp and number of bytes transferred, the entries for failed transfers are identical to the successful ones.
I am trying to download some files from a server using FileZilla 3.9.0.5, using regular FTP over explicit TLS. Many files download just fine. It refuses to download certain files, however, giving me messages like the following:
Status: Starting download of /public_html/foo/bar/baz.php
Command: PASV
Response: 227 Entering Passive Mode (***my server IP***)
Command: RETR baz.php
Response: 150-Accepted data connection
Response: 150 13.0 kbytes to download
Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Response: 226-File successfully transferred
Response: 226 0.000 seconds (measured here), 26.04 Mbytes per second
Error: File transfer failed after transferring 13,653 bytes in 1 second
The server in question is a CentOS/cPanel box.
Can someone tell me how to resolve this?
EDIT: Some additional insight: the files on which FileZilla melted down had some hard tabs (character 9). I replaced all hard tabs with 4 spaces in the copies of these files on the server, then was able to download them just fine. Maybe something about the tab characters caused the problem?
EDIT 2: The server logs just have lots of entries like this:
Sat Sep 13 18:24:26 2014 0 ****** 13682 /home/******/public_html/foo/bar/baz.php a _ o r ****** ftp 1 * c
The ******s above represent the IP, username, and username again for the account in question. Except for the time stamp and number of bytes transferred, the entries for failed transfers are identical to the successful ones.
FTP OS: Windows
FTP Server: FileZilla (latest (1.0.1)
Computer OS: Windows
FluentFTP Version: 35.0.5
Attempting to upload a file to FileZilla from C# (.net 3.1) using explicit TLS fails to perform TLS handshake (note «Connect» is successful)
This can be replicated every time (I’ve done it on 3 machines) by debugging the following code after installing FileZilla on a windows machine.
FileZilla settings — Under FTP Server
- Protocol: «Require explicit FTP over TLS»
I have also tried downloading the certificates via openssl and added them in to the code below, but with the same results.
using var client = new FtpClient("127.0.0.1", 21, "orderease", "xxx")
{
SocketKeepAlive = true,
ValidateAnyCertificate = true,
SslProtocols = SslProtocols.Tls12,
EncryptionMode = FtpEncryptionMode.Explicit,
DataConnectionType = FtpDataConnectionType.PASV,
};
var ftpLog = new StringBuilder();
client.OnLogEvent = (level, s) => { ftpLog.AppendLine(level + " - " + s); };
client.Connect();
client.SetWorkingDirectory("/GMS-EDI/GMS_Order");
var response = client.Upload(Encoding.ASCII.GetBytes(content), $"{fileName}.txt");
if (response == FtpStatus.Failed)
{
log.LogError("Failed to upload ");
log.LogError(ftpLog.ToString());
}
client.Disconnect();
Logs :
Filezilla Logs
2021-10-28T18:08:42.299Z >> [FTP Session 26 127.0.0.1 orderease] SYST
2021-10-28T18:08:42.299Z << [FTP Session 26 127.0.0.1 orderease] 215 UNIX emulated by FileZilla.
2021-10-28T18:08:49.043Z >> [FTP Session 26 127.0.0.1 orderease] CWD /GMS-EDI/GMS_Order
2021-10-28T18:08:49.043Z << [FTP Session 26 127.0.0.1 orderease] 250 CWD command successful
2021-10-28T18:08:52.655Z >> [FTP Session 26 127.0.0.1 orderease] PWD
2021-10-28T18:08:52.655Z << [FTP Session 26 127.0.0.1 orderease] 257 "/GMS-EDI/GMS_Order" is current directory.
2021-10-28T18:08:52.655Z >> [FTP Session 26 127.0.0.1 orderease] SIZE /GMS-EDI/GMS_Order/SPISO-20211028124510-N.txt
2021-10-28T18:08:52.655Z << [FTP Session 26 127.0.0.1 orderease] 213 892
2021-10-28T18:08:52.656Z >> [FTP Session 26 127.0.0.1 orderease] DELE SPISO-20211028124510-N.txt
2021-10-28T18:08:52.656Z << [FTP Session 26 127.0.0.1 orderease] 250 File deleted successfully.
2021-10-28T18:08:52.657Z >> [FTP Session 26 127.0.0.1 orderease] TYPE I
2021-10-28T18:08:52.657Z << [FTP Session 26 127.0.0.1 orderease] 200 Type set to I
2021-10-28T18:08:52.660Z >> [FTP Session 26 127.0.0.1 orderease] PASV
2021-10-28T18:08:52.660Z VV [FTP Session 26 127.0.0.1 orderease] Trying: data_listen_socket_->listen(1, 0)
2021-10-28T18:08:52.660Z << [FTP Session 26 127.0.0.1 orderease] 227 Entering Passive Mode (127,0,0,1,204,126)
2021-10-28T18:08:52.661Z VV [FTP Session 26 127.0.0.1 orderease] session::on_socket_event(): source = data listen, flag = 2, error = 0, state = -1
2021-10-28T18:08:52.662Z VV [FTP Session 26 127.0.0.1 orderease] tls_layer_impl::server_handshake()
2021-10-28T18:08:52.662Z VV [FTP Session 26 127.0.0.1 orderease] tls_layer_impl::continue_handshake()
2021-10-28T18:08:52.662Z VV [FTP Session 26 127.0.0.1 orderease] tls_layer_impl::continue_handshake()
2021-10-28T18:08:52.662Z >> [FTP Session 26 127.0.0.1 orderease] STOR SPISO-20211028124510-N.txt
2021-10-28T18:08:52.662Z << [FTP Session 26 127.0.0.1 orderease] 150 Starting data transfer.
2021-10-28T18:08:52.663Z VV [FTP Session 26 127.0.0.1 orderease] tls_layer_impl::continue_handshake()
2021-10-28T18:08:52.666Z VV [FTP Session 26 127.0.0.1 orderease] tls_layer_impl::continue_handshake()
2021-10-28T18:08:52.666Z II [FTP Session 26 127.0.0.1 orderease] TLS Handshake successful
2021-10-28T18:08:52.666Z II [FTP Session 26 127.0.0.1 orderease] TLS Session resumed
2021-10-28T18:08:52.666Z II [FTP Session 26 127.0.0.1 orderease] Protocol: TLS1.2, Key exchange: ECDHE-X25519, Cipher: AES-256-GCM, MAC: AEAD
2021-10-28T18:08:52.666Z VV [FTP Session 26 127.0.0.1 orderease] session::on_socket_event(): source = data, flag = 2, error = 0, state = 2
2021-10-28T18:08:52.667Z !! [FTP Session 26 127.0.0.1 orderease] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
2021-10-28T18:08:52.667Z == [FTP Session 26 127.0.0.1 orderease] Client did not properly shut down TLS connection
2021-10-28T18:08:52.667Z VV [FTP Session 26 127.0.0.1 orderease] tls_layer_impl::shutdown()
2021-10-28T18:08:52.667Z VV [FTP Session 26 127.0.0.1 orderease] data_socket_->shutdown() = 126
2021-10-28T18:08:52.667Z << [FTP Session 26 127.0.0.1 orderease] 425 Error while transfering data: ECONNABORTED - Connection aborted
2021-10-28T18:08:52.667Z VV [FTP Session 26 127.0.0.1 orderease] session::close_data_connection() = 1
2021-10-28T18:08:57.659Z !! [FTP Session 26 127.0.0.1 orderease] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted.
2021-10-28T18:08:57.659Z !! [FTP Server] Session ended with error from source 0. Reason: ECONNABORTED - Connection aborted.
FluentFTP logs
[2021-10-28T18:18:49.266Z] Failed to upload
[2021-10-28T18:18:49.903Z] Verbose - > Connect()
[2021-10-28T18:18:49.904Z] Info - Status: Connecting to 127.0.0.1:21
[2021-10-28T18:18:49.905Z] Verbose - Response: 220-FileZilla Server 1.0.1
[2021-10-28T18:18:49.905Z] Info - Response: 220 Please visit https://filezilla-project.org/
[2021-10-28T18:18:49.906Z] Info - Status: Detected FTP server: FileZilla
[2021-10-28T18:18:49.907Z] Info - Command: AUTH TLS
[2021-10-28T18:18:49.908Z] Info - Response: 234 Using authentication type TLS.
[2021-10-28T18:18:49.909Z] Info - Status: FTPS Authentication Successful
[2021-10-28T18:18:49.910Z] Verbose - Status: Time to activate encryption: 0h 0m 0s. Total Seconds: 0.0273426.
[2021-10-28T18:18:49.911Z] Info - Command: USER orderease
[2021-10-28T18:18:49.912Z] Info - Response: 331 Please, specify the password.
[2021-10-28T18:18:49.913Z] Info - Command: PASS ***
[2021-10-28T18:18:49.914Z] Info - Response: 230 Login successful.
[2021-10-28T18:18:49.915Z] Info - Command: PBSZ 0
[2021-10-28T18:18:49.916Z] Info - Response: 200 PBSZ=0
[2021-10-28T18:18:49.917Z] Info - Command: PROT P
[2021-10-28T18:18:49.918Z] Info - Response: 200 Protection level set to P
[2021-10-28T18:18:49.919Z] Info - Command: FEAT
[2021-10-28T18:18:49.920Z] Verbose - Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type*;size*;modify*;perm*;
Response: MLSD
Response: AUTH SSL
Response: AUTH TLS
Response: PROT
Response: PBSZ
Response: UTF8
Response: TVFS
Response: EPSV
Response: EPRT
Response: MFMT
[2021-10-28T18:18:49.923Z] Info - Response: 211 End
[2021-10-28T18:18:49.924Z] Info - Status: Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
[2021-10-28T18:18:49.925Z] Info - Command: OPTS UTF8 ON
[2021-10-28T18:18:49.926Z] Info - Response: 202 UTF8 mode is always enabled. No need to send this command
[2021-10-28T18:18:49.927Z] Info - Command: SYST
[2021-10-28T18:18:49.928Z] Info - Response: 215 UNIX emulated by FileZilla.
[2021-10-28T18:18:49.930Z] Verbose - > SetWorkingDirectory("/GMS-EDI/GMS_Order")
[2021-10-28T18:18:49.931Z] Info - Command: CWD /GMS-EDI/GMS_Order
[2021-10-28T18:18:49.932Z] Info - Response: 250 CWD command successful
[2021-10-28T18:18:49.933Z] Verbose - > Upload("SPISO-20211028124510-N.txt", Overwrite, False)
[2021-10-28T18:18:49.934Z] Verbose - > FileExists("SPISO-20211028124510-N.txt")
[2021-10-28T18:18:49.935Z] Verbose - Status: Testing connectivity using Socket.Poll()...
[2021-10-28T18:18:49.936Z] Info - Command: PWD
[2021-10-28T18:18:49.939Z] Info - Response: 257 "/GMS-EDI/GMS_Order" is current directory.
[2021-10-28T18:18:49.940Z] Info - Command: SIZE /GMS-EDI/GMS_Order/SPISO-20211028124510-N.txt
[2021-10-28T18:18:49.941Z] Info - Response: 213 892
[2021-10-28T18:18:49.942Z] Verbose - > DeleteFile("SPISO-20211028124510-N.txt")
[2021-10-28T18:18:49.943Z] Info - Command: DELE SPISO-20211028124510-N.txt
[2021-10-28T18:18:49.944Z] Info - Response: 250 File deleted successfully.
[2021-10-28T18:18:49.946Z] Verbose - > OpenWrite("SPISO-20211028124510-N.txt", Binary)
[2021-10-28T18:18:49.948Z] Info - Command: TYPE I
[2021-10-28T18:18:49.950Z] Info - Response: 200 Type set to I
[2021-10-28T18:18:49.951Z] Verbose - > OpenPassiveDataStream(PASV, "STOR SPISO-20211028124510-N.txt", 0)
[2021-10-28T18:18:49.954Z] Info - Command: PASV
[2021-10-28T18:18:49.955Z] Info - Response: 227 Entering Passive Mode (127,0,0,1,244,130)
[2021-10-28T18:18:49.956Z] Info - Status: Connecting to 127.0.0.1:62594
[2021-10-28T18:18:49.957Z] Info - Command: STOR SPISO-20211028124510-N.txt
[2021-10-28T18:18:49.958Z] Info - Response: 150 Starting data transfer.
[2021-10-28T18:18:49.959Z] Info - Status: FTPS Authentication Successful
[2021-10-28T18:18:49.961Z] Verbose - Status: Time to activate encryption: 0h 0m 0s. Total Seconds: 0.0057162.
[2021-10-28T18:18:49.962Z] Verbose - Status: Disposing FtpSocketStream...
[2021-10-28T18:18:49.963Z] Info - Response: 425 Error while transfering data: ECONNABORTED - Connection aborted
I am trying to download some files from a server using FileZilla 3.9.0.5, using regular FTP over explicit TLS. Many files download just fine. It refuses to download certain files, however, giving me messages like the following:
Status: Starting download of /public_html/foo/bar/baz.php
Command: PASV
Response: 227 Entering Passive Mode (***my server IP***)
Command: RETR baz.php
Response: 150-Accepted data connection
Response: 150 13.0 kbytes to download
Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Response: 226-File successfully transferred
Response: 226 0.000 seconds (measured here), 26.04 Mbytes per second
Error: File transfer failed after transferring 13,653 bytes in 1 second
The server in question is a CentOS/cPanel box.
Can someone tell me how to resolve this?
EDIT: Some additional insight: the files on which FileZilla melted down had some hard tabs (character 9). I replaced all hard tabs with 4 spaces in the copies of these files on the server, then was able to download them just fine. Maybe something about the tab characters caused the problem?
EDIT 2: The server logs just have lots of entries like this:
Sat Sep 13 18:24:26 2014 0 ****** 13682 /home/******/public_html/foo/bar/baz.php a _ o r ****** ftp 1 * c
The ******s above represent the IP, username, and username again for the account in question. Except for the time stamp and number of bytes transferred, the entries for failed transfers are identical to the successful ones.
|
# (отредактировано 11 лет, 8 месяцев назад) |
|
|
Темы: 7 Сообщения: 23 Участник с: 17 мая 2011 |
Прям как в заголовке — Не было печали, апдейтов накачали :))) Апдейты дело хорошее, но почему-то некоторые вещи ломаются напрочь после них, при этом, сразу хочу сказать, дабы избежать лишних недовольств, что конфиги просмативаются и обновляются после апдейтов. Проблема в следующем, не могу зайти по ftp на хостинг, использую filezilla — 3.5.1-1, и TLS шифрование — gnutls-3.0.2-1 Response: 234 AUTH TLS OK. Status: Initializing TLS... Error: GnuTLS error -12: A TLS fatal alert has been received. Error: Could not connect to server Пробовал переустановить gnutls, не помогло, может кто знает как это починить, а то как-то через web-морду не очень удобно пользоваться ftp. |
|
sleepycat |
# |
|
Темы: 98 Сообщения: 3291 Участник с: 19 июля 2011 |
дело не в программе,а в конфиге, имхо ябы удалил и натроил бы сначала,заодно пошагово, проверяя работу.
Лозунг у них был такой: «Познание бесконечности требует бесконечного времени». С этим я не спорил, но они делали из этого неожиданный вывод: «А потому работай не работай — все едино». И в интересах неувеличения энтропии Вселенной они не работали. (с) |
|
dernik |
# |
|
Темы: 7 Сообщения: 23 Участник с: 17 мая 2011 |
попробовал создать конфиг от другого пользователя на этой же машине, никогда до этого не заходил из под него, да и Filezilla не запускалась, так что конфигов не было. Результат — та же ошибка, видимо дело в программе или её работе именно с TLS. Для чистоты эксперимента, всё же удалил все конфиги и настроил по новой — не помогло… Пошагово настраивать, не особенно понял как это, ведь там подключение возможно только когда хост+юзер+пасс введён и правильно выставлен режим TLS, иначе вообще сразу идёт посыл от сервера далеко и надолго. Да я бы рад использовать другую прогу, мне вообще нравилось пользоваться ftp через “mc”, только вот он шифрование не поддерживает, а сейчас уже никак, у хостера шифрование 
|
|
Natrio |
# |
|
Темы: 47 Сообщения: 4767 Участник с: 08 января 2011 |
Вы пробовали откатывать обновившиеся пакеты? То есть filezilla и gnutls по одному. |
|
dernik |
# |
|
Темы: 7 Сообщения: 23 Участник с: 17 мая 2011 |
Спс всем и Natrio, откатился и заработало сразу. Видимо всё дело в gnutls 3.0.x, если кому интересно, то сейчас версии следующие стоят, было и стало: filezilla (3.5.1-1 => 3.5.0-1) gnutls (3.0.2-1 => 2.12.6.1-1) пока поставил эти пакеты в IgnorePkg, буду пробовать с нотика, с него редко работаю, зато арч на нём один в один как на домашнем. P.S. рано обрадовался |
|
dernik |
# |
|
Темы: 7 Сообщения: 23 Участник с: 17 мая 2011 |
Если кому интересно, то проблема не только у меня, все кто пользуются filezilla/gnutls в Арче с такими же косяками, уже зарепортили баг вот ветка с англоязычного форума — https://bbs.archlinux.org/viewtopic.php?id=124782 вопрос: может есть другой клиент работающий с шифрованием, раньше искал, как-то ничего не попалось на глаза. |
|
0leg |
# |
|
Темы: 7 Сообщения: 104 Участник с: 21 декабря 2008 |
Новый gnutls требует дописывания программ, которые юзают его: https://savannah.gnu.org/support/index.php?107660 Столкнулся с проблемой в claws-mail — не получалась почта с некоторых серверов. В claws-mail внесены изменения, чтобы работал с новым gnutls, теперь всё ок. |
|
sleepycat |
# |
|
Темы: 98 Сообщения: 3291 Участник с: 19 июля 2011 |
да есть всякишного, юзаю mc для фтп. но поручится за tls не могу, просто не уверен до конца… Лозунг у них был такой: «Познание бесконечности требует бесконечного времени». С этим я не спорил, но они делали из этого неожиданный вывод: «А потому работай не работай — все едино». И в интересах неувеличения энтропии Вселенной они не работали. (с) |
|
dernik |
# |
|
Темы: 7 Сообщения: 23 Участник с: 17 мая 2011 |
Всё пофиксили, вышла новая Filezilla 3.5.1-2, где оно вновь как и прежде, красиво заработало. |
|
dernik |
# |
|
Темы: 7 Сообщения: 23 Участник с: 17 мая 2011 |
Для тех кому интересно, я как-то выше задавал вопрос какие ftp клиенты поддерживают работу по SSL/TLS, оказалось, что под линуксом в общем-то из распространённых это только Filezilla, может есть и ещё, но как-то распространённых я не встречал, да и толковых тоже.
“В жизни нет того, чего бы нам хотелось” Мне нравится как работает Filezilla, в общем-то всё хорошо и продуманно, но в ней нет так нужных шорткатов, да парочка есть, но отсутствую непосредственно рабочие, такие как скачивание и закачивание, переход из одной панели в другую, а это ужасно раздражает, особенно когда сидишь редактируешь файл, сохранил, закинуть на сервер и тебе надо ради 2 кликов за мышой тянуться. Всё это длинное предисловие было к тому, что я нашёл обходной путь, есть такой замечательный пакет tlswrap — http://www.tlswrap.com/ |
