Filezilla Connection Attempt Failed - EAI_NONAME - Neither nodename nor servname provided, or not known

Avatar
kristinad
  • updated
  • Answered

I'm not able to connect to my site/servers via FTP. I've checked, and my name servers are pointing to Inmotion. Any other ideas why Filezilla isn't recognizing the server name?

Status: Resolving address of ftp.kristinad.com
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error: Could not connect to server

Pinned replies
Avatar
0
anonymous
  • Answer
  • Answered

Solution: Connection Attempt Failed With “eai_noname - Neither Nodename nor Servname Provided, or Not Known”

Sorry that you're running into trouble connecting to FTP with Filezilla! Here are some troubleshooting steps to help you solve the following error: connection attempt failed with "eai_noname - neither nodename nor servname provided, or not known".

Verify Your FTP Settings

As long as your FTP Username, Password, and Port (21) are correct, you should be able to resolve to your server and connect. As a test you can try removing the "ftp." from the beginning of your domain as this subdomain may be pointed to a different server from your main domain. So, instead of ftp.example.com use example.com.

Check Your DNS

If your settings are accurate and you are still not able to connect, the most likely problem is something DNS related. This could come down to issues with a CDN like Cloudflare, or just a recent DNS change not having synced up somewhere yet, known as propagation (common if a site was recently transferred).

Connect With Server Hostname

One reliable workaround is to switch out the domain you are using with your server's hostname, since it should resolve directly to your server. Just look up your hostname in the Account Technical Details section of AMP, and use that in the place where you previously put your domain name. It should look something like ecbiz###.inmotionhosting.com, biz###.inmotionhosting.com, vps####.inmotionhosting.com, or something else along those lines (with the numbers replaced by the actual server numbers). Try that and hopefully it will resolve the issue!

Connect With IP Address

Another option is to use your servers IP address instead of your domain name or server hostname. You can view this IP address on the right side of cPanel.

Review Your FTP Logs

If your problems persist, you can review your server's FTP logs. Any time you connect to your server or transfer files, it will create a log entry listing what was done. If you don't see any records, your connection is failing before it resolves to the server.

If you are seeing FTP logs from your IP address it should provide additional details such as a success or error message.

Replies 5
Avatar
0
anonymous
Quote from steve mills

I have this same problem. I've tried everything mentioned; full domain name with and without ftp., the Server Name, and shared IP address. I've tried every type of login and encryption in FileZilla, all the various options in the Site Manager window. Nothing works, just keep getting the exact same error every time when it tries to connect: "EAI_NONAME - Neither nodename nor servname provided, or not known".

I can connect with Fetch, but I don't want to buy it just so I can use an inferior ftp app. FileZilla does side-by-side comparison so it's easy to only upload changed files. This needs to be resolved.

Hi, Steve. Sorry you're having FileZilla related trouble. 

I'd suggest checking the FTP Error Logs (in cPanel is the easiest method if you have an account with cPanel)  to see what specific error is being returned when you try to connect with FileZilla on the server side. These error messages are usually much more informative than the ones you get in FileZilla/other clients and should be able to point you in the right direction. 

If you need help interpreting the error, feel free to post it here after removing personally identifiable information like your URL or IP address, or running it by one of our live Support agents. They can SSH in to your server and see what the issue is if need be. 

Avatar
0
steve mills

I have this same problem. I've tried everything mentioned; full domain name with and without ftp., the Server Name, and shared IP address. I've tried every type of login and encryption in FileZilla, all the various options in the Site Manager window. Nothing works, just keep getting the exact same error every time when it tries to connect: "EAI_NONAME - Neither nodename nor servname provided, or not known".

I can connect with Fetch, but I don't want to buy it just so I can use an inferior ftp app. FileZilla does side-by-side comparison so it's easy to only upload changed files. This needs to be resolved.

Avatar
2
anonymous
Quote from kristinad

