Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

Is there a special port for godaddy servers? Do I have to call them to enable ftp support? I can login w the username and password on the control panel on godaddy.com but not on ftp. I'm not sure what I'm doing wrong. I tried using Filezilla and CuteFTP Pro using port 21 but w/ no luck.

Go Daddy's Instructions are:

  1. FTP Address or Hostname: Your Domain Name
  2. FTP Username & Password: You selected both of these during account creation
  3. Start Directory: You should leave this blank or include a single forward slash (i.e. /)
  4. FTP Port: You should enter Standard, or 21. •FTP Client. ( ◦Filezilla, ◦WS-FTP, ◦CuteFTP Pro, ◦AceFTP )

Thanks!

share|improve this question

3 Answers 3

up vote 2 down vote accepted

Are you following godaddy's FTP instructions, and what brand is your router?

Update

Try setting data connection type to PASV (passive mode)

There may be more to it than that:

Modern FTP clients will select passive, or active FTP mode automatically, so this is not usually an issue. However, most FTP servers support active, and passive modes, and give you the choice. GoDaddy has configured ProFTP to only serve in passive mode, and there's a caveat with that:

Some modern routers, and high speed modem/router devices block passive FTP, or one part of it, on their firewalls. The answer is to let that part through your firewall. To test this, turn off all your firewalls, then try to narrow down which one it is. I can tell you that on OS X Yosemite it is not the Mac's firewall.

If it's your own router inside the service provider's device, you need to refer to the manufacturer's support information, or some other online resource.

If it's your ISP's device, you may have limited control over the firewall, and be unable to filter exactly what you want. In other words, you may have to turn the firewall off. Personally I find it unacceptable that GoDaddy is engaging in this silliness, but that's them, and they've always been a pain in the ass for real Webmasters, and Systems Administrators.

As an example: My ISP is Rogers, in the suburbs of Toronto. I have a very fast, and mostly reliable connection. However, I just switched modems to an Hitron CGN3, or CGN3ROG, if you like (note the 'ROG' suffix). I don't have complete control over the firewall, but I have some. If I turn off the blocking of P2P sharing, which I'd rather not, passive FTP works. Obviously this is some odd reasoning at Hitron where they consider passive FTP some kind of P2P sharing. But there you go.

Sussing out this answer required chatting with a very 'trying to be helpful', and patient, support tech at GoDaddy for about three hours, terminating at 2:44am. Eventually he queried a more techy tech, and he determined that one part of the passive FTP protocol was failing. From there I was able to run it into the ground.

You will note, please, that this has nothing to do with the FTP client software (FileZilla, Cyberduck, whatever), and that GoDaddy's FTP server does work as it should. It's just a combination of odd decisions on the parts of GoDaddy, and some device manufacturers.

share|improve this answer
    
Thanks for your reply. Yep, I have the ftp set on port 21... –  Brian McCarthy Mar 9 '11 at 15:27
    
@Brian, updated my answer with my next guess. :) –  John Conde Mar 9 '11 at 15:30

1) May sound stupid but did you put in ftp.yourdomain.com in for host? Try that if you didn't already.

2) Did you setup an actual FTP Account? Check here:

Hosting Dashboard > Settings > FTP Users

Create another user other than the "Primary FTP User", as that is typically your regular login info to the site. Once created, wait a few minutes till it says it's completed the setup, then go to your FTP Client and type in host: ftp.yourwebsite.com and the username with password, on port 21. You should be set.

share|improve this answer

What do the FTP client logs/terminal show in terms of errors?

In Filezilla -> View -> Message Log you will see the command/response sequence when your client attempts to login. You should be able to work out where it is going wrong from the codes.

EDIT: Wikipedia has a list of the common FTP codes

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.