Как исправить эту ошибку gnutls 110 tls соединение было неправильно разорвано - Исправление ошибок и поиск оптимальных решений проблем

Moderator: Project members

wanakt: 500 Command not understood; Posts: 3; Joined: 2022-06-20 08:23; First name: Jay; Last name: Kim

GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by wanakt » 2022-06-20 09:20

I am using FileZilla Server 1.4.1.

The server seems to be installed properly, since it passed the test on ftptest.net.
Furthermore, getting list of directories, downloading and delete through TLS Connection succeeded.

However, whenever I try to upload a file to the ftp, an error message «GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated» continues to appear.
The log of FileZilla Server is as follows;

<Date> Info [Type] Message
<> FTP Session 297 192.168.0.1 [Response] 220-FileZilla Server 1.4.1
<> FTP Session 297 192.168.0.1 [Response] 220 Please visit https://filezilla-project.org/
<> FTP Session 297 192.168.0.1 [Command] AUTH TLS
<> FTP Session 297 192.168.0.1 [Response] 234 Using authentication type TLS.
<> FTP Session 297 192.168.0.1 [Command] USER ****
<> FTP Session 297 192.168.0.1 [Response] 331 Please, specify the password.
<> FTP Session 297 192.168.0.1 [Command] PASS ****
<> FTP Session 297 192.168.0.1 wanakt [Response] 230 Login successful.
<> FTP Session 297 192.168.0.1 wanakt [Command] PBSZ 0
<> FTP Session 297 192.168.0.1 wanakt [Response] 200 PBSZ=0
<> FTP Session 297 192.168.0.1 wanakt [Command] PROT P
<> FTP Session 297 192.168.0.1 wanakt [Response] 200 Protection level set to P
<> FTP Session 297 192.168.0.1 wanakt [Command] OPTS utf8 on
<> FTP Session 297 192.168.0.1 wanakt [Response] 202 UTF8 mode is always enabled. No need to send this command
<> FTP Session 297 192.168.0.1 wanakt [Command] PWD
<> FTP Session 297 192.168.0.1 wanakt [Response] 257 «/» is current directory.
<> FTP Session 297 192.168.0.1 wanakt [Command] TYPE I
<> FTP Session 297 192.168.0.1 wanakt [Response] 200 Type set to I
<> FTP Session 297 192.168.0.1 wanakt [Command] PASV
<> FTP Session 297 192.168.0.1 wanakt [Response] 227 Entering Passive Mode (221,148,162,103,246,204)
<> FTP Session 297 192.168.0.1 wanakt [Command] STOR test/임차인 동의서(202호).pdf
<> FTP Session 297 192.168.0.1 wanakt [Response] 150 Starting data transfer.
<> FTP Session 297 192.168.0.1 wanakt [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
<> FTP Session 297 192.168.0.1 wanakt [Status] Client did not properly shut down TLS connection
<> FTP Session 297 192.168.0.1 wanakt [Response] 425 Error while transfering data: ECONNABORTED — Connection aborted

The odd things is that the file is uploaded properly regardless of the above error message.

It would be highly appreciated, if you would let me know what I should do to fix the above error.

botg: Site Admin; Posts: 34747; Joined: 2004-02-23 20:49; First name: Tim; Last name: Kosse; Contact:

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by botg » 2022-06-21 08:38

<> FTP Session 297 192.168.0.1 wanakt [Response] 227 Entering Passive Mode (221,148,162,103,246,204)

So the server sits behind a NAT router. Did you check the «Use the default host for local connections» checkbox on the server’s passive mode settings page?

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by tchicken » 2022-06-22 20:06

Thank you for your answer botg,

I checked the box, restarted the service, but I still have the same error, another idea ?

And I have the same problème in passive or active mode !

botg: Site Admin; Posts: 34747; Joined: 2004-02-23 20:49; First name: Tim; Last name: Kosse; Contact:

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by botg » 2022-06-23 07:54

Please provide a log with the checkbox enabled. Which client software are you using?

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by tchicken » 2022-06-23 20:16

I use FileZilla client, log attached, thanks for your help

Attachments

filezilla-server.log: (3.23 MiB) Downloaded 43 times

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by tchicken » 2022-06-24 07:47

«Use the following host (leave empty to keep the defaule one)» contained an IP address, I deleted it, it didn’t solve the problem, I add the new log file as an attachment. thank you again for your precious help.

Attachments

filezilla-server.log: (3.25 MiB) Downloaded 32 times

botg: Site Admin; Posts: 34747; Joined: 2004-02-23 20:49; First name: Tim; Last name: Kosse; Contact:

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by botg » 2022-06-24 09:32

Are you using any firewalls or AV products? What happens if you completely uninstall them for a test?

wanakt: 500 Command not understood; Posts: 3; Joined: 2022-06-20 08:23; First name: Jay; Last name: Kim

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by wanakt » 2022-06-25 02:36

I am using only window defender.
As per your recommendation, I reinstalled FileZilla Server but it did not solve the problem.

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Post

by tchicken » 2022-06-25 09:12

Hi Botg,
it seems that we are 2 to have the same problem !
I just have Windows defender in Windows Server 2019.
Hi Wanakt, what is your server configuration ?

wanakt: 500 Command not understood; Posts: 3; Joined: 2022-06-20 08:23; First name: Jay; Last name: Kim

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

#10

Post

by wanakt » 2022-06-25 09:56

My settings on FileZilla Server are as follows;

server listeners : port 21, protocol Explicit FTP over TLS and insecure plain FTP
TLS certificate : Use a self-signed X.509 certificate
Minumum allowed TLS version : v1.2
use the default host for local connections : checked

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

#11

Post

by tchicken » 2022-06-28 05:09

Hi there,
Did any of you find a solution to our problem? I’m still stuck on my side!

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

#12

Post

by tchicken » 2022-06-28 06:38

Customer side :
I changed the active mode by default, here is the trace :

Statut : Déconnecté du serveur
Statut : Résolution de l’adresse de lesarcs.dyndns.org
Statut : Connexion à 82.65.91.6:21…
Statut : Connexion établie, attente du message d’accueil…
Statut : Initialisation de TLS…
Statut : Connexion TLS établie.
Statut : Connecté
Statut : Récupération du contenu du dossier…
Statut : Le serveur a envoyé une réponse passive avec une adresse non routable. Adresse remplacée par celle du serveur.
Commande : MLSD
Réponse : 150 About to start data transfer.
Erreur : Connection interrompue après 20 secondes d’inactivité
Erreur : Impossible de récupérer le contenu du dossier
Statut : Déconnecté du serveur
Statut : Résolution de l’adresse de lesarcs.dyndns.org
Statut : Connexion à 82.65.91.6:21…
Statut : Connexion établie, attente du message d’accueil…
Statut : Initialisation de TLS…
Statut : Connexion TLS établie.
Statut : Connecté
Statut : Récupération du contenu du dossier…
Statut : Le serveur a envoyé une réponse passive avec une adresse non routable. Adresse remplacée par celle du serveur.
Commande : MLSD
Réponse : 150 About to start data transfer.
Erreur : Affichage du contenu du dossier annulée par l’utilisateur

Coté server :

<Date> Info [Type] Message
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 [Response] 234 Using authentication type TLS.
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 [Command] USER genturfevo
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 [Response] 331 Please, specify the password.
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 [Command] PASS ****
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Response] 230 Login successful.
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Command] PWD
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Response] 257 «/» is current directory.
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Command] TYPE I
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Response] 200 Type set to I
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Command] PASV
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Response] 227 Entering Passive Mode (192,168,0,111,234,209)
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Command] MLSD
<28/06/2022 08:33:19> FTP Session 1145 176.170.75.47 genturfevo [Response] 150 About to start data transfer.
<28/06/2022 08:33:39> FTP Session 1145 176.170.75.47 genturfevo [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
<28/06/2022 08:33:39> FTP Session 1145 176.170.75.47 genturfevo [Status] Client did not properly shut down TLS connection
<28/06/2022 08:33:39> FTP Session 1145 176.170.75.47 genturfevo [Error] Control channel closed with error from source 0. Reason: ECONNABORTED — Connection aborted.
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Response] 220-FileZilla Server 1.4.1
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Response] 220 Please visit https://filezilla-project.org/
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Command] AUTH TLS
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Response] 234 Using authentication type TLS.
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Command] USER genturfevo
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Response] 331 Please, specify the password.
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 [Command] PASS ****
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Response] 230 Login successful.
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Command] PWD
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Response] 257 «/» is current directory.
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Command] TYPE I
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Response] 200 Type set to I
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Command] PASV
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Response] 227 Entering Passive Mode (192,168,0,111,234,210)
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Command] MLSD
<28/06/2022 08:33:39> FTP Session 1146 176.170.75.47 genturfevo [Response] 150 About to start data transfer.

