# ansible\_winrm\_read\_timeout\_sec & ansible\_winrm\_operation\_timeout\_sec errors?

**URL:** <https://forum.ansible.com/t/ansible-winrm-read-timeout-sec-ansible-winrm-operation-timeout-sec-errors/26138>\
**Category:** Ansible Project\
**Created:** [November 27, 2017, 10:38am UTC](https://forum.ansible.com/t/ansible-winrm-read-timeout-sec-ansible-winrm-operation-timeout-sec-errors/26138 "2017-11-27T10:38:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SurferL](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@SurferL](https://forum.ansible.com/u/SurferL)\
**Post date:** [November 27, 2017, 10:38am UTC](https://forum.ansible.com/t/ansible-winrm-read-timeout-sec-ansible-winrm-operation-timeout-sec-errors/26138/1 "2017-11-27T10:38:26Z")

</div>

$Customer here is confused 🙂 using ansible version 2.4.1.0

I get `fatal: [redacted-url]: UNREACHABLE! => {"changed": false, "msg": "ssl: a float is required", "unreachable": true}`

When I use it in the command line with the following:

> ANSIBLE\_CONFIG=./ansible.cfg ANSIBLE\_FORCE\_COLOR=1 PYTHONUNBUFFERED=1 ansible-playbook -v -i ./ansible/hosts -l “TEST\_nodes” -e “ansible\_user=username ansible\_password=password ansible\_become\_pass=password ansible\_port=5986 ansible\_connection=winrm ansible\_winrm\_server\_cert\_validation=ignore ansible\_winrm\_read\_timeout\_sec=150 ansible\_winrm\_operation\_timeout\_sec=120” ./ansible/site.yml

Am I not allowed to use it in this way?

(Relevant GitHub issue: [https://github.com/ansible/ansible/issues/25539](https://github.com/ansible/ansible/issues/25539))

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [November 28, 2017, 11:24am UTC](https://forum.ansible.com/t/ansible-winrm-read-timeout-sec-ansible-winrm-operation-timeout-sec-errors/26138/2 "2017-11-28T11:24:48Z")

</div>

From that github issue, Dag suggests trying

ansible\_winrm\_read\_timeout\_sec=150.0

If that doesn’t work setting all of this stuff  
“ansible\_user=username ansible\_password=password ansible\_become\_pass=password ansible\_port=5986 ansible\_connection=winrm ansible\_winrm\_server\_cert\_validation=ignore ansible\_winrm\_read\_timeout\_sec=150 ansible\_winrm\_operation\_timeout\_sec=120”

in your group\_vars would save you a lot of typing :-). Since it is going to be true for any windows hosts you have, it one of those things you can probably set once and forget about.

Hope this helps,

Jon

---

<div class="post-metadata">

**Author:** ![SurferL](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@SurferL](https://forum.ansible.com/u/SurferL)\
**Post date:** [November 28, 2017, 2:13pm UTC](https://forum.ansible.com/t/ansible-winrm-read-timeout-sec-ansible-winrm-operation-timeout-sec-errors/26138/3 "2017-11-28T14:13:15Z")

</div>

Sadly ansible\_winrm\_read\_timeout\_sec=150.0 didn’t work

I’ll just add it to the group vars… thanks!

---

<div class="post-metadata">

**Author:** ![SurferL](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@SurferL](https://forum.ansible.com/u/SurferL)\
**Post date:** [November 28, 2017, 2:44pm UTC](https://forum.ansible.com/t/ansible-winrm-read-timeout-sec-ansible-winrm-operation-timeout-sec-errors/26138/4 "2017-11-28T14:44:44Z")

</div>

New issue raised as dagwieers suggested: [https://github.com/ansible/ansible/issues/33339](https://github.com/ansible/ansible/issues/33339)