Opened 16 years ago
Closed 16 years ago
#4404 closed Bug report (rejected)
No TLS-Encrypted connection possible
Reported by: | lsmod | Owned by: | |
---|---|---|---|
Priority: | low | Component: | FileZilla Client |
Keywords: | Cc: | ||
Component version: | Operating system type: | Windows | |
Operating system version: |
Description
I have configured my ProFTPD correct for working behind a firewall.
So MasqueradeAddress and PassivePorts is set.
Also a normal not encrypted connection is working in pasv-mode without any problems.
But using FTPES with TLS-Encryption always failed.
There are several descriptions that this is a known bug and should be fixed in future Filezilla-versions.
But now i am using a "future-version" 3.2.3.1 and it is still not working. :-(
Here the output from the connection:
====================================
Status: Auflösen der IP-Adresse für mydomain.mydyn.de
Status: Verbinde mit 84.60.43.26:21...
Status: Verbindung hergestellt, warte auf Willkommensnachricht...
Antwort: 220 FTP server ready.
Befehl: AUTH TLS
Antwort: 234 AUTH TLS successful
Status: Initialisiere TLS...
Status: Überprüfe Zertifikat...
Befehl: USER intern
Status: TLS/SSL-Verbindung hergestellt.
Antwort: 331 Password required for intern.
Befehl: PASS
Antwort: 230 User intern logged in.
Befehl: PBSZ 0
Antwort: 200 PBSZ 0 successful
Befehl: PROT P
Antwort: 200 Protection set to Private
Status: Verbunden
Status: Empfange Verzeichnisinhalt...
Befehl: PWD
Antwort: 257 "/" is current directory.
Befehl: TYPE I
Antwort: 200 Type set to I
Befehl: PASV
Antwort: 227 Entering Passive Mode (192,168,1,3,53,66).
Status: Vom Server gesendete Adresse für den Passiv-Modus ist nicht routingfähig. Benutze stattdessen die Serveradresse.
Befehl: LIST
Antwort: 150 Opening ASCII mode data connection for file list
Status: Server hat die TLS-Verbindung nicht ordnungsgemäß geschlossen
Fehler: Could not read from transfer socket: ECONNABORTED - Connection aborted
Antwort: 226 Transfer complete.
Fehler: Verzeichnisinhalt konnte nicht empfangen werden
Change History (1)
comment:1 by , 16 years ago
Priority: | high → low |
---|---|
Resolution: | → rejected |
Status: | new → closed |
Broken server. You have to contact the server administrator so that he can install a more recent version.
In addition the server is not properly configured. You have to contact the server administrator so that he can fix the configuration.