Always this error : [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.

botg: Site Admin; Posts: 34747; Joined: 2004-02-23 20:49; First name: Tim; Last name: Kosse; Contact:

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

#13

Post

by botg » 2022-06-28 07:57

Your server is behind a NAT router. You need to tell the server your public IP address.

tchicken: 503 Bad sequence of commands; Posts: 20; Joined: 2022-06-21 14:44; First name: Michel; Last name: POULET

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

#14

Post

by tchicken » 2022-06-28 21:33

Like this ?

: IP.jpg (78.95 KiB) Viewed 4003 times

Nothing change :
<Date> Info [Type] Message
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 [Response] 234 Using authentication type TLS.
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 [Command] USER genturfevo
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 [Response] 331 Please, specify the password.
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 [Command] PASS ****
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Response] 230 Login successful.
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Command] PWD
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Response] 257 «/» is current directory.
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Command] TYPE I
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Response] 200 Type set to I
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Command] PASV
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Response] 227 Entering Passive Mode (82,65,91,6,244,221)
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Command] MLSD
<28/06/2022 23:23:02> FTP Session 2085 176.170.75.47 genturfevo [Response] 150 About to start data transfer.
<28/06/2022 23:23:22> FTP Session 2085 176.170.75.47 genturfevo [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
<28/06/2022 23:23:22> FTP Session 2085 176.170.75.47 genturfevo [Status] Client did not properly shut down TLS connection
<28/06/2022 23:23:22> FTP Session 2085 176.170.75.47 genturfevo [Error] Control channel closed with error from source 0. Reason: ECONNABORTED — Connection aborted.

with this option :

: IP2.jpg (79.77 KiB) Viewed 4003 times

Nothing change…

boco: Contributor; Posts: 26451; Joined: 2006-05-01 03:28; Location: Germany

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

#15

Post

by boco » 2022-06-28 23:16

You also need to select a custom port range (the one you have forwarded in your router). The checkbox is only for local connection and will not do anything in this case as the connection is from the outside.

### 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 ###

Источник

На главную
How
Ошибка GnuTLS -110: соединение TLS было неправильно разорвано

2023

Редактор:
Christopher Sullivan |
Написать мне

Я заметил, что одна из моих служб Windows не подключается к FTP-серверу на Unix-сервере, я запускал исполняемый файл на своем ПК, поскольку разработчик не регистрировал никаких ошибок, и я получал ошибку тайм-аута при попытке получить ответ от FTPWebRequest Объект в C #.

При попытке доступа к FTP-серверу с помощью Filezilla я получаю сообщение об ошибке

Ошибка GnuTLS -110: соединение TLS было неправильно разорвано.

Использование SFTP не вызывает этой ошибки, равно как и использование FTP в виде простого текста (небезопасно).

Я действительно не понимаю этого и отмечаю, что приложение работает нормально в течение многих лет, и это внезапно происходит примерно на 4 серверах.

Ошибка GnuTLS -110: соединение TLS было неправильно разорвано.

Это просто означает, что одноранговый узел просто закрыл сокет и не выполнил надлежащее завершение TLS. Некоторые сломанные клиенты или серверы делают это. Предполагая, что это сообщение относится к передаче данных, вы обычно можете проигнорировать это, потому что передача все равно была завершена, поэтому данные не были потеряны.

Использование SFTP не вызывает этой ошибки, равно как и использование FTP в виде простого текста (небезопасно).

Конечно, вы этого не понимаете, поскольку SFTP использует протокол SSH вместо TLS, а простой FTP вообще не выполняет шифрования, поэтому TLS тоже. И если нет TLS, вы не можете получить никаких ошибок TLS.

Я действительно не понимаю этого и отмечаю, что приложение работает нормально в течение многих лет, и это внезапно происходит примерно на 4 серверах.

Возможно, серверы просто изменились, т.е. либо они никогда раньше не поддерживали FTPS (то есть FTP с TLS, не путать с SFTP), либо теперь они переключились на неработающую реализацию.

Означает ли это, что объект FTPWebRequest в C # использует TLS для FTP-соединений?
@kolexinfos: поскольку он поддерживает TLS, он будет использовать его, если он включен (SSL и TLS — разные имена для одного и того же семейства протоколов). Но я думаю, что это не связано с вашей проблемой, о которой сообщается с Filezilla.

Если вы подключаетесь к серверу cPanel, вы можете временно решить эту проблему, включив «Сломанная совместимость с клиентом» в настройках Pure-FTP в WHM.

Источник

Перейти к контенту

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

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

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

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

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

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

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

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

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

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.

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).

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.

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 бронзовых знака

Получилось решить проблему только переключением способа шифрования — вместо «Использовать явный 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.

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 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

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

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 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

Источник

Describe the bug

We intermittently receive an GnuTLS recv error (-110): The TLS connection was non-properly terminated when refreshing a git repository, which is hosted in BitBucket with a publicly trusted DigiCert Inc .com cert. The issue occurs with Skip server verification both on and off. The issue also occurs on both manual and automatic (polling) refreshes of the repo. If the Refresh button on the UI is clicked immediately after the error, the repo is refreshed and the error message is cleared.

To Reproduce

The issue is completely intermittent and cannot be reproduced on demand.

Expected behavior

The TLS connection should be properly terminated

Version

argocd: v1.6.0+c10ae24
  BuildDate: 2020-06-16T22:41:56Z
  GitCommit: c10ae246ab02f1356147118a1979fedcd1ceb704
  GitTreeState: clean
  GoVersion: go1.14.1
  Compiler: gc
  Platform: darwin/amd64
argocd-server: v1.6.1+159674e
  BuildDate: 2020-06-19T00:41:05Z
  GitCommit: 159674ee844a378fb98fe297006bf7b83a6e32d2
  GitTreeState: clean
  GoVersion: go1.14.1
  Compiler: gc
  Platform: linux/amd64
  Ksonnet Version: v0.13.1
  Kustomize Version: {Version:kustomize/v3.6.1 GitCommit:c97fa946d576eb6ed559f17f2ac43b3b5a8d5dbd BuildDate:2020-05-27T20:47:35Z GoOs:linux GoArch:amd64}
  Helm Version: version.BuildInfo{Version:"v3.2.0", GitCommit:"e11b7ce3b12db2941e90399e874513fbd24bcb71", GitTreeState:"clean", GoVersion:"go1.13.10"}
  Kubectl Version: v1.14.0

Logs

time="2020-07-23T17:00:52Z" level=info msg="git fetch origin --tags --force" dir="/tmp/https:__bitbucket.bdreporting.com_scm_devops_k8s" execID=AbVhO
time="2020-07-24T15:12:47Z" level=error msg="`git fetch origin --tags --force` failed exit status 128: error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated." execID=wiKJC
time="2020-07-24T15:12:47Z" level=error msg="finished unary call with code Internal" error="rpc error: code = Internal desc = Failed to fetch git repo: `git fetch origin --tags --force` failed exit status 128: error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated." grpc.code=Internal grpc.method=GenerateManifest grpc.request.deadline="2020-07-24T15:13:46Z" grpc.service=repository.RepoServerService grpc.start_time="2020-07-24T15:12:46Z" grpc.time_ms=675.091 span.kind=server system=grpc

Repo Confg

  repositories: |
    - passwordSecret:
        key: password
        name: repo-4290583797
      type: git
      url: https://bitbucket.bdreporting.com/scm/devops/k8s.git
      usernameSecret:
        key: username
        name: repo-4290583797

Источник

Я готовлюсь к установке плагина vim с помощью vundle после того, как я установил vimrc

set nocompatible
filetype off
set rtp+=~/.vim/bundle/Vundle.vim

