Fetch Softworks

error: an ftp with tls/ssl connection to "" could not be opened because an error has occur (24 posts)

• Started 10 years ago by Dan
• Latest reply 9 years ago from Jim Matthews

• Dan Member

  I just upgraded my OSX to 10.8...

  I get this error...

  error: an ftp with tls/ssl connection to "" could not be opened because an error has occurred. SSL error -9807

  Do I have to regenerate keys and if so can you give me all of the steps?

  Cheers,

  Dan

  Posted 10 years ago #

• Jim Matthews Administrator

  Hi Dan,

  Thanks for reporting this problem. I have a test version of Fetch that should fix it. Could you send an email to bugs@fetchsoftworks.com ? I will send you a link to download the test version.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 10 years ago #

• Jagjit Singh Member

  Hi there,

  I have exactly same issue. I have even tested on a fresh Mountain Lion.

  Connected to xxx.xxx.xxx.xxx port 990 (2012-07-28 4:33 PM)
  get_reply():con_conn->Getline() returns 3,-9807
  An FTP with TLS/SSL connection to “....” could not be opened because the FTP server dropped the connection. (Try again, or contact the server administrator to verify that the server is running.)

  Please help.
  Thanks,
  Jagjit

  Posted 10 years ago #

• Jim Matthews Administrator

  Hi,

  Please send email to the address listed above, and I will send you a link to a test version of Fetch that fixes this problem.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 10 years ago #

• Jagjit Singh Member

  The test build works OK Jim.

  Posted 10 years ago #

• Dan Member

  Yes it's working perfectly.

  Posted 10 years ago #

• Jim Matthews Administrator

  Glad to hear it!

  Posted 10 years ago #

• Lorenz Member

  Hi,

  I have the same issue despite upgrading to 5.7.2. (obviously on top of mountain lion). is 5.7.2 supposed to be fixing this or is there some other fix?

  thanks,

  Lorenz

  Posted 10 years ago #

• Jim Matthews Administrator

  There is another fix; please email bugs@fetchsoftworks.com for download instructions.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 10 years ago #

• Dany Richer Member

  Hi ! I got the same message

  error: an ftp with tls/ssl connection to "" could not be opened because an error has occurred. SSL error -9807

  How can I resolve this?
  Thanks
  Dany

  Posted 10 years ago #

• Jim Matthews Administrator

  Hi Dany,

  Send an email to bugs@fetchsoftworks.com and I'll send you the download instructions for a test version of Fetch that should fix this problem.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 10 years ago #

• Jim Matthews Administrator

  This problem is fixed in Fetch 5.7.3, which is now available for download at http://fetchsoftworks.com .

  Thanks to everyone who reported this problem, and tried test versions!

  Jim Matthews
  Fetch Softworks

  Posted 10 years ago #

• Nanako Inoue Member

  Fetch
  Hi,
  I tried to upload my FTP yahoo account site today, but below message came.
  error: an ftp with tls/ssl connection to "" could not be opened because an error has occurred. SSL error -9807

  I checked my other FTP servers, they are all fine to access with Fetch as usually, only this yahoo ftp was problem

  Thank you,
  Nanako Inoue
  my Fetch is 5.53. using Mac 10.8.2 _should I upgrade to 5.6 ?

  PS: I followed this below direction to open that ftp. and talk with yahoo technical service person send me this link.
  -------------------------------
  When Fetch is first launched, you will automatically be prompted to enter your FTP credentials.
  Host: ftp.yourdomain.com (replace yourdomain.com with your domain name)
  Username: Yahoo!ID@yourdomain.com (replace yourdomain.com with your domain name)
  Connect using: FTP with TLS/SSL
  Leave "Enable encryption" checked.
  Password: Yahoo! ID password
  Leave "Add to keychain" unchecked.
  Click Connect
  You'll receive a message "Fetch can not verify the identity of server "ftp.yourdomain.com (replace yourdomain.com with your domain name)." Click Continue.

  Posted 10 years ago #

• Jim Matthews Administrator

  Hi,

  You should upgrade to Fetch 5.7.3, which you can download from http://fetchsoftworks.com

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 10 years ago #

• Nanako Inoue Member

  excellent!!

  thank you very much!

  Posted 10 years ago #

