- Below are the steps to get FileZilla for mac os x and to install Step 1: Go to download page of FileZilla, download the filezilla*.tar.bz2. Now go to “Downloads” folder and double click on this tar.bz2 file to extract the FileZilla application software.
- Download Commander One PRO - FTP client for macOS 10.10 or later and enjoy it on your Mac. Commander One PRO is a revolutionary file manager for Mac with dual-panel interface. Multiple enhancements for better compatibility with OS X El Capitan (OS X 10.11). Wrong time of files creation when copying files from iOS, MTP or FTP to Mac.
For better or worse, in OS X 10.11 El Capitan, a new security measure prevents editing this file, even with root privileges. As discussed in this Stack Overflow thread, there are a few workarounds, such as disabling SIP with csrutil disable. If running Citrix Receiver for Mac 12.x on OS X El Capitan and are having trouble connecting, upgrade the NetScaler Gateway plugin. For more information, see this article on the Citrix downloads page: NetScaler Gateway Plug-in v3.1.4 for Mac OS X (El Capitan Support).
Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave 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
Comments
commented Oct 1, 2015
I upgraded my workstation to El Capitan last night and now connecting to a virtualbox-hosted VM doesn't seem to be working via ssh, although I can ssh locally. I'm using the latest source release (fe0e4f2). See below: [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» cat inventory/vagrant 0|10:42:43 [vagrant-linux] vagrant2 ansible_ssh_host=localhost ansible_ssh_user=root ansible_ssh_pass=vagrant ansible_ssh_port=2200⏎ [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ansible vagrant-linux -i inventory/vagrant -m ping -vvv 0|10:42:20 Using /[redacted]/dv-ansible/ansible.cfg as config file ESTABLISH CONNECTION FOR USER: root on PORT 2200 TO localhost vagrant2 | UNREACHABLE! [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ssh root@localhost -p 2200 3|10:42:23 root@localhost's password: vagrant Last login: Thu Oct 1 14:42:14 2015 from 10.0.2.2 Welcome to your Vagrant-built virtual machine. [root@localhost ~]# exit logout Connection to localhost closed. |
commented Oct 1, 2015
Hi @mcalhoun, which version of Ansible is this occurring on? |
commented Oct 1, 2015
I'm using the latest source code on the devel branch (fe0e4f2). |
commented Oct 1, 2015
Thanks, we have some users that have upgraded and we'll try to reproduce this. |
commented Oct 1, 2015
Thanks! Let me know if I can be of assistance in troubleshooting. |
commented Oct 1, 2015
@mcalhoun Please run with -vvvvv and post the output? And if the problem doesn't become clearer from doing so, perhaps you could cut-and-paste the ssh command that ansible actually executes and see what happens? |
commented Oct 1, 2015
If this datapoint helps, my Vagrant+El Capitan+ansible devel is working fine. |
commented Oct 1, 2015
@mcalhoun and you may want to try it with the stable-1.9 branch, just to pinpoint if it's something new or if this is some overall environmental configuration issue regarding ssh after the upgrade. |
commented Oct 1, 2015
Here's some of the requested output...I'll switch to 1.9 and see if that works... [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ansible vagrant-linux -i inventory/vagrant -m ping -vvvv 0|12:02:05 Using /[redacted]/dv-ansible/ansible.cfg as config file Loaded callback minimal of type stdout, v2.0 ESTABLISH CONNECTION FOR USER: root on PORT 2200 TO localhost vagrant2 | UNREACHABLE! [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ssh -V 0|12:04:55 OpenSSH_6.9p1, LibreSSL 2.1.7 [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ansible --version 0|12:04:57 ansible 2.0.0 (devel 9c42a4c) last updated 2015/10/01 12:04:27 (GMT -400) lib/ansible/modules/core: (detached HEAD b9090a8) last updated 2015/10/01 09:22:49 (GMT -400) lib/ansible/modules/extras: (detached HEAD 962afee) last updated 2015/10/01 09:22:49 (GMT -400) config file = /[redacted]/dv-ansible/ansible.cfg configured module search path = /[redacted]/ansible/library |
commented Oct 1, 2015
Switching to 1.9 works... [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ansible --version 0|12:09:03 ansible 1.9.4 (stable-1.9 a07ca04) last updated 2015/10/01 12:06:57 (GMT -400) lib/ansible/modules/core: (detached HEAD da496f9bcc) last updated 2015/10/01 12:08:01 (GMT -400) lib/ansible/modules/extras: (detached HEAD 81b345401f) last updated 2015/10/01 12:08:01 (GMT -400) configured module search path = /[redacted]/ansible/library [~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ansible vagrant-linux -i inventory/vagrant -m ping 0|12:09:09 vagrant2 | success >> { 'changed': false, 'ping': 'pong' } |
added this to the milestone Oct 2, 2015
commented Oct 2, 2015
@mcalhoun could you also run the devel version with -vvvvv and share the output there? Just please be sure to censor any sensitive information in it before doing so.. |
commented Oct 2, 2015
You might also want to run this simplified command instead of your full playbook: |
commented Oct 3, 2015
I'm getting the same error on the latest devel , 1.9.4 and stable-1.9 .Its similar to: I'm able to run it on a different setup |
commented Oct 3, 2015
so the actual errors is what i would expect from ssh if there is a networking issue (dns, route, etc) can you try: |
commented Oct 3, 2015
The El Captain machine is down right now, but it's not working on my other machine either. However I'm still able to run ansible. I was able to recreate it by installing the latest openssh on my old machine. |
commented Oct 3, 2015
so that confirms this is an ssh problem not really an ansible issue |
commented Oct 3, 2015
can you try using ansible adding -c paramiko on the command line? |
commented Oct 3, 2015
It works beautifully!. Thanks! |
commented Oct 5, 2015
Just to be clear, the original issue I reported in this thread is still occurring (with a3ed9fc) and '-c paramiko' has no effect on the issue. I can ssh outside of ansible just fine using the same username/password, but when using ansible it's not working. |
commented Oct 5, 2015
@mcalhoun it seems your problem is slightly different, can you show us the output when using -vvvv? |
commented Oct 5, 2015
[~/D/C/d/dv-ansible|ruby-2.2.1]‹master*› »»»» ansible vagrant-linux -i inventory/vagrant -m ping -vvvv 0|10:23:10 Using /Users/[redacted]/ansible.cfg as config file Loaded callback minimal of type stdout, v2.0 ESTABLISH CONNECTION FOR USER: root on PORT 2200 TO localhost vagrant2 | UNREACHABLE! => { 'changed': false, 'msg': 'ERROR! [Errno 61] Connection refused', 'unreachable': true } This is on the most recent devel banch pull. If I checkout stable-1.9, then the identical command works fine. I can also SSH directly (outside of ansible) without issue. |
commented Oct 5, 2015
it does not seem to be using ssh, can you run ansible directly? |
commented Oct 5, 2015
@bcoca I'm not sure what you mean...I am running ansible with the following command... ansible vagrant-linux -i inventory/vagrant -m ping -vvvv Are you suggesting that I do something else? |
commented Oct 5, 2015
@mcalhoun are you including the full output? Using that level of verbosity means there should be more ssh debugging information included. For example, here's the output from a ping to one of my VM's: |
Sftp Client For Mac Os X El Capitan
commented Oct 5, 2015
Yes, the full command and full output are below... ansible vagrant-linux -i inventory/vagrant -m ping -vvvv Using /Users/[redacted]/ansible.cfg as config file Loaded callback minimal of type stdout, v2.0 ESTABLISH CONNECTION FOR USER: root on PORT 2200 TO localhost vagrant2 | UNREACHABLE! => { 'changed': false, 'msg': 'ERROR! [Errno 61] Connection refused', 'unreachable': true } |
commented Oct 5, 2015
Hi. My SSH does´t work too. But my message is: Corrupted MAC on input. ssh_packet_read: message authentication code incorrect Can you help me with that? Regards, |
commented Oct 7, 2015
I've been doing a ton of testing with Vagrant, VirtualBox, VMware Fusion, and Ansible (both 1.9.3 and 2.0.0 devel at multiple revisions) on El Capitan and haven't run into this issue at all... I wonder if it's an environment thing? For El Capitan, I upgraded my Mac, but didn't change any particular settings on the system (no exotic hacks to disable new security features or anything). I've tested Drupal VM on both VirtualBox and VMware, and I've tested each of the VM configurations inside ansible-vagrant-examples one by one (some many, many times), and didn't have any issues either running Ansible playbooks manually connecting through private IPs configured by Vagrant, or through the connection that's automatically set up by Vagrant (e.g. 127.0.0.1 on port 2222 or 2200, etc.). Here's the version I just used again to re-run a bunch of the VM provisioning tests: |
commented Oct 7, 2015
@mcalhoun - Are you using a publicly-available vagrant box? And could you give a Vagrantfile/config that can be used to reproduce the issue? |
commented Oct 7, 2015
@geerlingguy What's weird is that this same configuration works just fine if I check out the stable-1.9 branch but doesn't work on the devl branch. For completeness I've also tried this with no ansible.cfg just to make sure it wasn't anything in the config file. I got the same result. Here are the steps I'm taking: Below are my versions (keeping up with the latest source every few hours by cron) and VagrantFile... VagrantFile |
commented Oct 7, 2015
Based on the ESTABLISH CONNECTION FOR USER: root on PORT 2200 TO localhost message, ansible is choosing to use the paramiko transport, not ssh. Does it work if you use -c ssh ? |
commented Oct 9, 2015
@amenonsen You are absolutely correct! Using the -c ssh flag fixes the issue. Any idea why stable-1.9 works without the flag and devel needs the flag? Thanks! Matt |
commented Oct 9, 2015
@mcalhoun when using smart as the transport, we attempt to use ssh with optimal settings (ControlPersist, etc). If that fails, we fall back to using paramiko, which is typically faster when those optimal settings aren't available. So, based on this, it appears we're falling back to paramiko and there's some bug there on the newest OSX version. |
commented Oct 9, 2015
except on OS X we used to have a kernel crash when using ssh and |
commented Oct 9, 2015
We only do that if an ssh password is specified: |
commented Oct 9, 2015
ah, so that might be way only some people see it, those using keys will now be using the newer ssh, those using passwords would still be on paramiko. |
commented Oct 9, 2015
@bcoca / @jimi-c - That would explain why I'm unable to see the problem—I've only tried using keys, not ever specifying a password. |
commented Oct 15, 2015
Just as an update while we're still looking at why this may be happening, set transport = ssh in your ansible.cfg to work around this bug for the time being. |
commented Oct 15, 2015
This may be caused with paramiko as a result of pycrypto. pycrypto is a compiled C module, which means that is was linked against a specific version of python and El Capitan provides a python upgrade. Since upgrading to El Capitan, I've had to re-compile any C modules that I have for other projects. Does re-installing pycrypto resolve the issue? I cannot easily test this right now. |
commented Oct 19, 2015
In case it's a useful datapoint, my El Capitan machine will only connect to my ubuntu VMs if I either (a) set pipelining off or (b) set transport to paramiko. But I may have a slightly unusual Python installation - am rebuilding things to see if that helps. |
commented Oct 21, 2015
If it is any help I had to shorten control path in El Capitan. See http://docs.ansible.com/ansible/intro_configuration.html#configuration-file |
Closed
commented Oct 26, 2015
Per this comment on another issue from @mcalhoun, we believe the core issue reporte has been resolved. If anyone else is still seeing issues with this, please open a new issue and be sure to test specifically if you're seeing the problem with -c paramiko or -c ssh rather than the default (smart ).Thanks! |
Ftp Client For Mac Os
added bug and removed bug_report labels Mar 7, 2018
locked and limited conversation to collaborators Apr 25, 2019
Citrix Client For Mac Os X
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.