Possible Common error in Filezilla software!

File transfer to be done from the local computer to the web hosting account is said to be as publication or uploading and for the purpose file transfer protocol is needed to be used. In case the application that is being used to design the website does not have FTP client then user has to download a software so as to upload the website pages.

Filizilla is the most easy solution for such task as it is featured with graphical user interface turning the file transfer in between the local machine and the remote system more easier. One needs to set up the FTP connection and transfer the files from system to remote machine.

Although Filezila serves as the best FTP software however there are times common Errors in Filezilla do occur causing trouble for the user and are as below:-

Error 53(Login Incorrect):-

The problem occurs quite often due to use of incorrect username and password. In order to get rid of the error one needs to ensure that the username and password are correct. The logs associated with connection will show following response;-
Response: 220 ProFTPD FTP Server ready.
Command: USER admin67890
Response: 331 Password required for admin67890
Command: PASS ******
Response: 530 Login incorrect.
Error: Critical error
Error: Could not connect to server

Could not connect to server Error:-

The error is found to occur while the hostname specified is incorrect. Although the mistake is found to occur because of typing mistake however sometimes it does happen due to DNS issues on user PC or that of the internet service providers system and so on results following problems :-
Status: Resolving address of server.microle24.com
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error: Could not connect to server
Status: Waiting to retry...

Unable to update website:-

While this problem occurs no error message is displayed on the screen and even the website seems to appear usual but while one tries to view the webpage via browser it shows 'holding page' as default. There might be several reason behind this problem and are as below;-

• Not having the 'default remote directory' in '/httpdocs' advanced settings menu.
• The default index.html page is not overwritten by the homepage so one has to delete the useless index.html page.
• Presence of capital letter in the homapage address so it is necessary to have all the letter in lowercase.