# Failed to connect to the host via ssh: OpenSSH\_7.4p1, OpenSSL 1.0.2k-fips  26 Jan 2017

**URL:** <https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880>\
**Category:** Ansible Project\
**Created:** [April 13, 2023, 5:06pm UTC](https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880 "2023-04-13T17:06:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![javed\_khan\_siddque](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/javed_khan_siddque/32/4964_2.png) [@javed\_khan\_siddque](https://forum.ansible.com/u/javed_khan_siddque)\
**Post date:** [April 13, 2023, 5:06pm UTC](https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880/1 "2023-04-13T17:06:42Z")

</div>

Hi Team,

i was trying to create ssh connection through tower for one server 162.xx.xx.xx  
but got below error

when i try to do it manually ssh connection , it is successful  
without any error.

fatal: [[server.xx.org](http://server.xx.org)]: FAILED! =\> {  
“ansible\_facts”: {},  
“changed”: false,  
“failed\_modules”: {  
“setup”: {  
“failed”: true,  
“module\_stderr”: “OpenSSH\_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O\_NONBLOCK\r\ndebug2: mux\_client\_hello\_exchange: master version 4\r\ndebug3: mux\_client\_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux\_client\_request\_session: entering\r\ndebug3: mux\_client\_request\_alive: entering\r\ndebug3: mux\_client\_request\_alive: done pid = 35\r\ndebug3: mux\_client\_request\_session: session request sent\r\ndebug1: mux\_client\_request\_session: master session id: 2\r\ndebug3: mux\_client\_read\_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 1\r\nShared connection to 162.xx.xx.xx closed.\r\n”,  
“module\_stdout”: “\r\n”,  
“msg”: “MODULE FAILURE\nSee stdout/stderr for the exact error”,  
“rc”: 1  
}  
},  
“msg”: “The following modules failed to execute: setup\n”  
}

\<162.xx.xx.xx\> Failed to connect to the host via ssh: OpenSSH\_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017

66  
debug1: auto-mux: Trying existing master

67  
debug2: fd 3 setting O\_NONBLOCK

68  
debug2: mux\_client\_hello\_exchange: master version 4

69  
debug3: mux\_client\_forwards: request forwardings: 0 local, 0 remote

70  
debug3: mux\_client\_request\_session: entering

71  
debug3: mux\_client\_request\_alive: entering

72  
debug3: mux\_client\_request\_alive: done pid = 35

73  
debug3: mux\_client\_request\_session: session request sent

74  
debug1: mux\_client\_request\_session: master session id: 2

75  
debug3: mux\_client\_read\_packet: read header failed: Broken pipe

76  
debug2: Received exit status from master 1

77  
Shared connection to 162.xx.xx.xx closed.

---

<div class="post-metadata">

**Author:** ![A\_Prakash](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@A\_Prakash](https://forum.ansible.com/u/A_Prakash)\
**Post date:** [May 18, 2023, 9:57am UTC](https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880/2 "2023-05-18T09:57:33Z")

</div>

Hi Team,

I’m also facing same issue which was reported by javed khan Siddque in the previous mail.

Can some one help me on this to get resolve from Tower.

Regards,  
Prakash A

---

<div class="post-metadata">

**Author:** ![mahespth](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mahespth/32/252_2.png) [@mahespth](https://forum.ansible.com/u/mahespth)\
**Post date:** [May 18, 2023, 10:02am UTC](https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880/3 "2023-05-18T10:02:50Z")

</div>

HI,

SSH failures can be for so many different reasons and for that reason is not easy to say from your output as SSH does not want to give away the the reasons for failure to a potential intruder, I would log on to your target and check your logs in /var/log/ likely messages or secure would tell you why it could not log in, or at least give you an indication as to why. Run a tail -f on the logs while you try your adhoc command or playbook.

Regards

---

<div class="post-metadata">

**Author:** ![A\_Prakash](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@A\_Prakash](https://forum.ansible.com/u/A_Prakash)\
**Post date:** [May 18, 2023, 10:15am UTC](https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880/4 "2023-05-18T10:15:05Z")

</div>

Hi Stephen,

Thanks for your reply.

Sure, i’ll share those details or logs soon from “/var/log/ likely messages or secure” as suggested.

Regards,  
Prakash.A

---

<div class="post-metadata">

**Author:** ![javed\_khan\_siddque](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/javed_khan_siddque/32/4964_2.png) [@javed\_khan\_siddque](https://forum.ansible.com/u/javed_khan_siddque)\
**Post date:** [May 18, 2023, 6:20pm UTC](https://forum.ansible.com/t/failed-to-connect-to-the-host-via-ssh-openssh-7-4p1-openssl-1-0-2k-fips-26-jan-2017/37880/5 "2023-05-18T18:20:16Z")

</div>

I noticed that issue got auto resolved after few days.  
only changes is those messages still appears but as a WARNING not as a FATAL ERROR.