Your best friend for file transfer.

Fetch application logoFetch

Error -9824 (13 posts)

  • Started 1 year ago by cmsmith
  • Latest reply 9 months ago from Jim Matthews
  • cmsmith Member

    I have been connecting without issue for years and today I am getting an error -9824. I do not know anything about how this works so I need a dummy's guide to working through/around this. I have several large folders of information to upload to my website (slideshows for clients). I cannot find anything on how to fix this. I have re-enered my info and tried alternate connections listed with my host as well. Please help!!!

    Posted 1 year ago #

  • Bim Member

    cmsmith, I am glad I'm not the only one having this issue (SSL error -9824). Everything worked fine yesterday (and for a long time in the past). However, today, Fetch will not connect with any website that is on an Aabaco Small Business (formerly Yahoo! Small Business) server. Fetch is still connecting with my websites that are hosted on Hostway's servers, but not the ones on Aabaco's. Someone from Aabaco suggested that I try connecting with FileZilla. It worked! So, it is definitely an issue with Fetch. You might try FileZilla to get you by until Fetch Softworks can solve this issue, which I hope they can do quickly. I much prefer using Fetch.

    Here is some information from Fetch's log transcript, if that helps:

    Fetch 5.7.5 (5H1476) Intel (Web Store) running on Mac OS X 10.7.5 (11G63) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial XXXXXXXXXX-XXXX-XXXX X
    Connecting to ftp.xxxxxxxxxxxxxxx.com port 21 (Mac OS X firewall is limiting connections to specific applications) (11/2/16 2:33 PM)
    Connected to 66.196.82.113 port 21 (11/2/16 2:33 PM)
    220-Welcome to the Yahoo! Web Hosting FTP server
    220-Need help? Get all details at:
    220-http://help.luminate.com/help/us/webhosting/gftp/
    220-◇
    220-No anonymous logins accepted.
    220-Yahoo!
    220-Local time is now 12:33. Server port: 21.
    220-This is a private system - No anonymous login
    220 You will be disconnected after 5 minutes of inactivity.
    AUTH TLS
    234 AUTH TLS OK.
    An FTP with TLS/SSL connection to “ ftp.xxxxxxxxxxxxxxx.com” could not be opened because an error has occurred. (SSL error -9824.)

    I hope this is helpful!

    Edited 1 year ago #

  • cmsmith Member

    Thank you. I had tried filezilla earlier, but it didn't work. I just tried it again and it is connecting. I do not like the interface much, but if it is what is working, it is what I am using. hope Fetch gets it fixed soon. Thanks again!

    Posted 1 year ago #

  • XTN Member

    Aye. This is happening to me as well. Same host (Aabaco) that I swear must be one guy with like 10 PCs sitting in his rec room somewhere. It would be uncivilized to say how disappointed I am with Yahoo.

    PLEASE FIX

    Edited 1 year ago #

  • Jim Matthews Administrator

    Hi,

    Please contact me at http://fetchsoftworks.com/fetch/feedback . I'll send you a download link for an experimental copy of Fetch that should solve this problem.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Edited 1 year ago #

  • Bim Member

    Apparently, the problem, at least in my case, is that Aabaco's servers won't work with Mac OS X 10.7.5 (the latest OS my MacBook Pro accepts) when using Fetch. When I loaded the experimental copy of Fetch on my MacBook Pro, I still received the same error message. However, when I loaded the experimental copy of Fetch on my wife's newer, but much slower MacBook (not Pro) running Mac OS X 10.9.5, I could access the files on Aabaco's servers just fine. Evidently, when I need to access files on Aabaco's servers, I will be stuck with FileZilla until I can afford a newer MacBook Pro. However, I can still access files with my current laptop on Hostway (and other) servers using Fetch.

    I'm still hoping there is a better solution to this issue that will allow me to continue utilizing Fetch as my primary FTP client.

    Posted 1 year ago #

  • Jim Matthews Administrator

    Hi Bim,

    Unfortunately I don't know of a better solution. Fetch uses Apple's SecureTransport framework for secure communication. Apple added support for TLS 1.2 to SecureTransport in the OS X 10.8 release. And Aabaco's servers now require TLS 1.2.

    FileZilla works because it uses an internal TLS library rather than SecureTransport.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • XTN Member

    My Mac is 10.10. FWIW.

    Posted 1 year ago #

  • Bim Member

    Jim Matthews,

    I appreciate your willingness to research this issue and grant me such a specific and clear answer. I certainly did not receive such help from Aabaco.

    Thanks,

    Bim

    Posted 1 year ago #

  • skulldaddy Member

    I too use 10.7 mac, and have no plans on upgrading for reasons. I really hate to lose Fetch! Can it make to work? If not, I will have to use another FTP client.

    Posted 10 months ago #

  • Jim Matthews Administrator

    Unfortunately I don't know of a way to make it work on 10.7. I'm sorry I don't have a better answer.

    Jim Matthews
    Fetch Softworks

    Posted 10 months ago #

  • John Member

    Hi, I'm running Mac OS 10.6.8 and just updated Fetch to 5.7.6 that includes TLS1.2 but still can't access my site on Aabaco. At first I couldn't even access my site on Aabaco from Firefox so I changed my password and now that works. But FTP access with Fetch still fails with the error message 9824. Appreciate if anyone can assist.

    Posted 10 months ago #

  • Jim Matthews Administrator

    Hi,

    As noted above, Fetch needs OS X 10.8 or later to support TLS 1.2, and Aabaco now requires TLS 1.2. So your options are:

    1) Use a different FTP client, such as FileZilla.
    2) Upgrade to OS X 10.8 or later
    3) Switch to a different web hosting company, such as Dreamhost or Pair.com

    I apologize that I don't have better options to offer.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 9 months ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.