Your best friend for file transfer.

Fetch application logoFetch

Using FTP with GoDaddy web Hosting (36 posts)

  • Started 2 years ago by Madison
  • Latest reply 1 week ago from Jim Matthews
  • Madison Member

    I seem to be having an issue with using fetch and accessing my ftp for my GoDaddy site. I have tried entering multiple log in criteria and nothing is working. Any suggestions?

    Posted 2 years ago #

  • Jim Matthews Administrator

    Hi,

    I would contact GoDaddy and verify that you have the correct hostname, username and password for FTP login. It's the GoDaddy server that decides whether to let you in, Fetch just sends it what you enter.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 2 years ago #

  • rikc Member

    Yes having the same issues. Godaddy says the can see it on there end. I changed passwords and everything is correct. But still having issues.

    Posted 2 years ago #

  • Jim Matthews Administrator

    Hi,

    When you try to make a new connection Fetch connects to the server named in the Hostname field, and sends that server the username and password that you entered in the Username and Password fields. It's the server -- in this case a computer at GoDaddy -- that says whether the information you entered is correct.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 2 years ago #

  • rikc Member

    Yes everything is correct. Acturally called go-daddy. They tried it on there end. An its working.
    Not sure whats going on. Am at a lost. Using another 3rd party software. See what happens.

    Posted 2 years ago #

  • Jim Matthews Administrator

    You might send them the contents of the Fetch Transcript window, so they can see what Fetch is sending to the server (except for the password -- they have to take your word for that).

    Jim Matthews
    Fetch Softworks

    Posted 2 years ago #

  • studebaker Member

    Same issue here. Fetch won't connect to new goDaddy hosting. Cyberduck works. Might be worth some investigation on your end...

    Posted 2 years ago #

  • Jim Matthews Administrator

    Hi,

    I'd be very interested in investigating that. Could you try connecting with Fetch, and then choose "Fetch Transcript" from the Window menu and send me the contents at http://fetchsoftworks.com/fetch/feedback (or here)?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 2 years ago #

  • studebaker Member

    Went back in and now connection is working. Not sure why as I didn't do anything different.

    Posted 2 years ago #

  • Jim Matthews Administrator

    Thanks for trying again; please do let me know if the problem returns.

    Jim Matthews
    Fetch Softworks

    Posted 2 years ago #

  • Pat Member

    I am having the same issues with Godaddy that are listed above. All exact same scenarios with Godaddy support on the phone and not able to login etc. I did screen shots of what I am entering and the error message I get. Finally downloaded another ftp program and I can get in with same criteria but I don't like it at all. I want to stick with Fetch as I have used it for 20 years and love it!

    Edited 6 months ago #

  • Jim Matthews Administrator

    Hi Pat,

    Could you try connecting with Fetch, and then choose "Fetch Transcript" from the Window menu and send me the contents at http://fetchsoftworks.com/fetch/feedback (or here)?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 6 months ago #

  • cvgood Member

    Having same problem unable to connect to my acc. thru fetch, Host, UN & password all confirmed connect using ftp keeps telling me wrong PW but am able to get in thru internet site GoDad, fetch 5.7.5 (5H1476, Web Store). fetch transcript below. Thanks

    Fetch 5.7.5 (5H1476) Intel (Web Store) running on Mac OS X 10.12.5 (16F73) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH55001-VDDZ-L2M8 T
    Connecting to cvgoodwin.com port 21 (Mac OS X firewall is allowing connections) (6/6/17, 10:13 AM)
    Connected to 72.167.232.74 port 21 (6/6/17, 10:13 AM)
    220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
    220-You are user number 1 of 500 allowed.
    220-Local time is now 07:13. Server port: 21.
    220-This is a private system - No anonymous login
    220 You will be disconnected after 3 minutes of inactivity.
    USER cvgood55
    331 User cvgood55 OK. Password required
    PASS
    530 Login authentication failed
    An FTP connection to “cvgoodwin.com” could not be opened because the server rejected the password. (Contact the server administrator to verify that you have the correct hostname, username, password, and authentication method.
    Server responded: “Login authentication failed”)
    Update check skipped at 6/6/17, 10:15 AM (next check after 6/9/17, 6:42 AM)
    Connecting to cvgoodwin.com port 21 (Mac OS X firewall is allowing connections) (6/6/17, 12:31 PM)
    Connected to 72.167.232.74 port 21 (6/6/17, 12:31 PM)

    Posted 5 months ago #

  • Jim Matthews Administrator

    Hi,

    When you log into your server Fetch is acting as a go-between. Fetch sends the password that you enter to the server, and the server answers either "yes, you can proceed" or "no, that isn't the password I was looking for." To fix this problem you need to contact your server administrator (i.e. GoDaddy) and have them reset your FTP login password, so that you have the password that the server expects.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 5 months ago #

  • Pat Member

    Hi Jim,
    After I posted here I spoke with GoDaddy and then tried again later. It connects fine now with Fetch. So perhaps they changed something in their settings.

    Posted 5 months ago #

  • Paul Member

    I'm having a similar problem, but getting different error messages. I tried to connect to GoDaddy, and it actually worked the first time, but after several minutes it dropped the connection with an authentication failure, and I can't get it to reconnect. I tried using sftp command from terminal, and got the same issue. (My credentials are fine, GD customer support successfully logged in and used FTP commands.)

    Thanks for the "check the Transcript" tip, that confirmed that the error is the same, and it has something to do with the key changing and my Mac using some strict key checking. Transcript of error:

    <<
    SSH2_FXP_INIT 3
    Unknown server response: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

    @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

    IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

    Someone could be eavesdropping on you right now (man-in-the-middle attack)!

    It is also possible that a host key has just been changed.

    The fingerprint for the ECDSA key sent by the remote host is
    SHA256:Y+IOsT3V57kX15b+1qQlJFUwJgHxkhuS7/H3JgDZkhg.

    Please contact your system administrator.

    Add correct host key in /Users/paul/.ssh/known_hosts to get rid of this message.

    Offending ECDSA key in /Users/paul/.ssh/known_hosts:11

    ECDSA host key for higherdig.net has changed and you have requested strict checking.

    Host key verification failed.

    SFTP connection to “higherdig.net” could not be opened because the SFTP server rejected your authentication information. (Contact the server administrator to verify that you have the correct hostname, username, password, and authentication method.)
    >>

    Terminal message is identical starting after "Unknown server response:" through "Host key verification failed." The paragraph after that is the same error message that Fetch displays in the connection window.

    Help! Do I delete the entry in /Users/paul/.ssh/known_hosts? The fingerprint in this message doesn't look like the key itself, which is longer (but removing the record could reset it and get a new key added). Or, is there some setting in my MacOS X to ignore such changes? They suggested using a different client, but I have my doubts that would work.

    Posted 2 months ago #

  • Jim Matthews Administrator

    Hi,

    You can remove the offending key from known_hosts by following these steps:

    1) Choose Utilities from the Go menu in the Finder
    2) Open Terminal
    3) Enter the following command and type Return:

    sed -i -e "11d" ~/.ssh/known_hosts

    Let me know if that doesn't fix the problem.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 2 months ago #

  • JP Member

    I'm having the same issue with Fetch via SFTP to GoDaddy Managed Wordpress theme port 22. First time connected fine and uploaded theme. After that have been unable to connect. Changed SFTP password at GoDaddy to no avail. Spoke with GD support, they confirmed my IP was not blacklisted and were able to connect remotely. Tried again via FileZilla and was able to connect fine. Tried again via Fetch to no avail. It's definitely a Fetch issue - Jim, if you have any suggestions would really appreciate it.

    Thnx!

    Posted 2 months ago #

  • Paul Member

    Sounds like the same issue with the known_hosts file. I was able to work around it by editing that file to remove the last line, but I had to do this repeatedly since this key seems to keep changing. The workaround from Jim would only work if the GoDaddy entry is the 11th in your file, but if you can find and edit the file, just delete the record (long line) that has the GoDaddy key in it.

    Paul

    Posted 2 months ago #

  • JP Member

    Thnx Paul - do you mean edit the transcript "ECDSA host key for 198.71.233.141 has changed and you have requested strict checking." ? Not sure how to edit the transcript....

    Posted 2 months ago #

  • Paul Member

    No, but it means to edit a file that the transcript points you to, on your Mac. The "host key" it's referring to is in this file:

    /Users/paul/.ssh/known_hosts (replace "paul" with your Mac username)

    or as Jim mentioned in his comment, once you're in Terminal, the file that's at: ~/.ssh/known_hosts

    This file contains host keys for all hosts you've done SSH or SFTP sessions with, and apparently GoDaddy changed their keys constantly. So this file needs to be edited. The command Jim provided above would work for you, with one potential modification:

    My transcript included the following line:

    Offending ECDSA key in /Users/paul/.ssh/known_hosts:11

    His instructions included the number "11" from my error message. Yours is probably different, maybe lower. So once you're in terminal, replace the "11" in this command with whatever appears at the end of the corresponding line in your transcript.

    sed -i -e "11d" ~/.ssh/known_hosts

    becomes

    sed -i -e "#d" ~/.ssh/known_hosts

    where # is that number.

    That's it. Just a (somewhat) power user, not official support.

    Paul

    Posted 2 months ago #

  • JP Member

    Thnx Paul - in my case it was #7... entered
    sed -i -e “7d" ~/.ssh/known_hosts
    into terminal and tried again to no avail.... Error "SFTP connection to "spiritrentalcars.com" could not be opened because the SFTP server rejected your authentication information."

    Again, can SFTP fiine with FileZilla and CyberDuck.

    Posted 2 months ago #

  • Jim Matthews Administrator

    Hi JP,

    What do you see in the transcript now that you removed that line from known_hosts?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 2 months ago #

  • JP Member

    strange- this morning it opened in Fetch fine. maybe computer needed a restart after removal of the known_hosts. thnx all for your help!

    Posted 2 months ago #

  • Jim Matthews Administrator

    Glad it's working now!

    Jim Matthews
    Fetch Softworks

    Posted 2 months ago #

  • Russell Member

    Same issue here as JP.
    Other FTP clients work fine. It's only Fetch that doesn't work for GoDaddy Managed Wordpress hosting. Connects only time in 100.

    The thing is, I LIKE Fetch. Have been using it for years. I don't want to switch software for one website I manage. Certainly don't like the built-in spam with FIleZilla.

    Posted 3 weeks ago #

  • JP Member

    Hi Russell - I've found using SFTP and Port 22, if I keep trying to connect I'll usually get through within the 5th to 10th attempts. You've got to keep entering Port 22 though. This is definitely a Fetch issue and I wish they'd resolve it - my preferred client as well.

    Posted 3 weeks ago #

  • Russell Member

    Thanks JP . Appreciate the tip. The Terminal stuff is above my pay grade.

    Posted 3 weeks ago #

  • JP Member

    The terminal changes didn't help anyway...

    Posted 3 weeks ago #

  • Jim Matthews Administrator

    Russell: Could you post the contents of the Fetch Transcript window after a connection failure, or else submit the transcript at http://fetchsoftworks.com/fetch/feedback ?

    JP: If you choose SFTP you don't need to enter port 22 (port 22 is the default port for SFTP).

    Both of you: Do you have "Ask before accepting unknown host keys" checked in the Security section of Fetch Preferences? If so, does unchecking it make a difference?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 3 weeks ago #