That worked for me too. Did not add the @.. part . Now I can access the GoDaddy site by ip address as well. Thanks for leaving this post!Maquis wrote:Had the same problem, fixed it by adding domain to the user.
instead of <username>
I used <username>@<domain>
For example:
Maquis@example.com
530 Login authentication failed
Moderator: Project members
Re: 530 Login authentication failed
-
- 500 Command not understood
- Posts: 1
- Joined: 2020-04-25 13:52
- First name: Jibagast
- Last name: Mdosi
Re: 530 Login authentication failed
Initially I was able to use the FTP xml config file to setup the ftp connection which logged in ok, however when I tried to log back in I would get the 530 Login authentication failed error even after creating a new account and reseting the password serveral times.
Then while going back and forth I noticed looking at the file permissions on Godaddy this was a Unix server, so I changed the server type from (Default Auto Detect) to Unix
Under Site Manager -> Advanced -> Site type ( Your Server may differ so select )
Hope this helps.
Then while going back and forth I noticed looking at the file permissions on Godaddy this was a Unix server, so I changed the server type from (Default Auto Detect) to Unix
Under Site Manager -> Advanced -> Site type ( Your Server may differ so select )
Hope this helps.
- Attachments
-
- Setup.gif (33.39 KiB) Viewed 1242 times
Re: 530 Login authentication failed
@jibagast: The server type only affects the path syntax, it has no bearing on the login process.
-
- 500 Command not understood
- Posts: 1
- Joined: 2020-05-20 13:56
- First name: Debbie
- Last name: Heath
Re: 530 Login authentication failed
I had this issue also and i was entering all of the correct information like domain, username and password etc.
Turned out to be IP restricted and since i was now working from home, I advised my company IT manager of my home IP address which he then white-listed. Now it works.
Thought I would post this (probably obvious to most) solution, just incase it helps any others out there who not overly clued up about these things - like me
Turned out to be IP restricted and since i was now working from home, I advised my company IT manager of my home IP address which he then white-listed. Now it works.
Thought I would post this (probably obvious to most) solution, just incase it helps any others out there who not overly clued up about these things - like me