Opened 18 years ago
Last modified 11 years ago
#1100 closed Bug report
Listen to SSL/TSL-connections feature seems to be broken
Reported by: | silviang | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Server |
Keywords: | Cc: | silviang, Tim Kosse | |
Component version: | Operating system type: | ||
Operating system version: |
Description
Hello,
I have been instructed by the developer
from "2brightsparks" (the SyncBackSE backup tool
developers) to contact you about this issue.
What is going on is that when I activate the "Use
implicit connection (port 990)" in SyncBackSE I get
an error message like this on the client (SyncBackSE)
side:
"Connect failed: SSL/TSL (18):.Please check your FTP
settings and network connection"
And on the server side on the console I see the
following:
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> Connected, sending welcome message...
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 220-FileZilla Server version 0.9.18
beta
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 220-written by Tim Kosse
(Tim.Kosse@…)
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 220 Please visit
http://sourceforge.net/projects/filezilla/
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> €L
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 3
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> €
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> À
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> €
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> @
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> d
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> b
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> €
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> €
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)>
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> 500 Syntax error, command
unrecognized.
(000002) 5/31/2006 7:50:13 AM - (not logged in)
(192.168.1.100)> disconnected.
The SyncBackSE developer, Michael J. Leaver, looked
at the above report and he replied the following:
"With 0.9.16c beta I could not reproduce this issue,
but on newer versions of Filezilla it does fail. ...
Please contact Filezilla support to get the issue
resolved."
That is why I am filing this bug report.
Thank you,
Silvian
Change History (4)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Hello,
I have not changed that setting in my case. And the
default is 990. Is there some file I can send you to have
all this setting information?
Also the SyncBackSE developer (Michael J. Leaver) has been
able to reproduce this as well and he did that in his own
environment.
Please let me know what else is needed to debug this
report. Thank you,
Silvian
comment:3 by , 18 years ago
Can you please toggle the server online status in the admin
interface and post the resulting output from the log?
Also, please attach the <Settings> section from the
FileZilla Server.xml (but please edit out the admin password
prior to posting) to this bug replort.
One more test, open a command promt in Windows and type
"telnet 127.0.0.1 990" (without the quotes)
Will you see the FTP welcome message then?
comment:4 by , 18 years ago
I am closing this report as I discovered that I have to
change the port on the lcinet to 990 as well...
Thank you,
Silvian
Works for me, are you sure you've set port 990 as SSL/TLS
port and not as normal FTP port inside the admin interface?