Cyberduck Mountain Duck CLI

Opened on Apr 30, 2015 at 8:21:02 PM

Closed on May 2, 2015 at 6:58:52 AM

#8780 closed defect (duplicate)

Interoperability Failure with Bitgravity Server

Reported by: dag02005 Owned by: dkocher
Priority: normal Milestone: 4.7.1
Component: ftp Version: 4.7
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description (last modified by dkocher)

On our new MacPro (OS X Yosemite), we're getting an "Interoperability Failure: 215 UNIX TYPE L8" every time we try to log in to our Bitgravity server using Cyberduck. Oddly enough, this problem only happens for our admin account, not our guest account (which of course has limited usability). All our Macs with older version of OS X can log in to the server fine.

Build 17342

Log below... 

220-Welcome to Pure-FTPd.
220-Local time is now 13:17. Server port: 21.
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
USER efe@theauteurs.com
331 User efe@theauteurs.com OK. Password required
PASS ********
230-Your bandwidth usage is restricted
230 OK. Current restricted directory is /
FEAT
500 ?
SYST
211-Extensions supported:
 EPRT
 IDLE
 MDTM
 SIZE
 REST STREAM
 MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
 MLSD
 AUTH TLS
 PBSZ
 PROT
 ESTA
 PASV
 EPSV
 SPSV
 ESTP
211 End.
PWD
215 UNIX Type: L8
QUIT
257 "/" is your current location

Change History (2)

comment:1 Changed on May 1, 2015 at 6:53:15 AM by dkocher

  • Component changed from core to ftp
  • Description modified (diff)
  • Milestone set to 4.8
  • Owner set to dkocher
  • Status changed from new to assigned
  • Summary changed from "Interoperability Failure" When Access Our Bitgravity Server to Interoperability Failure with Bitgravity Server

comment:2 Changed on May 2, 2015 at 6:58:52 AM by dkocher

  • Resolution set to duplicate
  • Status changed from assigned to closed

Duplicate for #8669. The server is responding with out of sync messages after the 500 ? error reply to FEAT. Please open an issue with ​Pure-FTPD.

Note: See TracTickets for help on using tickets.