Well, that didn't work either. Logging in with the server name just gave the same error.


But, I tried dropping the "ftp." from the front of my domain name did work. So, I'm good now.

Sorry I didn't think of that one earlier, but I'm glad that worked!

Avatar
1
kristinad
Quote from anonymous

Solution: Connection Attempt Failed With “eai_noname - Neither Nodename nor Servname Provided, or Not Known”

Sorry that you're running into trouble connecting to FTP with Filezilla! Here are some troubleshooting steps to help you solve the following error: connection attempt failed with "eai_noname - neither nodename nor servname provided, or not known".

Verify Your FTP Settings

As long as your FTP Username, Password, and Port (21) are correct, you should be able to resolve to your server and connect. As a test you can try removing the "ftp." from the beginning of your domain as this subdomain may be pointed to a different server from your main domain. So, instead of ftp.example.com use example.com.

Check Your DNS

If your settings are accurate and you are still not able to connect, the most likely problem is something DNS related. This could come down to issues with a CDN like Cloudflare, or just a recent DNS change not having synced up somewhere yet, known as propagation (common if a site was recently transferred).

Connect With Server Hostname

One reliable workaround is to switch out the domain you are using with your server's hostname, since it should resolve directly to your server. Just look up your hostname in the Account Technical Details section of AMP, and use that in the place where you previously put your domain name. It should look something like ecbiz###.inmotionhosting.com, biz###.inmotionhosting.com, vps####.inmotionhosting.com, or something else along those lines (with the numbers replaced by the actual server numbers). Try that and hopefully it will resolve the issue!

Connect With IP Address

Another option is to use your servers IP address instead of your domain name or server hostname. You can view this IP address on the right side of cPanel.

Review Your FTP Logs

If your problems persist, you can review your server's FTP logs. Any time you connect to your server or transfer files, it will create a log entry listing what was done. If you don't see any records, your connection is failing before it resolves to the server.

If you are seeing FTP logs from your IP address it should provide additional details such as a success or error message.

Well, that didn't work either. Logging in with the server name just gave the same error.


But, I tried dropping the "ftp." from the front of my domain name did work. So, I'm good now.

Avatar
0
anonymous
  • Answer
  • Answered

Solution: Connection Attempt Failed With “eai_noname - Neither Nodename nor Servname Provided, or Not Known”

Sorry that you're running into trouble connecting to FTP with Filezilla! Here are some troubleshooting steps to help you solve the following error: connection attempt failed with "eai_noname - neither nodename nor servname provided, or not known".

Verify Your FTP Settings

As long as your FTP Username, Password, and Port (21) are correct, you should be able to resolve to your server and connect. As a test you can try removing the "ftp." from the beginning of your domain as this subdomain may be pointed to a different server from your main domain. So, instead of ftp.example.com use example.com.

Check Your DNS

If your settings are accurate and you are still not able to connect, the most likely problem is something DNS related. This could come down to issues with a CDN like Cloudflare, or just a recent DNS change not having synced up somewhere yet, known as propagation (common if a site was recently transferred).

Connect With Server Hostname

One reliable workaround is to switch out the domain you are using with your server's hostname, since it should resolve directly to your server. Just look up your hostname in the Account Technical Details section of AMP, and use that in the place where you previously put your domain name. It should look something like ecbiz###.inmotionhosting.com, biz###.inmotionhosting.com, vps####.inmotionhosting.com, or something else along those lines (with the numbers replaced by the actual server numbers). Try that and hopefully it will resolve the issue!

Connect With IP Address

Another option is to use your servers IP address instead of your domain name or server hostname. You can view this IP address on the right side of cPanel.

Review Your FTP Logs

If your problems persist, you can review your server's FTP logs. Any time you connect to your server or transfer files, it will create a log entry listing what was done. If you don't see any records, your connection is failing before it resolves to the server.

If you are seeing FTP logs from your IP address it should provide additional details such as a success or error message.