# New User First Issue discrepancy between ansible & tower

**URL:** <https://forum.ansible.com/t/new-user-first-issue-discrepancy-between-ansible-tower/30107>\
**Category:** Ansible Project\
**Created:** [April 12, 2019, 3:28pm UTC](https://forum.ansible.com/t/new-user-first-issue-discrepancy-between-ansible-tower/30107 "2019-04-12T15:28:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joel.fisak](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@joel.fisak](https://forum.ansible.com/u/joel.fisak)\
**Post date:** [April 12, 2019, 3:28pm UTC](https://forum.ansible.com/t/new-user-first-issue-discrepancy-between-ansible-tower/30107/1 "2019-04-12T15:28:42Z")

</div>

Ansible works, a single playbook “helloworld.yml” works via cmd line. Yet in tower it doesn’t. My hosts file is very simple (just 1 IP).

ansible]$ cat hosts

# This is the default ansible ‘hosts’ file.

---

<div class="post-metadata">

**Author:** ![Jon\_Stanley](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@Jon\_Stanley](https://forum.ansible.com/u/Jon_Stanley)\
**Post date:** [April 12, 2019, 3:33pm UTC](https://forum.ansible.com/t/new-user-first-issue-discrepancy-between-ansible-tower/30107/2 "2019-04-12T15:33:45Z")

</div>

Did you set up the private key as a credential in Tower? It would appear that you can’t authenticate to the remote host when you run via tower. In the UI, there’s an option for what credential to use for the job template. I don’t have an instance in front of me to walk you through it exactly, but that should set you on the right track.

---

<div class="post-metadata">

**Author:** ![dan\_linder](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dan_linder/32/3833_2.png) [@dan\_linder](https://forum.ansible.com/u/dan_linder)\
**Post date:** [April 13, 2019, 1:46pm UTC](https://forum.ansible.com/t/new-user-first-issue-discrepancy-between-ansible-tower/30107/3 "2019-04-13T13:46:43Z")

</div>

Really looks like your credentials in Tower aren’t properly setup properly.

Double check that the ssh key or userid/password you’re using in Tower are valid and work with the 10.244.193.34 system.

If that fails, run the play with verbosity set to 3 or 4, and get onto the remote system to review the sshd log files for additional information and post that back here for us to look into.