call vundle#begin()

Plugin 'gmarik/Vundle.vim'
Plugin 'valloric/youcompleteme'

call vundle#end()

Затем я ввожу :PluginInstall и получаю сообщение об ошибке

  2 [2018-09-27 10:47:17] Plugin valloric/youcompleteme                                                | 18 " line enables syntax highlighting by default.
  3 [2018-09-27 10:47:17] $ git clone --recursive 'https://github.com/valloric/youcompleteme.git' '/roo| 19 syntax on;
    t/.vim/bundle/youcompleteme'                                                                       | 20 if has("syntax")
  4 [2018-09-27 10:47:17] > Cloning into '/root/.vim/bundle/youcompleteme'...                          | 21   syntax on
  5 [2018-09-27 10:47:17] > error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was| 22 endif
     non-properly terminated.

А затем я перехожу в каталог ~/.vim/bundle и выполняю

git clone --recursive 'https://github.com/valloric/youcompleteme.git

И получить это

Cloning into '~/.vim/bundle/youcompleteme'...
remote: Enumerating objects: 15, done.
remote: Counting objects: 100% (15/15), done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 34431 (delta 4), reused 8 (delta 1), pack-reused 34416
Receiving objects: 100% (34431/34431), 32.58 MiB | 2.37 MiB/s, done.
error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.
Resolving deltas: 100% (12305/12305), done.

Как сказано в this, кажется, что плагин были загружены, несмотря на ошибку. Но на самом деле я не могу найти каталог youcompleteme.

Я тоже стараюсь

git clone --recursive 'git@github.com:Valloric/YouCompleteMe.git' '~/.vim/bundle/youcompleteme'

И получить это

Cloning into '~/.vim/bundle/youcompleteme'...
ssh: connect to host github.com port 22: Connection timed out
fatal: Could not read from remote repository.

Так как это решить?

2 ответа

Лучший ответ

Перекомпилируйте и установите git, решите это, наконец, шаги следующие:

sudo apt-get install build-essential fakeroot dpkg-dev -y
sudo apt-get build-dep git -y
sudo apt-get install libcurl4-openssl-dev -y
cd ~
mkdir source-git
cd source-git/
apt-get source git
cd git-2.*.*/
sed -i -- 's/libcurl4-gnutls-dev/libcurl4-openssl-dev/' ./debian/control
sed -i -- '/TESTs*=s*test/d' ./debian/rules
dpkg-buildpackage -rfakeroot -b -uc -us
sudo dpkg -i ../git_*ubuntu*.deb

И не использовать -y — это нормально, -y просто для пропуска ввода y. Результат:

Cloning into 'syntastic'...
remote: Enumerating objects: 27, done.
remote: Counting objects: 100% (27/27), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 18671 (delta 9), reused 16 (delta 5), pack-reused 18644
Receiving objects: 100% (18671/18671), 4.26 MiB | 701.00 KiB/s, done.
Resolving deltas: 100% (10572/10572), done.
Checking connectivity... done.

G.yx
27 Сен 2018 в 06:29

Так как это решить?

Проверяя, сохранятся ли эти ошибки в течение следующих нескольких часов.

Статус GitHub прямо сейчас

Мы изучаем сообщения о повышенном уровне ошибок.

И это могло быть побочным эффектом их проблем.

Другой подход — убедиться, что вы используете последнюю версию Git, что OP сделал путем перекомпиляции Git.

VonC
27 Сен 2018 в 06:20

Источник

GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

Re: GnuTLS error -110 in gnutls_record_recv: The TLS Connection was non-properly terminated

GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Re: GnuTLS error -110: The TLS connection was non-properly terminated

Question

Answer

Product Synonym

2 ответа

Читайте также: