Your best friend for file transfer.

Fetch application logoFetch

Can't connect to server (6 posts)

  • Started 3 years ago by Henry
  • Latest reply 3 years ago from Jim Matthews
  • Henry Member

    All of a sudden, I can't connect to my web server. Below is the transcript. It tries to connect and then gives error message "An FTP with TLS/SSL connection to 68.178.255.13 could not be opened because there was an internal TLS/SSL error.

    Fetch 5.7.4 (5H1367) Intel (Web Store) running on Mac OS X 10.7.5 (11G63) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Expires 11/9/14 T
    Connecting to 68.178.255.13 port 21 (Mac OS X firewall is allowing connections) (10/25/14 5:06 PM)
    Connected to 68.178.255.13 port 21 (10/25/14 5:06 PM)
    220 FTP Server
    AUTH TLS
    234 AUTH TLS successful
    An FTP with TLS/SSL connection to “68.178.255.13” could not be opened because there was an internal TLS/SSL error. (Please try again.)
    Connecting to 68.178.255.13 port 21 (Mac OS X firewall is allowing connections) (10/25/14 5:07 PM)
    Connected to 68.178.255.13 port 21 (10/25/14 5:07 PM)
    220 FTP Server
    AUTH TLS
    234 AUTH TLS successful
    An FTP with TLS/SSL connection to “68.178.255.13” could not be opened because there was an internal TLS/SSL error. (Please try again.)
    Connecting to 68.178.255.13 port 21 (Mac OS X firewall is allowing connections) (10/25/14 5:07 PM)
    Connected to 68.178.255.13 port 21 (10/25/14 5:07 PM)
    220 FTP Server
    ADAT
    550 SSL/TLS required on the control channel
    AUTH This command is checking whether this server supports Kerberos or GSS security, see RFC 2228
    500 AUTH not understood
    AUTH GSSAPI
    500 AUTH not understood
    An FTP with GSSAPI connection to “68.178.255.13” could not be opened because the FTP server does not support security extensions. (Contact the server administrator for more information.
    Server responded: “AUTH not understood”)
    Connecting to whlong2@68.178.255.13 port 22 (10/25/14 5:07 PM)
    SSH2_FXP_INIT 3
    Update check skipped at 10/25/14 5:08 PM (next check after 10/26/14 8:29 AM)
    SFTP connection to “68.178.255.13” could not be opened because the connection to the SFTP server could not be established or was lost. (Try again, or contact the server administrator to verify that you have the correct hostname, username, password, and authentication method, and that the server is running.
    Server responded: “ssh: connect to host 68.178.255.13 port 22: Operation timed out

    ”)
    Connecting to 68.178.255.13 port 21 (Mac OS X firewall is allowing connections) (10/25/14 5:09 PM)
    Connected to 68.178.255.13 port 21 (10/25/14 5:09 PM)
    220 FTP Server
    AUTH TLS
    234 AUTH TLS successful
    An FTP with TLS/SSL connection to “68.178.255.13” could not be opened because there was an internal TLS/SSL error. (Please try again.)
    Connecting to 68.178.255.13 port 21 (Mac OS X firewall is allowing connections) (10/25/14 5:32 PM)
    Connected to 68.178.255.13 port 21 (10/25/14 5:32 PM)
    220 FTP Server
    AUTH TLS
    234 AUTH TLS successful
    An FTP with TLS/SSL connection to “68.178.255.13” could not be opened because there was an internal TLS/SSL error. (Please try again.)

    Posted 3 years ago #

  • Henry Member

    I am able to connect with Filezilla.

    Posted 3 years ago #

  • Jim Matthews Administrator

    Hi,

    It appears that the server made a change that breaks connections from the OS X networking software that Fetch uses on OS X 10.7 (Lion). Perhaps this is a response to security issues recently found in SSL. I am able to connect with Fetch on OS X 10.8 (Mountain Lion) and 10.10 (Yosemite).

    I would recommend using FileZilla on 10.7, or else upgrading to 10.8 or a newer OS X release.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 3 years ago #

  • Henry Member

    I'm also able to connect using Transmit. This would seem to point to an issue with Fetch if I'm able to connect using two other FTP programs.

    Posted 3 years ago #

  • Henry Member

    BTW: I've been using Fetch with 10.7 for some time now with no trouble. The trouble just started suddenly. Any help would be appreciated.

    Posted 3 years ago #

  • Jim Matthews Administrator

    Hi,

    As I wrote above, I'm guessing that the server administrators recently made a change, and that broke compatibility with OS X 10.7's Secure Transport TLS/SSL software (Fetch uses Secure Transport, FileZilla and Transmit do not).

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 3 years ago #

Reply

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