# Deploy hanging indefinitely at copy project files step

**URL:** https://discourse.roots.io/t/deploy-hanging-indefinitely-at-copy-project-files-step/9208
**Category:** trellis
**Tags:** ansible
**Created:** 2017-03-27T09:14:16Z
**Posts:** 11
**Showing post:** 11 of 11

## Post 11 by @mZoo — 2018-03-28T05:02:24Z

Just an update that having a version of Ansible that was installed with Homebrew, as opposed to `pip` can also cause this error. As of today looks like `ansible 2.4.2` is the version we want. At least version 2.4.

> [@Github and new Cryptographic Standard](https://discourse.roots.io/t/github-and-new-cryptographic-standard/11701/7):
>
> Thanks for the prompt to look further. Turns out it’s not your primary system openssl version that matters, but your python’s ssl. TL;DR I’m guessing you’re using Ansible installed via homebrew ([kudos to GitHub user 1ambda](https://github.com/ansible/ansible/issues/33417#issuecomment-367913362)). Try brew uninstall -f ansible then pip install ansible Make sure you’re on python \>= 2.7.9 warning Ansible via homebrew # ansible installed from latest homebrew # https://github.com/Homebrew/homebrew-core/blob/29d5b28ca721eca971521af13a4e9a9a9d32bdd9/Formula/ansible.r…

I think it’s basically `brew uninstall ansible` and `pip install ansible==2.4.2`.

`which ansible`  
`which python` (needs to be 2 and not 3 until later this year, I read)  
`which openssl`

Might also be insightful. For me I’m using versions located in `/usr/local/bin`, which is in my `$PATH` _before_ `local/bin` so that those commands will find binaries to use there before getting to `system` versions which are probably located in `/usr/bin`.

I’m not quite clear on how or why exactly the _brewed_ Python `pip` installs one version of `openssl`, while the _brew-installed_`openssl` is different.

---

_[View the full topic](https://discourse.roots.io/t/deploy-hanging-indefinitely-at-copy-project-files-step/9208)._