Mountain Lion Support not fixed? about fileshuttle HOT 19 OPEN

from fileshuttle.

Can you make sure, that your credentials work in another programm (Transmit/Cyberduck)? I'm using the latest Version from GitHub and it works pretty well without crashing or errors. I'm transferring data via FTP.

from fileshuttle.

I am using Cyberduck right now, and uploads work without a hitch. Settings are the same; I even copy/pasted from Keychain to make sure I wasn't somehow typing the wrong password. Here are two screenshots –

from fileshuttle.

Could you please check console.app for log data?

from fileshuttle.

2/25/13 2:14:33.675 PM FileShuttle[465]: Upload Failed with error Error Domain=NSURLErrorDomain Code=-1004 "couldn't connect to host" UserInfo=0x100493270 {NSLocalizedDescription=couldn't connect to host, NSErrorFailingURLStringKey=ftp://adamk.in:21///Ns4OO4quIZ.png, NSErrorFailingURLKey=ftp://adamk.in:21///Ns4OO4quIZ.png, 2097154=227, NSUnderlyingError=0x100463da0 "couldn't connect to host"}

from fileshuttle.

Do you have a local firewall? like little snitch?

from fileshuttle.

I have messed with my host file to block access to some stuff, but that is all.

127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
50.18.210.140 id-cms.ipplex.com
184.169.170.34 id-qa-cms.ipplex.com
107.21.203.87 idmedia-cms.ipplex.com
74.208.9.173 id-demo.ipplex.com
fe80::1%lo0 localhost

from fileshuttle.

okay, then I'm out … sounds for me like an application based firewall rule but could also be a bug :(

I'm sorry. Perhaps Anthony or Michael have more ideas!

from fileshuttle.

Thank you Rico. Will Anthony or Michael see this thread?

from fileshuttle.

Yepp. They do. But I'm not sure how busy they are so it might take one or two days to get response. also they need a way to reproduce your issue to fix it.

from fileshuttle.

i see that cyberduck is using ACTIVE FTP mode, can you confirm it also works fine in passive mode (just ruling out stuff)

are you also able to try another FTP server and credentials to confirm if its an app issue or other localised system issue

the error is: couldn't connect to host, NSErrorFailingURLStringKey=ftp://adamk.in:21///Ns4OO4quIZ.png

this means the app couldnt connect to adamk.in on port 21 - this usually means that the connection is blocked on either your mac end or the remote end or that the remote ftp service isnt running or that there is some other internet issue between

are you trying while connected with cyberduck? does your FTP server have any kind of concurrent connection limit

from fileshuttle.

Passive mode does not work for my server.

On Feb 25, 2013, at 8:26 PM, Anthony Somerset [email protected] wrote:

i see that cyberduck is using ACTIVE FTP mode, can you confirm it also works fine in passive mode (just ruling out stuff)

are you also able to try another FTP server and credentials to confirm if its an app issue or other localised system issue

—
Reply to this email directly or view it on GitHub.

from fileshuttle.

there it is :-)

from fileshuttle.

Well it's never supported passive, but FileShuttle used to work just fine under snow leopard (i never had lion). So why does it not work now?

On Feb 26, 2013, at 12:07 PM, Rico Neitzel [email protected] wrote:

there it is :-)
—
Reply to this email directly or view it on GitHub.

from fileshuttle.

Probably that's one of the changes to make it work under ML … i don't know. it's just a guess.

from fileshuttle.

I changed the way FTP files are uploaded. The old way crashed FileShuttle.
It now uses CURL, we should have an option to enable passive mode and forward that option to CURL.

from fileshuttle.

Just to clarify, my server uses Active :-)

On Feb 26, 2013, at 1:27 PM, Michael Villar [email protected] wrote:

I changed the way FTP files are uploaded. The old way crashed FileShuttle.
It now uses CURL, we should have an option to enable passive mode and forward that option to CURL.

—
Reply to this email directly or view it on GitHub.

from fileshuttle.

My bad ;)

from fileshuttle.

Hi @michaelvillar , any update on this? Will I be able to start using FileShuttle again anytime soon :-)

from fileshuttle.