# unsupported connection type: ssh

**URL:** <https://forum.ansible.com/t/unsupported-connection-type-ssh/17001>\
**Category:** Ansible Project\
**Created:** [December 9, 2014, 6:55pm UTC](https://forum.ansible.com/t/unsupported-connection-type-ssh/17001 "2014-12-09T18:55:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trevor\_G](https://avatars.discourse-cdn.com/v4/letter/t/9de0a6/32.png) [@Trevor\_G](https://forum.ansible.com/u/Trevor_G)\
**Post date:** [December 9, 2014, 6:55pm UTC](https://forum.ansible.com/t/unsupported-connection-type-ssh/17001/1 "2014-12-09T18:55:55Z")

</div>

I hadn’t used Ansible on my laptop for a while, and now when returning to projects that I was working on before, I’m stuck on a fatal:

fatal: [test-centos01] =\> unsupported connection type: ssh

I’m encountering this from a project with a VagrantFile that used to boot and provision just fine. I can’t seem to find anything describing why that may fail and how I could possibly correct it. I’m using:

- MacOS 10.10.1
- ansible 1.7.1
- vagrant 1.6.5
- virtual box 4.3.18

Thanks,  
Trevor

---

<div class="post-metadata">

**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\
**Post date:** [December 9, 2014, 9:47pm UTC](https://forum.ansible.com/t/unsupported-connection-type-ssh/17001/2 "2014-12-09T21:47:44Z")

</div>

What command are you invoking?

I'm assuming something simple like

ansible test-centos01 -m ping

is failing with that message?

What happens if you try other connection types like:

ansible test-centos01 -c paramiko -m ping

and

ansible localhost -c local -m ping

-Toshio

---

<div class="post-metadata">

**Author:** ![Trevor\_G](https://avatars.discourse-cdn.com/v4/letter/t/9de0a6/32.png) [@Trevor\_G](https://forum.ansible.com/u/Trevor_G)\
**Post date:** [December 9, 2014, 10:54pm UTC](https://forum.ansible.com/t/unsupported-connection-type-ssh/17001/3 "2014-12-09T22:54:09Z")

</div>

Yeah. Here’s the result of all those:

trevor:~ $ ansible apps01 -m ping -i inventory.conf  
apps01 | FAILED =\> unsupported connection type: ssh  
trevor:~ $ ansible apps01 -c paramiko -m ping -i inventory.conf  
apps01 | FAILED =\> unsupported connection type: paramiko  
trevor:~ $ ansible localhost -c local -m ping -i inventory.conf  
localhost | FAILED =\> unsupported connection type: local  
trevor:~ $ more inventory.conf  
[apps]  
apps01

I tried uninstalling and reinstalling ansible as well.

trevor:~ $ brew install ansible  
==\> Downloading [http://releases.ansible.com/ansible/ansible-1.7.1.tar.gz](http://releases.ansible.com/ansible/ansible-1.7.1.tar.gz)  
Already downloaded: /Library/Caches/Homebrew/ansible-1.7.1.tar.gz  
==\> Downloading [https://pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.tar.gz](https://pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.tar.gz)  
Already downloaded: /Library/Caches/Homebrew/ansible–pycrypto-2.6.tar.gz  
==\> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec  
==\> Downloading [https://pypi.python.org/packages/source/P/PyYAML/PyYAML-3.10.tar.gz](https://pypi.python.org/packages/source/P/PyYAML/PyYAML-3.10.tar.gz)  
Already downloaded: /Library/Caches/Homebrew/ansible–pyyaml-3.10.tar.gz  
==\> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec  
==\> Downloading [https://pypi.python.org/packages/source/p/paramiko/paramiko-1.11.0.tar.gz](https://pypi.python.org/packages/source/p/paramiko/paramiko-1.11.0.tar.gz)  
Already downloaded: /Library/Caches/Homebrew/ansible–paramiko-1.11.0.tar.gz  
==\> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec  
==\> Downloading [https://pypi.python.org/packages/source/M/MarkupSafe/MarkupSafe-0.18.tar.gz](https://pypi.python.org/packages/source/M/MarkupSafe/MarkupSafe-0.18.tar.gz)  
Already downloaded: /Library/Caches/Homebrew/ansible–markupsafe-0.18.tar.gz  
==\> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec  
==\> Downloading [https://pypi.python.org/packages/source/J/Jinja2/Jinja2-2.7.1.tar.gz](https://pypi.python.org/packages/source/J/Jinja2/Jinja2-2.7.1.tar.gz)  
Already downloaded: /Library/Caches/Homebrew/ansible–jinja2-2.7.1.tar.gz  
==\> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec  
==\> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1  
🍺 /usr/local/Cellar/ansible/1.7.1: 495 files, 6.1M, built in 10 seconds

trevor:~ $ ansible localhost -c local -m ping -i inventory.conf  
localhost | FAILED =\> unsupported connection type: local

I’m not sure if this could be a Yosemite issue.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [December 9, 2014, 11:57pm UTC](https://forum.ansible.com/t/unsupported-connection-type-ssh/17001/4 "2014-12-09T23:57:37Z")

</div>

looks more like a broken install, it could not find any connection plugin.