Opened 9 years ago

Closed 7 years ago

Last modified 6 years ago

#7835 closed Bug report (invalid)

530 error

Reported by: Albert Myers Owned by:
Priority: normal Component: FileZilla Client
Keywords: 530 Login incorrect Cc: albert1705@…
Component version: Operating system type: Windows
Operating system version: Windows 7 Service Pack 1

Description

Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 2 of 50 allowed.
Response: 220-Local time is now 07:12. Server port: 21.
Response: 220-IPv6 connections are also welcome on this server.
Response: 220 You will be disconnected after 15 minutes of inactivity.
Command: USER aemyers1
Response: 331 User aemyers1 OK. Password required
Command: PASS
Response: 530 Login authentication failed
Error: Critical error
Error: Could not connect to server

Change History (7)

comment:1 by Alexander Schuch, 8 years ago

Keywords: Login incorrect added; error removed
Resolution: invalid
Status: newclosed

Did you try another FTP client just to check that the server even accepts the password?

comment:2 by Yegg, 7 years ago

Resolution: invalid
Status: closedreopened

I am facing the same problem with the actual FileZilla 3.0.6.2
(running on a 64bit Windows 7 SP1 with recent patches).

When connecting (in passive mode) to a "PureFTPd" Server running
with "-Y 1" (Accept both normal sessions and SSL/TLS ones.)
I get exactly the same behavior as described above:

Status: Connection established, waiting for welcome message...
Trace: CFtpControlSocket::OnReceive()
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 13 of 50 allowed.
Response: 220-Local time is now 15:35. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220-IPv6 connections are also welcome on this server.
Response: 220 You will be disconnected after 15 minutes of inactivity.
Trace: CFtpControlSocket::SendNextCommand()
Command: AUTH TLS
Trace: CFtpControlSocket::OnReceive()
Response: 234 AUTH TLS OK.
Status: Initializing TLS...
Trace: CTlsSocket::Handshake()
Trace: CTlsSocket::ContinueHandshake()
Trace: CTlsSocket::OnSend()
Trace: CTlsSocket::OnRead()
Trace: CTlsSocket::ContinueHandshake()
Trace: CTlsSocket::OnRead()
Trace: CTlsSocket::ContinueHandshake()
Trace: CTlsSocket::OnRead()
Trace: CTlsSocket::ContinueHandshake()
Trace: TLS Handshake successful
Trace: Cipher: AES-256-CBC, MAC: SHA1
Status: Verifying certificate...
Trace: CFtpControlSocket::SendNextCommand()
Command: USER yegg
Status: TLS/SSL connection established.
Trace: CTlsSocket::OnRead()
Trace: CFtpControlSocket::OnReceive()
Response: 331 User yegg OK. Password required
Trace: CFtpControlSocket::SendNextCommand()
Command: PASS *
Trace: CTlsSocket::OnRead()
Trace: CFtpControlSocket::OnReceive()
Response: 530 Login authentication failed
Trace: CControlSocket::DoClose(1094)
Trace: CFtpControlSocket::ResetOperation(1094)
Trace: CControlSocket::ResetOperation(1094)
Error: Critical error
Error: Could not connect to server
Trace: CFileZillaEnginePrivate::ResetOperation(1094)
...

When using a "lftp" command line client with the same credentials
I can successfully login

lftp
lftp :~> open <host>
lftp ftp.orbiteam.de:~> user yegg <passwd>
lftp yegg@…:~> ls
...

The pure-ftpd logs the following:

Jan 25 15:51:12 <server> pure-ftpd: (?@<client>) [INFO] New connection from <client>
Jan 25 15:51:12 <server> pure-ftpd: (?@<client>) [INFO] SSL/TLS: Enabled TLSv1/SSLv3 with DHE-RSA-AES256-SHA, 256 secret bits cipher
Jan 25 15:51:15 <server> pure-ftpd: (?@<client>) [WARNING] Authentication failed for user [yegg]
Jan 25 15:51:15 <server> pure-ftpd: (?@<client>) [INFO] Logout.

This bug was already reported several times here:

#7896 #7951 #7974 #7976 #8028

but has always been marked as 'invalid'. Unfortunately it is very valid for me.

Regards,
--Yegg

in reply to:  2 comment:3 by Yegg, 7 years ago

Replying to Yegg:

lftp
lftp :~> open <host>
lftp ftp.orbiteam.de:~> user yegg <passwd>
lftp yegg@…:~> ls
...

The pure-ftpd logs the following:

Jan 25 15:51:12 <server> pure-ftpd: (?@<client>) [INFO] New connection from <client>
Jan 25 15:51:12 <server> pure-ftpd: (?@<client>) [INFO] SSL/TLS: Enabled TLSv1/SSLv3 with DHE-RSA-AES256-SHA, 256 secret bits cipher
Jan 25 15:51:15 <server> pure-ftpd: (?@<client>) [WARNING] Authentication failed for user [yegg]
Jan 25 15:51:15 <server> pure-ftpd: (?@<client>) [INFO] Logout.

Oops, to prevent misunderstandings: pure-ftpd logged the above for FileZilla. Using "lftp" it logs

Jan 25 15:59:05 <sever> pure-ftpd: (?@<client>) [INFO] New connection from <client>
Jan 25 15:59:05 <sever> pure-ftpd: (?@<client>) [INFO] SSL/TLS: Enabled TLSv1/SSLv3 with DHE-RSA-AES128-SHA, 128 secret bits cipher
Jan 25 15:59:06 <sever> pure-ftpd: (?@<client>) [INFO] yegg is now logged in
Jan 25 15:59:06 <sever> pure-ftpd: (yegg@<client>) [INFO] SSL/TLS: Enabled TLSv1/SSLv3 with DHE-RSA-AES128-SHA, 128 secret bits cipher

Regards,
--Yegg

comment:4 by Alexander Schuch, 7 years ago

Status: reopenedmoreinfo_reopened

Do you have any non 7 bit US-ASCII character in your password?

in reply to:  4 comment:5 by Yegg, 7 years ago

Status: moreinfo_reopenedreopened

Replying to ci-dev:

Do you have any non 7 bit US-ASCII character in your password?

no. I just have a plain random us-ascii password.

comment:6 by Alexander Schuch, 7 years ago

Status: reopenedmoreinfo_reopened

Can you use Wireshark or another network sniffer at your end with non-encrypted FTP and check that the proper password is transmitted? Maybe you have set another keyboard layout only for FileZilla application and thus are mistyping the password all the time?

in reply to:  6 comment:7 by Yegg, 7 years ago

Resolution: invalid
Status: moreinfo_reopenedclosed

Replying to ci-dev:

Can you use Wireshark or another network sniffer at your end with non-encrypted FTP and check that the proper password is transmitted? Maybe you have set another keyboard layout only for FileZilla application and thus are mistyping the password all the time?

yo've been right, with the correct password it works (confusion due differnt keyboard layouts windows/unix); mea culpa

Note: See TracTickets for help on using tickets.