# Issue with 2019 server and Ansible

**URL:** <https://forum.ansible.com/t/issue-with-2019-server-and-ansible/33666>\
**Category:** AWX Project\
**Created:** [August 24, 2020, 1:16pm UTC](https://forum.ansible.com/t/issue-with-2019-server-and-ansible/33666 "2020-08-24T13:16:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![George\_E](https://avatars.discourse-cdn.com/v4/letter/g/58956e/32.png) [@George\_E](https://forum.ansible.com/u/George_E)\
**Post date:** [August 24, 2020, 1:16pm UTC](https://forum.ansible.com/t/issue-with-2019-server-and-ansible/33666/1 "2020-08-24T13:16:23Z")

</div>

We have:

Tower 3.6.4  
Ansible 2.9.6

Server is 2019, time is correct, getting this error:

• Server: xxxxxxxx {‘msg’: u’kerberos: HTTPSConnectionPool(host='xxxxxxl', port=5986): Max retries exceeded with url: /wsman (Caused by SSLError(SSLError(“bad handshake: SysCallError(104, 'ECONNRESET')”,),)), ssl: HTTPSConnectionPool(host='xxxxxxxxx', port=5986): Max retries exceeded with url: /wsman (Caused by SSLError(SSLError(“bad handshake: SysCallError(104, 'ECONNRESET')”,),))', ‘unreachable’: True, ‘changed’: False}

I took out server name put x’s in it.

New to Ansible, please give details if you have time, what I can try.

Thanks!

---

<div class="post-metadata">

**Author:** ![David\_Maple](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@David\_Maple](https://forum.ansible.com/u/David_Maple)\
**Post date:** [August 24, 2020, 1:45pm UTC](https://forum.ansible.com/t/issue-with-2019-server-and-ansible/33666/2 "2020-08-24T13:45:07Z")

</div>

This list is for the AWX project. Your question is not really related, itt is purely an Ansible question.

However, the first thing I would check is if you have a certificate problem. Either your certificate is not from a trusted CA, like a self-signed cert., or the name you used to reach the server does not match any of the names in the certificate. If it is an untrusted CA, a self-signed or expired certificate, you could set the variable "`ansible_winrm_server_cert_validation: ignore" as a workaround. If that works, you can be sure it is a certificate problem. This may not matter unless you're a stickler about certificates or have compliance policies to live up to.`

`In Ansible documentation, there is a section that may help: [HTTPS Certificate Validation](https://docs.ansible.com/ansible/latest/user_guide/windows_winrm.html#https-certificate-validation)`

`Best of luck.`

---

<div class="post-metadata">

**Author:** ![George\_E](https://avatars.discourse-cdn.com/v4/letter/g/58956e/32.png) [@George\_E](https://forum.ansible.com/u/George_E)\
**Post date:** [August 24, 2020, 5:51pm UTC](https://forum.ansible.com/t/issue-with-2019-server-and-ansible/33666/3 "2020-08-24T17:51:22Z")

</div>

thank you and sorry for spamming wrong group. have a great day.