Page 3 of 5

Re: 530 Login authentication failed

Posted: 2012-03-05 10:23
by shital sakhare
this issues is regarding the server security. in cpanel whm such a security is provided . its a host access control in WHM. if such access control list is being provided then their will not possible to log in using filezilla or using any of the FTP-client. for that you have to request to server administrator to allow his IP to connect via FTP

Re: 530 Login authentication failed

Posted: 2012-03-15 20:09
by pheobes18
Currently there are 5 people connecting to our FTP using the same log-in information. Everyone is able to connect except for me. I contacted our support person and they said all my user/pw information is correct. They even created a new log-in for me to connect. It still won't allow me to connect. I have disabled my firewall, made exceptions for the ports and am still not able to connect. They have checked my IP and I am not banned.

Any ideas as to why I can't connect & what I can do to fix this?

Re: 530 Login authentication failed

Posted: 2012-03-17 00:44
by rdndr
I'm having the login problem, as well - 331 Password required, and 530 user cannot log in. Forgive my ignorance, I am not even close to understanding a lot of what I'm doing, but what I've done works. Until today. (I'm also not following some of the language used in this topic.)

I have been using FileZilla version 3.0.11.1 on my Mac under Leopard very successfully. I use this program about twice a year. Since I last used it, I have upgraded my OS to 10.6.8 (Snow Leopard); I have not updated FileZilla or NVU (where I edit my pages). I have verified that I'm using the correct host/user/password about 15 times, so that's not my problem. Could my OS X upgrade be causing my problem? If so, would the update to latest version of FileZilla Client help?

Thanks!

Re: 530 Login authentication failed

Posted: 2012-03-17 00:47
by rdndr
Forgot to mention that I also can't drag any files into the upload queue.

Re: 530 Login authentication failed

Posted: 2012-03-17 02:52
by boco
Note that 3.0.11.1 is unsupported.

The 530 message is coming from the server. It cannot log you in for some reason. Which, it doesn't tell.

Re: 530 Login authentication failed

Posted: 2012-06-15 08:39
by NatSui
Hi all
I haven't found any answer anywhere for a special problem:
In our company all internet traffic is proxied with authentication (no anonymous connections allowed) including ftp connections.
In Filezilla (v. 3.5.3) configuration (connections -> ftp -> ftp-proxy) we had therefore to configure following user defined settings for authentication to work:

Code: Select all

USER %u@%h %s
PASS %p
ACCT %w 
With these settings usually everything works fine.

Problem starts with an external ftp account like:
ftp server: host.example.com
ftp user name: XYZ@example.com
ftp user password: somepassword

Is it possible to define an escape character for the '@' in the username?

Because this way the request with the proxy settings looks like

Code: Select all

Status:	connecting with proxyserverip:21...
Status:	connected, waiting for wellcome..
Answer:	220 Proxy FTP Service
Command:	USER XYZ@example.com@host.example.com Domain\DomainUser
Answer:	331 Enter password.
Command:	PASS ********
Answer:	332 Enter proxy password.
Command:	ACCT *********
Answer:	530 Login authentication failed
If the ftp username doesn't contain an '@' everything works fine. but with an '@' Filezilla thinks ftp user is only XYZ and ftp server is example.com@host.example.com.

Is there a way to change this behavior?

Re: 530 Login authentication failed

Posted: 2012-06-16 22:12
by botg
If the ftp username doesn't contain an '@' everything works fine. but with an '@' Filezilla thinks ftp user is only XYZ and ftp server is example.com@host.example.com.
Actually its the server that interprets this, FileZilla merely assembles the argument to the USER command, it does not parse it.

Unfortunately there is no escape character. Please note that FTP proxies are not standardized, they are not covered by the FTP specifications.

Re: 530 Login authentication failed

Posted: 2012-06-18 08:59
by NatSui
Thank you for the fast reply.
I've been expecting it...
We will try to receive a username without '@' from the external partner...

Re: 530 Login authentication failed

Posted: 2012-08-02 11:51
by eamonmoriarty
I was baffled that I had some ftp connections on Filezilla which were working OK but most new ones that I created would not connect and gave 530 login failed errors.
I had been copying and pasting the username, password etc directly from cpanel to ensure that I got it right.
I then got the bright idea to first paste it into a Plain Text Document and then copy it from there to Filezilla.
Voila! All previous failures working!
I presume direct copy and past from cpanel is introducing some unwanted formatting.

Re: 530 Login authentication failed

Posted: 2012-08-03 00:35
by boco
I presume direct copy and past from cpanel is introducing some unwanted formatting.
Yes, most probably leading or trailing blanks. Browsers just love to copy these along, and you won't be able to spot them even if you see the copied string, as blanks are... well.... blank/invisible.

Re: 530 Login authentication failed

Posted: 2012-11-19 04:28
by RandyT
Unencrypted FTP works OK, but when I attempt to use Explicit FTP over TLS, I get the 530 Login authentication failed.
I installed Cyberduck, imported the same site parameters from Filezilla and it worked OK.
It appears that Filezilla 3.6.0 on Windows 7 has a problem with encrypted connections.

Re: 530 Login authentication failed

Posted: 2012-11-19 07:35
by botg
Login is exactly the same with plain FTP and FTP over TLS in FileZilla. If it works with plain FTP and not with FTP over TLS, you either entered something different or it's a problem with the server.

Re: 530 Login authentication failed

Posted: 2012-11-19 18:33
by RandyT
I used stored host parameters, so login was the same except for adding encryption. Apparently it's a (Yahoo) server problem, as later attempts with CyberDuck didn't work either. Don't know why it worked the first time, unless CD didn't pick up the TLS flag the first time. Yahoo Small Business has indicated they wouldn't accept non-encrypted connections after September, but they still work, so I guess I'll stick with that for now.
Thanks for the reply.

Re: 530 Login authentication failed

Posted: 2012-11-22 02:29
by Pepdeal
Thanks for sharing.My site is now working fine

Re: 530 Login authentication failed

Posted: 2013-04-03 21:04
by frankieb
fixed it! apparently filezilla doesn't like special characters in passwords like @#$%+ etc...

changed my password to something WITHOUT any special characters and voila! instant connection!

good luck