Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mountain Lion Support not fixed? #20

Open
theadamkramer opened this issue Feb 25, 2013 · 19 comments
Open

Mountain Lion Support not fixed? #20

theadamkramer opened this issue Feb 25, 2013 · 19 comments

Comments

@theadamkramer
Copy link

From the Description of the 2.1 download, it would seem as though Mountain Lion support has been added, although I still cannot upload files on my machine.

Is there something I need to reset in order to make this work?

@theadamkramer
Copy link
Author

Screen Shot 2013-02-25 at 2 05 08 PM

@riconeitzel
Copy link

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.

@theadamkramer
Copy link
Author

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 –
cd
fs

@riconeitzel
Copy link

Could you please check console.app for log data?

@theadamkramer
Copy link
Author

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"}

@riconeitzel
Copy link

Do you have a local firewall? like little snitch?

@theadamkramer
Copy link
Author

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

@riconeitzel
Copy link

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!

@theadamkramer
Copy link
Author

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

@riconeitzel
Copy link

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.

@anthonysomerset
Copy link
Collaborator

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

@theadamkramer
Copy link
Author

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.

@riconeitzel
Copy link

there it is :-)

@theadamkramer
Copy link
Author

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.

@riconeitzel
Copy link

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

@michaelvillar
Copy link
Owner

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.

@theadamkramer
Copy link
Author

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.

@michaelvillar
Copy link
Owner

My bad ;)

@theadamkramer
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants