Resolve FTP EAI_NODATA error
In this article I'm going to review why you might be encountering an EAI_NODATA - No address associated with nodename error in your FTP client. Sometimes an EAI_NODATA error is also related to either a EHOSTUNREACH error, or an ECONNABORTED error as well.
These are common FTP errors that occur when your domain name is not registered and pointing to a web server. Also sometimes if you just recently changed where your domain name is hosted at, your FTP client can cache private data settings from the old connection. This could prevent you from connecting to the correct server.
When DNS changes are made to your domain name, this changes the physical server your domain's website files are hosted on. These changes can take up to 24 hours to fully propagate, and especially after updating your domain's name servers you might get the EAI_NODATA error within your FTP program
Fixing EAI_NODATA error
The steps below should be able to resolve the EAI_NODATA - No address associated with nodename error from happening. There are two methods in which you can utilize to try to prevent this error from happening to you.
The easiest method would simply be to find your server name in cPanel, then in the hostname field of your FTP client, use that server name.
This would ensure that your FTP client is directly connecting to our web server that hosts your website, and it wouldn't have to rely on any recent changes to your domain name's DNS setting.
If your server was biz104 for instance, you would want to use the hostname biz104.inmotionhosting.com to be able to connect.
To try to resolve the EAI_NODATA error and keep using your domain name, you'd want to clear out the private data associated with that connection in your FTP client.
In this example we're going to be using FileZilla.
Hopefully this fixes any common FTP errors like EAI_NODATA, EHOSTUNREACH, or ECONNABORTED. If for some reason you're still having issues you should still be able to upload a file using File Manager in cPanel as well.
We value your feedback!
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
new! - Enter your name and email address above and we will post your feedback in the comments on this page!
2014-04-09 11:16 am
Hi, very easy instructions to follow and understand, no problem there. When I tried passive set up and test I got aborted error. When I tried Active I get 503 error.
2014-04-09 7:30 pm
It sounds like you are more than likely encountering a firewall issue. Do you currently have any firewall software running on the computer that you're trying to establish an FTP connection from?
Have you been able to FTP from your current computer to any other FTP servers, or are you just having a problem connecting to your website's FTP account?
2014-07-09 3:25 am
It is good enough, very simple and clear. Thank you so much!
2014-07-29 4:20 pm
Had this error, this fixed it like a charm (the three steps for Filezilla above) - so thanks!
2014-09-26 7:35 am
ECONNREFUSED - Connection refused by server"I'm getting the above error and followed the insturctions in http://www.inmotionhosting.com/support/community-support/file-management/how-do-i-fix-a-connection-refused-error-in-filezillabut it didn't work. I also tried to turn off the firewall. The surprising thing is that I can access other servers from the same program bar one
2014-09-26 10:12 am
Thank you for contacting us. In the Official FileZilla forums, they discuss several other solutions. Aside from the firewall, they recommend checking your anti-virus.
We are happy to help, but will need some additional information. Have you made any DNS changes recently to the domain you are connecting to?
Have you confirmed domain's nameservers/DNS are pointed to the right location?
If you have any further questions, feel free to post them below.
2015-03-25 6:50 pm
I had this problem, but the solution was much simpler since it was a silly mistake from me.
I had written as host: ftp.mydomain.com.
When I changed it to just mydomain.com without ftp in front, it worked.