• Gary Member

  i've upgraded to Fetch 5.7.3, but still running into access issues using TSL/SSL. Any solutions?

  warmest, gary

  Edited 9 years ago #

• Jim Matthews Administrator

  Hi,

  What sort of issues are you seeing? Could you post the contents of the Fetch Transcript window?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 9 years ago #

• Gary Member

  Jim,

  thanks for helping out… i've tried using two different Macs, both running Mac OS 10.8.5. Using Fetch 5.7.3, i can conned to other non-TSL/SSL sites, but still having issues with TSL/SSL access.

  The error message is "Fetch could not get the file list because there was a timeout trying to establish a passive mode data connection. A server firewall might be blocking passive mode (PASV) transfer. Ask the server administrator for help, or try unchecking the "Use passive mode transfer (PASV)" box on the General pane of the Preference."

  i've tried checked and unchecked (PASV) mode.

  Any advise would be appreciated.

  warmest, gary

  Posted 9 years ago #

• Jim Matthews Administrator

  Have you asked the people who run those sites whether they support passive mode (PASV)? FTP has two ways to do transfers, active mode and passive mode, and passive mode is the only one that really works for FTP with TLS/SSL, but it won't work if the server has a firewall that blocks FTP data connections.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 9 years ago #

• Gary Member

  Yes…they support passive mode on FileZilla FTP server.

  Posted 9 years ago #

• Jim Matthews Administrator

  I'd recommend contacting us at http://fetchsoftworks.com/fetch/feedback and submitting the contents of your Fetch Transcript window after you get one of these errors. I'll see what I can figure out.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 9 years ago #

• Jim Matthews Administrator

  To summarize: Apparently Comcast/Xfinity's "Typical Security (Medium)" router setting blocks outbound TCP ports 49152-65534. That blocks FTP passive connections. I would set the router to "Minimum Security (Low)" or "Custom Security" (but leave the "Block peer to peer" box unchecked -- that's the one that breaks FTP passive mode).

  Jim Matthews
  Fetch Softworks

  Posted 9 years ago #

• Gary Member

  Jim,

  We’re still fighting with the TSL/SSL access issue. Thanks for the suggestion to set the router to "Minimum Security (Low)" or "Custom Security" (with the "Block peer to peer" box unchecked). Fetch v5.7.3 seems to work fine in Xfinity “Minimum Security (Low)” and “Custom Security” settings. But naturally for security reasons, we’d like to maintain a “Typical Security (Medium)".

  Using the “Typical Security (Medium)", we have also adjusted the following in the Xfinity Advanced Settings:

  Port Triggering
  Service Name: Encrypted_FTP
  Serice Type: TCP
  Trigger Port(s): 21
  Target Port(s): 49152-65534
  Active: checked

  Using Fetch v5.7.3, with the above mentioned settings we can access and send to the TSL/SSL server for relatively “small files”. We’re trying to send larger files (a folder of photos) in excess of 125mg or larger.

  With Fetch v5.7.3, the transfer stops sending in the midway through transmissions. Sometime it will pick up again several minutes later. Sometimes it will stop completely and not finish the transmission at all.

  However, using CyberDuck v4.4.4, with the same XFinity configuration, the transmissions go through fine.

  Our preference is to use Fetch, rather than CyberDuck, with the XFinity “Typical Security (Medium)".

  If you have any clues, we’re all ears.

  Warmest,

  Gary

  Posted 9 years ago #

• Jim Matthews Administrator

  I would be interested in seeing a transcript of a failed Fetch connection using that configuration (you can send it to bugs@fetchsoftworks.com).

  I see three problems with using Port Triggering:

  1) You are opening ports for inbound traffic, which is arguably worse than turning off "Block peer to peer".
  2) The ports only stay open for 10 minutes, and if a file takes more than 10 minutes to transfer the port will close in the middle of the upload.
  3) If more than one person on the network uses FTP at the same time there will be problems, since the router will forward traffic to one local machine at a time. FTP user 1 might be in the middle of a transfer when FTP user 2 opens a connection, resulting in all of FTP user 1's traffic being misdirected. This sort of failure would be erratic and hard to debug.

  I wish Xfinity let you selectively block ports; that way you could block peer to peer applications without blocking FTP. Unfortunately that doesn't seem to be an option.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 9 years ago #