Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Moderator: Project members
-
- 504 Command not implemented
- Posts: 11
- Joined: 2020-08-18 12:57
- First name: Sergey
- Last name: Bakiev
Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
This error started to occur when connecting to the Filezilla FTP server via the Filezilla client. Help me understand what the reason might be.
Status: Connecting*******
Status: Connection established, waiting for welcome message...
Command: AUTH TLS
Response: 234 Using authentication type TLS
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER *****
Response: 331 Password required for ******
Command: PASS **********
Response: 230 Logged on
Command: SYST
Response: 215 UNIX emulated by FileZilla
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type*;size*;modify*;
Response: MLSD
Response: AUTH SSL
Response: AUTH TLS
Response: PROT
Response: PBSZ
Response: UTF8
Response: CLNT
Response: MFMT
Response: EPSV
Response: EPRT
Response: 211 End
Command: PBSZ 0
Response: 200 PBSZ=0
Command: PROT P
Response: 200 Protection level set to P
Status: Authorized
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (10,128,35,32,195,89)
Command: MLSD
Response: 150 Opening data channel for directory listing of "/"
Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Error: Could not read from socket: ECONNABORTED - Connection aborted
Response: 426 Connection closed; aborted transfer of "/"
Error: Failed to retrieve directory listing
Status: Connecting*******
Status: Connection established, waiting for welcome message...
Command: AUTH TLS
Response: 234 Using authentication type TLS
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER *****
Response: 331 Password required for ******
Command: PASS **********
Response: 230 Logged on
Command: SYST
Response: 215 UNIX emulated by FileZilla
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type*;size*;modify*;
Response: MLSD
Response: AUTH SSL
Response: AUTH TLS
Response: PROT
Response: PBSZ
Response: UTF8
Response: CLNT
Response: MFMT
Response: EPSV
Response: EPRT
Response: 211 End
Command: PBSZ 0
Response: 200 PBSZ=0
Command: PROT P
Response: 200 Protection level set to P
Status: Authorized
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (10,128,35,32,195,89)
Command: MLSD
Response: 150 Opening data channel for directory listing of "/"
Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Error: Could not read from socket: ECONNABORTED - Connection aborted
Response: 426 Connection closed; aborted transfer of "/"
Error: Failed to retrieve directory listing
-
- 504 Command not implemented
- Posts: 11
- Joined: 2020-08-18 12:57
- First name: Sergey
- Last name: Bakiev
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
connecting to FileZilla Server 0.9.60 beta on Windows server 2012 r2
Use Filezilla client
----------------
Version: 3.49.1
Build information:
Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2020-07-15
Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406
Compiler flags: -g -O2 -Wall
Linked against:
wxWidgets: 3.0.6
SQLite: 3.31.1
GnuTLS: 3.6.14
Operating system:
Name: Windows 10 (build 17763), 64-bit edition
Version: 10.0
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 lm
Settings dir: C:\Users\Adun\AppData\Roaming\FileZilla\
Use Filezilla client
----------------
Version: 3.49.1
Build information:
Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2020-07-15
Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406
Compiler flags: -g -O2 -Wall
Linked against:
wxWidgets: 3.0.6
SQLite: 3.31.1
GnuTLS: 3.6.14
Operating system:
Name: Windows 10 (build 17763), 64-bit edition
Version: 10.0
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 lm
Settings dir: C:\Users\Adun\AppData\Roaming\FileZilla\
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Are you any firewalls? What happens if you completely disable, or better yet uninstall them for a test?
-
- 504 Command not implemented
- Posts: 11
- Joined: 2020-08-18 12:57
- First name: Sergey
- Last name: Bakiev
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Only Windows firewall. Disabling it, the problem persists, and adding exception rules (access to everything) didn't help either.
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Do you still experience it in 3.50.0?
-
- 504 Command not implemented
- Posts: 11
- Joined: 2020-08-18 12:57
- First name: Sergey
- Last name: Bakiev
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
There are still some ideas, the problem has not been solved. Tell me at least in which direction to look
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Try installing a more modern CPU in the computer running the client.
-
- 504 Command not implemented
- Posts: 11
- Joined: 2020-08-18 12:57
- First name: Sergey
- Last name: Bakiev
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
checked on a PC with i5 7400t and 16 gb, same error occurs.
-
- 504 Command not implemented
- Posts: 11
- Joined: 2020-08-18 12:57
- First name: Sergey
- Last name: Bakiev
Re: Error: Error GnuTLS -18: An error was encountered at the TLS Finished packet calculation.
Thank you very much for your advice. The problem turned out to be on the provider's firewall hardware. The application filter on port 21 was incorrectly configured.